Unable to install Monthly Rollups - Windows hangs on "Shutting down service: Windows Modules Installer"

T

Tomas Ruzicka

Hi all,

since a few months I have troubles installing Monthly Rollups on one of our Windows 2012 R2 VM. Every time I select the current Rollup it gets downloaded and installed. Uppon reboot Windows gets stuck at "Shutting down service: Windows Modules Installer" for quite a long time. taskkill nor pskill are able to kill the trustedinstaller.exe (as suggested in some forums - both end with trying to reach the server forever). After some time (30-60 minutes) the VM gets reset, boots up with "Previous shutdown was unexpected" and the Rollup is not installed. If I selected more than just this Rollup for installation, all the other Updates appear not installed the next time I check for updates as well. Downloading the Rollup and installing it manually ends with the very same result.

It's not a problem of just the last Rollup. Except for 2018-07 Rollup which was skipped by intention this happend with at least 2-3 previous Rollups as well. I did not find any usefull information in the WindowsUpdate.log nor the CBS.log (at least nothing usefull for me). There's always an information about closing TI and then many minutes later about starting it again (after the "unexpected shutdown"):

2018-08-21 09:50:01, Info CBS Starting TrustedInstaller finalization.˰

2018-08-21 09:50:01, Info CBS Ending TrustedInstaller finalization.˰

2018-08-21 10:50:39, Info CBS TI: --- Initializing Trusted Installer ---˰

2018-08-21 10:50:39, Info CBS TI: Last boot time: 2018-08-21 10:50:17.484˰



Until the last try yesteray I didn't watch the console of the VM in the time between clicking on "Restart Windows" and the "Shutting down..." mesage so I'm not sure if it was the same previously as well. But during this last try

* Windows really restarted correctly

* displayed the "Updates are being installed..." message

* followed by "failed to install Updates - rolling back"

* followed by the "Shutting down service: Windows Modules Installer" message

* booted up with "previous shutdown was unexpected" many minutes later


To recover I tested already to:


None of the above was successfull unfortunately. Luckily, this VM is not business critical so I can play with it. I'm already prepared to reinstall it completely if necessary. But before I do this I would like to ask if someone else has/had the same problem, how to "debug" that misbehavior and how to recover finally.

Thanks in advance for any hints!

Continue reading...
 
Back
Top Bottom