VSS Errors 8193 and 13

Shanedh65 said:

Here is the batch file that I created to stop the cryptographic service. You need to run this bat file as an administrator, then you can shutdown or reboot windows.

You must use this batch file before shutting down. I know it works for me.

If you have windows 10 pro you can use gpedit to run this bat file everytime you shutdown or restart windows by going to gpedit - computer configuration - windows settings - scripts - shutdown. Select add, select the bat file then ok. You don't need to run this batch file if you use this option.

Absolutely amazing, thank you so much!

I have done several restarts and shut downs since yesterday night and have not received these VSS errors anymore.

Your solution is much simpler than it looks. It's simply one of those superficial errors that happen on shutdown and restart.

I have made the experiment to look at the clock timer and the VSS errors that are recorded are exactly at the same time when the restart or shut down occurs.

I also get the PerfDiag logger error in the exact timing as the VSS, Session "PerfDiag Logger" failed to start error: 0xC0000035 Event ID 2 this also occurs randomly and usually on restart shutdown in the same timing as the VSS error.

Although the difference is now no more VSS errors. Before I was having sometimes 21 after only a single restart all at the same time. Now is none. I know system restore is working perfectly fine and the restore points are created successfully.
Need to investigate what is causing "PerfDiag Logger" failed to start error: 0xC0000035 on restart/shutdown it is a similar superficial bug.
Microsoft need to fix this, unfortunately their latest August update hasn't fixed these errors yet. Using your bat file for now and setting the gpedit script is the best solution.

VSS errors 8193 - 13 is always unsolved!

Yes , we know , ms still did not fix it ...............better have a look in this forum , some weeks back , theres a very good working solution , to avoid this garbage..........

@pietcorus2
Thank you! Your suggestion to use "Shanedh65" .bat file worked for me!

Grrrrrrrrrrr................

.....????.....

So , still not solved............will they ever.......??

Maybe next Win10-version , next month....