VSS Errors 8193 and 13

@EyeinThe Sky
I use Sc Stop in Task Scheduler instead of Net Stop as the latter delays the shutdown and is forced to end (return code 41306). Not had the errors for weeks.
Frank

EyeInTheSky said:

Are you suggesting that my .bat file should look like this:

sc stop cryptsvc
shutdown /s /t 0

Also, could you export your task from your scheduler to a file so that I may see the structure of how you did this?

To export, right click on the task and choose export and then upload the file to your post. I would appreciate seeing the task first hand to examine what I may possibly need to do.

I believe the file will export as a .XML file but I should be able to open it in notepad to see the structure as text.

<?xml version="1.0" encoding="UTF-16"?>
-<Task xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task" version="1.2">
-<RegistrationInfo>
<Date>2020-04-16T16:43:51.0870511</Date>
<Author>ACER-ASPIRE-5\frank</Author>
<Description>On shutdown stop CryptSVC</Description>
<URI>\Stop CryptSVC</URI>
</RegistrationInfo>
-<Triggers>
-<EventTrigger>
<Enabled>true</Enabled>
<Subscription><QueryList><Query Id="0" Path="System"><Select Path="System">*[System[Provider[@Name='User32'] and EventID=1074]]</Select></Query></QueryList></Subscription>
</EventTrigger>
</Triggers>
-<Principals>
-<Principal id="Author">
<UserId>S-1-5-18</UserId>
<RunLevel>HighestAvailable</RunLevel>
</Principal>
</Principals>
-<Settings>
<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>
<DisallowStartIfOnBatteries>false</DisallowStartIfOnBatteries>
<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>
<AllowHardTerminate>false</AllowHardTerminate>
<StartWhenAvailable>false</StartWhenAvailable>
<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>
-<IdleSettings>
<StopOnIdleEnd>true</StopOnIdleEnd>
<RestartOnIdle>false</RestartOnIdle>
</IdleSettings>
<AllowStartOnDemand>true</AllowStartOnDemand>
<Enabled>true</Enabled>
<Hidden>false</Hidden>
<RunOnlyIfIdle>false</RunOnlyIfIdle>
<WakeToRun>false</WakeToRun>
<ExecutionTimeLimit>PT0S</ExecutionTimeLimit>
<Priority>7</Priority>
</Settings>
-<Actions Context="Author">
-<Exec>
<Command>"C:\Sc Stop CryptSvc.bat"</Command>
<WorkingDirectory>C:\</WorkingDirectory>
</Exec>
</Actions>
</Task>

It is a basic task and you use SYSTEM for user account with highest privilege


The script (bat file) is saved in C:\ and should be like this:


Even restart either manual or by updates will stop the VSS errors with this task, I haven't tried Fast Startup yet.
Frank

@EyeInTheSky
"When a specific event is logged", and that is 1074 (shutdown) don't use Daily

Assuming that MSFT did not include the VSS fix in KB4560960 that we got today and you want to try my task I have here the screen shots how to create the Basic Task:
Note that the task may not run the first time as you have to "prime" the task before shutting down: After you created it, right click on the new task in Task Scheduler and left click on "Run", then, after a few seconds, click on "End".again and close Task Scheduler.
Type Administrative Tools in Search, Open it, and click on Services. You will get a Red warning that access is blocked, this means your job ran OK manually and CryptSvc has stopped. Close the warning and left click again on Services in Admin. Tools, this time Services will open, click on "Cryptographic services" and click on Stop (in purlple, left top of the Services screen), then click on Start (in blue left top of Services): The interactive control of Services is not fully integrated with the SC commands. You are all set now,
To double check if CryptSvc is running, type Services in Search and Services should open normally without a warning, close Services, make sure all apps are also closed and shutdown or restart.

When you are back to you desktop you should check your task the first time if it ran OK: Type Event Viewer in Search and in 'Event Viewer Local" click on Information Type in the "Summary of Administartive Events". Find Information Event ID 1074 (Shutdown) and note the time; your task should have run 1 seconds after that time. If you see new VSS errors in Event viewer the task did obviously not run or something is wrong with the script.

Last is, opening Task Scheduler, and look at the end of your task at the "Last run time" (one sec. after Event 1074) and Last Run Results (0x0), Return code 41306 may show after the first 1-2 shutdowns but this will clear up with a steady 0x0 result: This has to do with CryptSVC service dependent apps that are also closed, 41306 is sucessful but the task was forced to end (took too long).

Let me know if not clear or you need help.
Frank

A quick test that I've done for the 8193 and 13 VSS errors -

1. Create a manual System Restore point.

When a System Restore point is created, I usually see the VSS 8193 and 13 errors on reboot.

2. Open Task Manager.

3. Click on the Services tab.

4. Scroll to the CryptSvc entry, right-click, and select Stop.

5. Reboot.

No VSS errors.

Since the 8193 and 13 errors have never prevented me from creating a System Restore point, or rolling back from a previous restore point, it's not a huge concern for me.

As mentioned, the issue appears to have been resolved in Windows 10 2004.

OldNavyGuy said:

A quick test that I've done for the 8193 and 13 VSS errors -



1. Create a manual System Restore point.

When a System Restore point is created, I usually see the VSS 8193 and 13 errors on reboot.

2. Open Task Manager.

3. Click on the Services tab.

4. Scroll to the CryptSvc entry, right-click, and select Stop.

5. Reboot.

No VSS errors.

Since the 8193 and 13 errors have never prevented me from creating a System Restore point, or rolling back from a previous restore point, it's not a huge concern for me.

As mentioned, the issue appears to have been resolved in Windows 10 2004.

Not working for me!

Hi @EyeInTheSky
Glad you got it to work, I know that Brink states in the Tutorials to change task defaults config. to Windows10 but in most other forums it is stated to leave it alone: How to create an automated task using Task Scheduler on Windows 10 | Windows Central The "Configure for" settings should be left alone unless you're required to use a different compatibility option.
Check with Shawn Brink why he recommends to change the config to W10, I am happy with the default settings.
Frank

If you have Pro or above, you can also run scripts at Shutdown using Group Policy -

Place your batch file in C:\WINDOWS\System32\GroupPolicy\Machine\Scripts\Shutdown

Run gpedit.msc

Navigate to Computer Configuration > Windows Settings > Scripts (Startup/Shutdown)

Right-click on Shutdown and select Properties

Click Add

Click Browse, and add the batch file you placed in the Shutdown folder.

Click OK

Run rsop.msc

The first time through, you'll be prompted to select a user or users to assign.

Under your user name and computer name, navigate to Computer Configuration > Windows Settings > Scripts > Shutdown.

If assigned, your batch file should show in that folder.

To ensure that it runs, create a folder C:\Shutdown and use a test batch file that either deletes a file, or creates a file in that folder.