Windows vista hangs at shutting down screen

This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. Registry is an important part, so ensure that the registry is not damaged. Wednesday, July 13, AM. I have the same problem with tascam us, have to plug it out before shutting down. Pain in the arse! Proposed as answer by akeel ahamad Friday, February 17, AM.

Saturday, January 7, PM. Proposed as answer by neep8 Saturday, June 23, PM. Saturday, February 18, AM. Thanks Daemame Sticky notes did indeed stop the shutdown, restart always worked fine Saturday, June 23, PM. Answer 1 I tried everything until I figured it out. Answer 2 Now I did this after disconnecting all drives with exception to the system drive and then tried the system and it did not hang.

Edited by Comptnt. Saturday, October 13, PM. This is obviously a BUG. Why will Microsoft not respond?? I belive we allow them to get away with POR Quality software not fit for purpose by engagin in thes forums and trying to help people Microsoft should do it.

If the software was pirated of course they should not but when it is legitimate? Thursday, November 8, PM. Linda, please help me, I am not so computer savy.

Friday, May 17, AM. Thursday, February 12, PM. I am so happy that this worked! Edited by ki'tiara Monday, August 3, PM. Monday, August 3, PM. That's crazy, my name is Phillip also, and my Win7 hangs on shutdown as well.

What the heck Tuesday, August 18, AM. Edited by jamestheboyyyyy Wednesday, August 30, AM. Wednesday, August 30, AM. There are some apps and programs that are designed to launch when you start your computer. Depending on the number of apps and their complexity, startup and shutdown times may vary from computer to computer. Good time to do some house cleaning.

Download and Open CCleaner or you may go for any other reputable app. That will not only help solve the computer stuck on shutting down screen problem, but also improve booting time. Open Device Manager from the Start menu and wait, scratch that. Intel has launched a utility tool that will keep all your drivers up to date. Just click on the link below to download and install it. I would recommend you to do it even if you are not facing any issues.

Intel drivers are known to cause problems with Windows shutdowns. Open Command Prompt with admin rights and give the below command. Ideally, the shutdown process should go smoothly and is required every once in a while. Getting stuck on shut down screen is frustrating, but you shouldn't for hours either. If it's not working in minutes unless otherwise installing an update, follow this guide.

Next up: Want to customize the Windows 10 Start menu smartly? Click on the link below to learn how to go about doing that. I think we may have tried removing SEP entirely on a test system with no positive change, but I don't see that we logged having tried that, so we'll possibly need to revisit that just to confirm.

I can get this to happen on any of our Vista machines under any profile I try, so I feel like I can safely rule out the profile at this point. The safe mode approach and working slowly from there was going to be my next attempt. It doesn't happen every time, though, which makes this a little more challenging. I'm also beginning to suspect that the system must be on for some minimum period of time before this happens.

From an application standpoint, the only common end-user applications would be Lotus Notes 8. I can get it to lock up without ever starting Notes. However, there is a Multi-user Cleanup service for Notes that might be worth a look as a possible commonality.

Trust me, we've reviewed the event logs. In fact, the Event Log service itself shuts down before the system hangs.

Maybe a developer can help with the shutdown sequence, but I'm guessing networking, graphics or Explorer must be a few of the last items on the shutdown list? Hanging on shutdown typically means something which loaded at startup isn't gracefully letting go of resources. Drivers weren't there, application compatibility wasn't there,". Read more here this article was also published in but it never really got fixed properly so I think it's still mostly valid.

I think Galen's answer was the best. I was able to finally get some good profiling from Process Monitor using the Enable Boot Logging option. With this, I identified the first culprit as the Netman service, which seemed to just go into a polling loop on shutdown and never quit.