To be honest I don’t know exactly which KB is associated with the issue.
I pushed out over 20 patches in a short span of time and never botherd to pin down which one it was. I just restored the three machines that exibited the problem and let them do the recent patches in smaller groups.
You can use process explorer to try and pin it down but I was never easily able to find a process/patch match. In the end I had to much to do so I just retored them to an earlier state.
Hell it could have been caused by a combination of patches overwriting the same file at the same time or something.