7

Windows 7 msconfig lets users select the options No GUI boot and OS boot information to have a list of drivers being loaded during boot. Is it possible to have similar detailed messages during shutting down/restarting/logging off? Here's the screen I want disable or give me more details:

Shutting down Windows 7

  • windows
  • shutdown
  • msconfig
Improve this question
7
  • 1
    I don't understand the question. Can you try to explain what you want, preferably with an example?
    – LPChip
    May 25, 2014 at 20:29
  • 1
    @LPChip I think what he wants is to replicate the No GUI Boot feature for shutdown, ie. No GUI Shut down...
    – ᔕᖺᘎᕊ
    May 25, 2014 at 20:34
  • 1
    Yes, I want to do what what @shub said.
    – user33758
    May 25, 2014 at 21:28
  • I want to know what step of the shutdown process is making it slower.
    – user33758
    May 25, 2014 at 21:33
  • 2
    I think you're looking for this then: thewindowsclub.com/enable-verbose-status-message-windows. It tells you exactly what is happening during boot up/shut down, without removing GUI, it says things instead of 'shutting down...'
    – ᔕᖺᘎᕊ
    May 25, 2014 at 21:37

3 Answers 3

Reset to default
12

There can be many reasons Windows takes a long time to shutdown. Here are some ways to find out why and to speed it up:

Why:

  1. Enable Verbose Mode. This tells you what is happening during shut down, like 'Stopping Services':

    • Press Win + R
    • Type regedit
    • Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
    • Right click on the right pane, New > DWORD Value. Name it verbosestatus. Double click it, make the value 1.

  2. Check the Event Log:

    • Press Win + R
    • Type eventvwr.msc
    • Go to Applications and Services Logs > Microsoft > Windows > Diagnostics / Performance > Operational.
    • Sort the 'Task Category' column alphabetically.
    • Look at all items under the category 'Shutdown Performance Monitoring'
    • Try to spot anything odd.

What to do:

  1. Change the delay before programs are force closed:

    • Press Win + R
    • Type regedit
    • Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control
    • Double click the WaitToKillServiceTimeout
    • Set the value to something smaller (milliseconds - 1000 = 1 seconds)

  2. Use Windows Performance Toolkit (this is a link to another SuperUser answer)

  3. Perform a clean-boot:

    • Press Win + R
    • Type msconfig
    • Click General tab > Selective Startup
    • Uncheck Load Startup items
    • Click the Services tab, check the Hide all Microsoft Services box, and then click Disable All
    • Click OK, and when you are prompted, click Restart.

Now, this should speed it up a lot. From the previous steps, if you are suspicious about any programs, then un-check them first. Then start enabling one-by-one and see which one is causing the problem.

Hope this helps

Improve this answer
1
  • 1
    I ended up using Windows Performance Toolkit and found out that Comodo Firewall was the problematic program.
    – user33758
    May 27, 2014 at 0:15
7

From user @shub helpful link:

  1. Run gpedit.msc from the Start menu search
  2. Go to Computer Configuration > Administrative Templates > System
  3. In the right pane, double-click on Verbose vs normal status messages

Once enabled, this setting makes the system display detailed status messages that show each step in the process of starting, shutting down, logging on, or logging off the system.

However, if the “Remove Boot / Shutdown / Logon / Logoff status messages” setting is enabled, this setting will be ignored.

--

Update: I've ended using Windows Performance Toolkit and found out that Comodo Firewall was the problematic program. After reinstalling it, Windows now shutdowns normally.

Improve this answer
1
  • 2
    For those looking for this setting, it has seemingly been renamed in Windows 10 as "Display highly detailed status messages", but it's still in the same location.
    – SeinopSys
    Jan 22, 2019 at 18:29
1

Have you checked the eventlog? It will log all problems during startup/shutdown.

You are likekly to find the problem in the system log, but if an application were to hang, it would be in the application log instead.

Improve this answer