This tutorial will show you how to change the WaitToKillServiceTimeout value for how long the system waits for services to stop when you shut down the computer in Windows 10 and Windows 11.
The WaitToKillServiceTimeout value is the default 5 seconds Windows waits for background services to stop gracefully on their own when you shut down the computer.
If all services stop before the WaitToKillServiceTimeout value expires, the system will automatically continue to shut down without waiting for this value to expire.
If the WaitToKillServiceTimeout value expires, Windows will automatically force stop all background services that didn't already stop gracefully.
If any services require more than 5 seconds to shut down, they do not shut down gracefully since they are forced to stop. If you have this situation, you may want to increase the WaitToKillServiceTimeout value to allow more seconds. The WaitToKillServiceTimeout setting has a maximum value of one hour.
Some apps may change the WaitToKillServiceTimeout value when you install them, giving their background services extra time to stop.
Reference:

DFSR event ID 2213 - Windows Server
Describes an issue that triggers event ID 2213 in Windows 2008 or Windows 2012. This event occurs when a server or the DFSR Service experiences a dirty shutdown. Best practices are included.
learn.microsoft.com
You must be signed in as an administrator to change the WaitToKillServiceTimeout value.
Here's How:
1 Open Registry Editor (regedit.exe).
2 Navigate to the key below in the left pane of Registry Editor. (see screenshot below)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3 In the right pane of the Control key, double click/tap on the WaitToKillServiceTimeout string value (REG_SZ) to modify it. (see screenshot above)
4 Enter a number for many milliseconds you want for the WaitToKillServiceTimeout value, and click/tap on OK. (see screenshot below)
The default value is 5000 milliseconds (5 seconds).
It is recommended to not set a value below 2000 milliseconds (2 seconds).
5 You can now close Registry Editor if you like.
That's it,
Shawn Brink
Last edited: