Shutting down Windows 10 from CMD takes more time than usual....

Click For Summary

Discussion Overview

The discussion revolves around the differences in shutdown times between using the command prompt and the graphical user interface (GUI) on Windows 10. Participants explore the implications of command shutdown processes, potential settings affecting shutdown speed, and the role of Windows fast startup.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested

Main Points Raised

  • One participant notes that shutting down Windows 10 from CMD takes longer than using the GUI, comparing it to Linux shutdown processes.
  • Another participant suggests that the command shutdown may wait for processes to close orderly, while the GUI may force a timeout, raising a question about prompts for unsaved files during shutdown.
  • Several participants mention the concept of "Windows fast startup," with one questioning its relevance to slow shutdown times.
  • Another participant proposes that there is a default time before shutdown, referencing the /t switch in the shutdown command.
  • A participant shares an update that using the command shutdown /s /hybrid /t 0 /f significantly improves shutdown and startup times, making them comparable to the GUI method.
  • One participant suggests trying a shift-click on the GUI shutdown button as an alternative approach.

Areas of Agreement / Disagreement

Participants express varying views on the reasons for the differences in shutdown times, with some proposing technical explanations while others question the relevance of certain factors. The discussion remains unresolved regarding the exact causes of the observed shutdown delays.

Contextual Notes

Participants reference specific command switches and settings, such as the /t switch and fast startup, but do not reach a consensus on their impact on shutdown times. There are also mentions of potential differences in behavior based on application states during shutdown.

Who May Find This Useful

This discussion may be useful for users experiencing slow shutdown times on Windows 10, particularly those interested in command line operations and system settings related to shutdown processes.

Wrichik Basu
Science Advisor
Insights Author
Gold Member
Messages
2,186
Reaction score
2,694
TL;DR
Why does Windows 10 take more time to shutdown if it is triggered from the command prompt rather than the usual shutdown button?
Just like a Linux computer can be made to shut down from the terminal using sudo poweroff, a Windows 10 PC can be shut down from the command prompt using shutdown /s.

I have, however, seen that Windows 10 takes more time to shut down if the command is triggered from CMD. In my laptop, it generally takes two times the time for usual shutdown using the GUI, unlike Linux, where shutting down from the terminal is perhaps faster than using the GUI. In addition, starting the laptop (running Win 10) after it was shut down from CMD takes more time too.

What is the difference between shutting down the PC from CMD compared to the normal shut down process using the GUI buttons?
 
Computer science news on Phys.org
My WAG involves running processes. Command shutdown might be waiting for orderly process shut down while the GUI forces time out. Do you see different prompts if, say, an unsaved Word file is open before shutting down?
 
  • Like
Likes   Reactions: phinds
Google 'Windows fast startup'.
 
  • Like
Likes   Reactions: hmmm27
pbuk said:
Google 'Windows fast startup'.
What does fast startup have to do with slow shutdown? I'm not saying it doesn't just curious what the connection is if there is one.
 
I'm guessing there's a default time before shutdown... yup the /t switch
 
  • Informative
  • Like
Likes   Reactions: jedishrfu and phinds
hmmm27 said:
I'm guessing there's a default time before shutdown... yup the /t switch
Forgot to mention - i have set /t to 0.
Klystron said:
Do you see different prompts if, say, an unsaved Word file is open before shutting down?
If /t > 0, no prompt is shown. But in this case, no application is open when i am shutting down.
 
Yeah, I thought it seemed too easy... perhaps looking at the syslog (whatever M$ calls it) could shed some light... Event Viewer.
 
phinds said:
What does fast startup have to do with slow shutdown? I'm not saying it doesn't just curious what the connection is if there is one.
That's why I suggested a search :wink: but briefly fast startup works by loading a preconfigured kernel from disk which was saved during the previous shutdown (unless you disable fast startup), thus avoiding loading many separate driver files from disk as well as part of the (UEFI) BIOS bare metal boot routine.
 
  • Informative
Likes   Reactions: phinds
pbuk said:
That's why I suggested a search :wink: but briefly fast startup works by loading a preconfigured kernel from disk which was saved during the previous shutdown (unless you disable fast startup), thus avoiding loading many separate driver files from disk as well as part of the (UEFI) BIOS bare metal boot routine.
For fast startup, the command should be shutdown /s /hybrid. Will try it tonight and post the results.

Update: Using the command shutdown /s /hybrid /t 0 /f makes the shutdown and startup quite fast, almost as fast as using the GUI buttons.
 
Last edited:
  • #10
Try <shift> clicking the GUI Shutdown button.

(ie: what pbuk said)
 

Similar threads

Replies
2
Views
3K
  • · Replies 12 ·
Replies
12
Views
5K
  • · Replies 18 ·
Replies
18
Views
3K
  • · Replies 12 ·
Replies
12
Views
4K
  • · Replies 123 ·
5
Replies
123
Views
20K
Replies
3
Views
12K
  • · Replies 37 ·
2
Replies
37
Views
7K
  • · Replies 11 ·
Replies
11
Views
2K
  • · Replies 7 ·
Replies
7
Views
2K
Replies
2
Views
8K