Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My Windows 7's shutdown process is taking too long, so I created a custom Event Viewer view to review all events from all logs during the delay. The trouble is, the event log has nothing recorded. For example, I initiated a system restart (Start > Restart) at 12:51:09pm today.

enter image description here

Do you know where I can trace or what I can chase to see what happens after Event ID 13? Or find what causes the delay? I can swear that Windows is still running a shutdown/hourglass screen after 12:51pm.

share|improve this question
does shutdown -f take the same time? – soandos Jun 13 '11 at 17:56
Do you have anything like OffLine files? – sgmoore Jun 13 '11 at 18:56
soandos, yes. so does shutdown -f -r. sgmoore, no. – William C Jun 13 '11 at 19:03
Try doing it as another user. It may be a bad profile. Also, if you want to so that command, do shutdown -s -f -t 00 (s=shutdown, f=force so you don't have to end task on anything, t 00=do it immediately. – KCotreau Jun 13 '11 at 19:04
please, download and run "process explorer" ( and see all processes running on your computer. right click on column header and check "command line" to see from where the processes are started. then use "save as" to save a txt file with all informations showed, open it, copy and paste that here and so we can see if the problem is a running process. – kokbira Jun 15 '11 at 11:40
up vote 1 down vote accepted

Usually the first thing to do is to try a shutdown in safe mode and if that works, use MSConfig to disable all non essential services and startup processes and test again. If that works, you start enabling them until you get it to go wrong.

One very simple method, which sometimes helps, is to open task manager and switch to processes and leave this open while you try to shutdown. Quite often task manager will remain open long enough for you to see what processes are taking a long time to shutdown and may identity the fault. (In some case, task manager will shutdown early, but you can restart it again)

Another alternative is Process Monitor from Sysinternals/Microsoft which may show you what is happening (eg file/network activity) when you shutdown.

At the advanced level Microsoft have some performance tools which are designed to help OEM's trace and diagnose startup and shutdown problems. I have never used them and given their target market, they may be complicated to use, but if you are interested search for Xbootmgr.exe

share|improve this answer

Go to:

Control Panel > All Control Panel Items > Performance Information and Tools > Advanced Tools

Are there any performance issues reported there?


You can also do a clean boot, then re-enable Non Microsoft programs and services one at a time to possibly find the offending one that slows shutdown.

See this page

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .