I am trying to deploy Critical OS patches using the pre-installed Windows OS Critical Patch label. I have tried this on a number of machines but around 90% of the time I have machines that this fails to deploy on. The error message is SUCESS (102) but they all say Reboot Required.

  • A reboot (or multiple reboots) does not solve the issue.
  • Resetting the deploy tries and re-deploying does not solve the issue.

We are running V5.5.90548 with all applied hotfixes (going to v6 right now it not an option). I am hoping to avoid having to go to each machine and running updates locally.

Any insight is appreciated.

4 Comments   [ - ] Hide Comments


  • Are all the patches for that label downloaded?
  • They are downloaded and ready to be deployed.
  • Is there any download errors?
  • No download errors. I did notice something else. The patches showing as Error requesting the reboot are showing as an installed patch (via windows update) on the machines. But the error log does not go away. Going to try a label with OS patches that are only x86 and see if that makes a difference.
Please log in to comment

There are no answers at this time
Answer this question or Comment on this question for clarity


Nine Simple (but Critical) Tips for Effective Patch Management
This paper reviews nine simple tips that can make patch management simpler, more effective and less expensive.