we have problems doing windows update and rebooting my windows server 2008 r2.
it says we have updates to do so we did them and everything seems to be fine but the window seems to be not responsive after a certain time.
I did a log off and see my window change status from installing update #3 to finished and need rebooting.
I log again and windows update ask me to reboot. so I click on restart.
my server initiate the reboot process but stay 1 hour 30 minutes on the window "shutting down windows modules installer service..."
this problem is happening on all my server 2008 r2 and it takes from 1 hour to 1 hour 30 minutes depending which server.
this is not a dns issue because if i do not install updates it reboot in 2 or 3 minutes. this his happening only when we are doing windows updates.
this happen on my private network without internet access and also on my public network with internet access.
if I shutdown the server when it is shutdowning the modules installer service i have to do the updates again. but if i let the server takes 1 hour and more it finally shutdown the module installer service and I can install other updates or stop if there is not anymore updates to do.
these servers are only member server with adminpak for managing my active directory dns, dhcp etc...
can you help me and tell me why windows server 2008 r2 is so buggy for the windows update service.
if I don't have this problem i have to do a checksur.exe to find which kb is corrupted and fix it before continuing my updates.... so complicated with 2008 to keep them up to date...