«The VSS service is shutting down due to idle timeout» — event 8224 on Windows 10.

Original Title: System volume information keeps increasing

This folder keeps increasing and gobbling up my C drive. I have System Restore set on the C drive alone with a maximum of 12 Gb, but it ignores this and sets itself to 100%. I have many files in this folder and a new one appears often (15+ in the last 90 min). Each time a new file appears, it coincides with «The VSS service is shutting down due to idle timeout» — event 8224 in Event Viewer. Any ideas how to stop it?.

Thanks for replying and sorry for delayed response.

SFC scan and DISM scan will detect if any of the system files are missing or corrupted and will replace the same to enhance and resolve the system issues on the PC.

Run SFC scan and DISM scan on the PC by following the steps below and check if the issue is resolved.

SFC scan is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. If a Windows Resource Protection (WRP) file is missing or is corrupted, Windows may not behave as expected. For example, some Windows functions may not work, or Windows may crash.

Windows corruption errors may prevent Windows updates and service packs from installing. For example, an update might not install if a system file is damaged. The DISM scan or System Update Readiness tool may help you to fix some Windows corruption errors.

Step 1: Open an Administrator command prompt window by

1. Press Windows logo + X keys on the keyboard and select Command Prompt (Admin) option.
2. Click on Yes and continue. Provide administrator password if prompted.
3. Check if it says Administrator: Command Prompt at the top of the command prompt window.

Step 2: Type the following commands in the CMD Prompt:

Dism.exe /online /cleanup-image /scanhealth

Dism.exe /online /cleanup-image /restorehealth

sfc /scannow

Step 3: Close the command window and check if the issue is resolved.

Write to us with the status of the issue on the same post for further assistance. Your reply is most important for us to ensure we assist you accordingly.

Computer Shuts Down During Windows 10 Upgrade

Replies (9) 

17 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

3 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

4 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Power down computer.

Wait 10 minutes.

Setup will automatically restore your previous Windows 10 build or previous version of Windows.

Launch command prompt with administrator privileges.

Press Windows key + X

Click Command Prompt (Admin)

Type the following command:

rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN

Hit Enter on your keyboard

Exit command prompt

• Disable (preferrably uninstall) your Antivirus utility before attempting the upgrade.
• Restart a few times and try again.
• Disable General USB Devices (example — Smart Card Reader).
• If you are using a SCSI hard disk, make sure you have drivers available for your storage device on a thumdrive and it is connected. During Windows 10 setup, click the Custom Advanced Option and use the Load Driver command to load the appropriate driver for the SCSI drive. If this does not work and setup still fails, consider switching to a IDE based hard disk.
• Do a clean boot and try again.
• If you are upgrading using the .ISO file, disconnect from the Internet during setup, if you are connected by LAN (Ethernet) or Wi-Fi, disable both and attempt setup again.
• If you are updating through Windows Update, when the download reaches 100% disconnect from the Internet LAN (Ethernet) or Wi-Fi and proceed with the installation.
• If that does not work, try using the .ISO file to upgrade if possible.
• If you are connected to a domain, switch to a local account
• If you have any external devices attached to the machine, disconnect them (example, gaming controllers, USB keys, external hard disk, printers, non-essential devices).

Click HERE to download official ISO media for Windows 10 from Microsoft.

How does a windows service behaves on Windows shutdown?

Is there a timeout for stopping Windows Services when Windows is shutting down? I know there is a registry key «WaitToKillServiceTimeout» but does this timeout effect on services, when Windows is shutting down or is there another timeout?

I want to find out, how long system during shutdown waits for services when it calls the OnStop method of a service.

Can a service prevent Windows from shutting down?

1 Answer 1

[WaitToKillServiceTimeout] Determines how long the system waits for services to stop after notifying the service that the system is shutting down.

Then yes, that’s value used to wait for services shutdown but also note that it’s shared for all services:

If all services stop before this value expires, the system shuts down.

For your question «Can a service prevent Windows from shutting down?» answer is «more or less». You can’t prevent Windows to shutdown (it may be really annoying for users if they can’t shutdown because a service decided they shouldn’t) but:

When the value of this entry expires, the system notifies the user that the service has not stopped. The user can either force the service task to stop or continue to wait. If the user waits, this value specifies the interval between repeated user notices that the service has not stopped.

Some services increase the value of this entry to provide more time for cleanup tasks.

In case your service is slow to shutdown you may increase such value (during installation) to give you more time. In theory using a very high value you’ll postpone shutdown for a very long time (but this behavior isn’t same as cancel it and don’t forget it’s shared for all services).

AFAIK a service can’t cancel shutdown but a GUI application can do it using ShutdownBlockReasonCreate() function.

Default Shutdown Order of Windows Services

While I could find articles on how the windows services start in an order that is based on service groups and within a service group based on tags, I am unable to get information on the default shutdown order of windows services.

If we do not specify a «PreshutdownOrder» to alter the shutdown sequence, can we assume that windows services would shutdown in an order that is reverse of the order in which they start? If no then why is it so and how is the shutdown order determined? If yes then can you please point me to relevant documentation preferably from Microsoft?

I am asking this question because I have an application whitelisting service (say A) on my machine that belongs to a service group and a few services (say B and C) that do not belong to any service group. For system security reasons, I want to ensure that whitelisting service A starts before other services start and shuts down after other services shut down.

1 Answer 1

After the preshutdown notifications have been completed, all control handlers that have called SetServiceStatus with the SERVICE_ACCEPT_SHUTDOWN control code receive the SERVICE_CONTROL_SHUTDOWN control code. They are notified in the order that they appear in the database of installed services.

I believe the upshot of that is that the order in which services are notified is unpredictable. Of course, the services do not necessary stop in the order in which they are notified; the system does not wait for each service to stop before notifying the next one.

Based on your description, in your scenario the best option would probably be for service A to continue running during the system shutdown. Any service that does not register for shutdown notification is simply left running until the system is actually powered down or restarted.

However, if it is essential that service A is notified that the system is shutting down (for example, it might need to close a database file cleanly) then it can return STOP_PENDING while it waits for all of the dependent services to stop.

Restart or Shut Down

You might have to restart the host computer and all of the stations in your MultiPoint Services system if instructed after you install hardware, software, and software updates. If you have added new hardware devices to a station, you might also want to associate the hardware devices to that station. For more information about how to associate stations, see the Switch Between Modes topic.

To turn off your MultiPoint Services system’s computer safely, the computer must perform a shutdown process that closes any open programs, shuts down Windows, and turns off your computer and its associated stations. Do not just unplug or press the Power button to turn off your computer. You should shut down your computer at the end of the day and when you must install new hardware enclosed in the computer case. If you add other hardware to the system, you may also need to shut down or restart the server.

Before you restart or shut down the computer that is running MultiPoint Services, all user sessions must have ended.

Restart the computer

End all user sessions. For more information about ending user sessions, see the End a User Session topic.

In MultiPoint Manager, click Home, and then click Restart the computer.

Shut down the computer

End all user sessions. For more information about ending user sessions, see the End a User Session topic.

In MultiPoint Manager, click the Home tab, and then click Shut down the computer.