Windows shutdown service

Any additional feedback? Submit and view feedback for This product This page. View all page feedback. In this article. Displays the Remote Shutdown box. Logs off the current user immediately, with no time-out period. Shuts down the computer. On the next boot, if Automatic Restart Sign-On is enabled, the device automatically signs in and locks based on the last interactive user.

After sign in, it restarts any registered applications. On the next restart, if Automatic Restart Sign-On is enabled, the device automatically signs in and locks based on the last interactive user.

Aborts a system shutdown. Effective only during the time-out period. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? In this article. If your service takes longer than 60 seconds, it will still be terminated. Be sure to choose a timeout value that is long enough to cover your scenario, but not too long to make shutdown intolerable.

Changing the WaitToKillServiceTimeout setting is a quick fix but the delay you specify will apply to all services. If another, non-critical service is hung, Windows will wait the full duration before terminating it. To make sure that Windows waits for your specific service, you should update the code to accept preshutdown notifications. This article reviews the code to be added in C projects. The preshutdown process was introduced in Windows Vista circa As the name suggests, it runs before the regular shutdown process.

Its purpose is to give mission-critical services an early start on exiting, ahead of less important modules. Windows proceeds with the regular shutdown procedure see above. By default, that fixed period is seconds 3 minutes — more than enough time for most Windows Services to tidy up and exit gracefully.

But what if you need more than three minutes? Fortunately Microsoft has provided a solution there as well…. With a simple code change, a preshutdown service can instruct Windows to wait more than the default 3 minutes for the service to end in the preshutdown phase. Whichever works better in your situation.

Hopefully one of these two solutions will delay shutdown long enough to eliminate the database corruption. Please try them, and be sure to get in touch if you have any questions! Hi, Thanks for very usefull post. I need exactly this 3 minutest delay and I guided this post and build my service. But unfortunately windows is not waiting 3 minutes. Having said that, a couple of things come to mind. Firstly services are on the clock. If they don't respond fast enough then things go awry.

For a shutdown you have 20 seconds, by default. For a reboot it is longer seconds in Windows Hence if your shutdown is taking too long it might fail on shutdown but not on a reboot. The other thing that comes to mind is that, maybe, your machine isn't actually shutting down. If you're clicking the Shut Down option in the Power menu then it likely is. But starting with Win 8 we have fast boot which could be changing the shut down request to hibernate or something.

I've never looked at the shutdown behavior of services in this mode so I cannot confirm. If your service runs on the computer being shut down, it get's the proper order to close.

Wich it should do in a speedy fashion. If you service design requires that you differentiate between ending of service due to shutdown or reboot, the design might be faulty. There is no reliable way to differentiate between the two. After all a user could just power down via ACPI event pressing the power button at the start of the boot sequence.