Thank you for posting your question.
As discussed through support case today, this looks like a known issue in relation to TrustedInstaller.exe but this is more Microsoft issue.
Windows Server 2008 will run TrustedInstaller.exe shortly after rebooting after installing the monthly Windows Updates.
The program will take up ~75-100% of a CPU core for up to 30 minutes or more, as it is running the malicious software removal scanning code.
While this is running on a single-core machine, certain programs or services will not work properly, such as SQL Server -- most single-core SQL Server installations will not take connections while the above is running.
So, plan accordingly. After your first reboot, expect a CPU hog.
If you're running on Amazon EC2, it may be wise to make sure to boot up as a dual-core server after installing updates, and then back down to a single-core once TrustedInstaller is done hogging a core. => source:
in addition to entries from the CBS.log:
2017-05-17 22:35:44, Info CBS Expecting attribute name [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
2017-05-17 22:35:44, Info CBS Failed to get next element [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
you can find several possible solutions provided by Microsoft, for example:
- a. Press “Windows Key" to open Start menu
- b. Type “cmd” without quotes in the search box.
- c. On the left pane, right click on the “cmd” option and select “Run as Administrator”.
- d. Type ‘sfc /scannow’ without quotes and hit enter.