I experience a strange problem yesterday that I haven't seen before.
We had previously approved the patch for MSWU-919, Q2800095 (File Windows6.1-KB2800095-x64.msu), shortly after it was initially released in April 2014
It appears that Microsoft re-released the file for MSWU-919. The original file was Windows6.1-KB2800095-x64.msu and the new file is Windows6.1-KB2800095-V2-x64.msu on 6/10/14. (notice the V2)
In preparation for patching this week, I downloaded patch files that we didn't' already have, but didn't actually "approve" any of them for deployment.
Our Shavlik agents started picking up the newly downloaded v2 version and deployed them unexpectedly. This particular patch requires a restart, so any system that already had patch MSWU-919 previously approved, brought down and executed the new version and was restarted, causing an unexpected disruption for us.
I'm not sure how this got through the Shavlik patching process. The KB is the same, but the file name seems to have changed. I looked through the release notes of the shavlik XML files and don't see any reference to an updated version of MSWU-919.
Any idea what happened and if something like this can be prevented in the future?