We have about 250 out of 8000 computers that are currently exhibiting the problem that prompted this question
Specifically, after patches are installed (we use group policy and WSUS), my understanding is that the startup mode of the TrustedInstaller service is changed from Manual to Automatic. When the user reboots, the patches complete installation and the
service is set back to Manual for the next cycle.
On the computers that have the problem, the startup mode is never changed to Automatic. Therefore, even if the user reboots, patch installation is never completed. The pending transactions (as shown in the CBS.log file) prevent all subsequent
patches from installing. Some of the PC"s are more than one year behind in patches.
The brute force fix we have found is to set the service to Automatic and then immediately reboot the PC. This takes time from our desktop support team and affects the users. I would prefer a fix from Microsoft.
Has anyone else seen this behavior? Is it a known bug?
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.