If you know you have absolute ability to rebuild, and you should know this before you start, then you know you can handle the kitchen blowing up. Last night it took me almost 2 hours to complete Windows Module Installer service after 147 patches have been deployed to my Win srv 2012 R2 64 bit. My first suspicion is perhaps one of the Windows update patches this week 10 Nov 2011 may something to do with it, which was still pending a system restart. From another computer using the Services snap-in services. It all just exercises in frustration. It was already running as a production server so no new software has been installed since.
Shutting down service: Group Policy Client. Patience was the best answer to this issue for me. I am not sure why it happens but I have had to reactive a few servers after an odd event caused them to lose their license activation. Best Regards, Eve Wang Please remember to mark the replies as answers if they help and unmark them if they provide no help. You can remotely kill the hung services from there.
I've never seen that problem, but here's my take: Windows Updates needs to finish some post-update tasks and is unable to do so when a non-admin user logs on to the server. Then I log in to another server by using admin credentials and go in to services. I'm not sure what to try next, I'd appreciate any pointers. I gave up after 10 minutes. Of course after an hour or so you should consider pulling the plug. After serveral reboots claiming it was installing updates, it finally got to login, but at that point started slinging errors about bad entry points in dlls, and it could not start Service Manager, even after a second restart by me.
Particularly if they have not done any in a long time or if you recently virtualized the server. Also check to see if your license did not become deactivated. It took 7 and half minutes stalled on the shutting down windows installer module message. Of course, if you're accepting stop requests, then you'd better make sure that your service can safely handle those requests, especially if your service is still progressing through its startup code. Your input is still very much appreciated.
Thanks Hi, Is there any update about this problem? The link you mentioned is used to connect client to Essentials domain without joining domain. Patience worked for me as well. Subsequent shut downs stop at the same message. Very odd and very fast before log on. Type troubleshooting in the Cortana search bar, troubleshooting appears at top. One thought - If the shutdown was an unexpected one shouldn't I see an error message like I did ages ago with a power cut? Please remember to select Mark as Answer if someone provides the answer or mark as helpful if the response helps to lead you in the right direction. Then tried all other options that windows is giving under log on window.
Or, run the System Configuration Utility, and then click to clear the check box for the problem item. I'm offering the suggestion to sit tight for a bit and let Windows install the updates before hard-resetting it. Judge the risks and act accordingly. If you have same problem then you need to try. After that I was able to signon, but only with a local account and not domain account. He viewed it frame-by-frame and this is what he saw: 1.
The operating system on this machine was Windows Server 2008 R2. If it's physical server than you need to check the power supplies. It would make this reply to the top and easier to be found for other people who has the similar problem. The other running Windows 2003 guest was stuck in the logon dialog. Sometime happen 2- or 3 times a day but sometimes not happen whole week. I then considered what other steps I could take to try and force the server to reboot remotely.
But it does make for a fun, exciting evening of rebooting when you think one is about to get stuck. It will start Windows Vista by using a minimal set of drivers and startup programs. Virtual 2012 R2 server seemed stuck at shutting down service windows modules installer - long enough for me to start searching the problem. Like mentioned above, can take some time! Is any of these a known troublemaker? They go by very fast and I am unable to read some. I have seen some server lose their activation. And that is hard coded into the executable.
It happens suddenly and shuts down the server without any information. I got logged in and am now clearing out the needs consolidation message by consolidating them. Let me know if there is any further details I can provide, I will be checking this frequently throughout the day. Shall I force a hard reboot? I then considered what other steps I could take to try and force the server to reboot remotely. Just an Hyper-V management service timeout. Eventually it just cleared itself - rebooted - and the updates had installed correctly 94 of them, due to it being a new Server 2012 R2 install. Can anyone suggest please I'm a novice with Server 2012 what's going on? That would mean that if you install windows 10 now from even the current installation media you should automatically activate your windows 10 licence.
The easiest way to use the script described in the article bearing in mind that you will have to do all steps remotely. Still there when I came back so I started searching for answers. Please post back and let us know. Again, just be patient and don't pull plug, let it run. Obviously, this service prevents the server from performing the correct reboot. This info does not match exactly with your post. Please let us know if you would like further assistance.