VSS Errors 8193 and 13

pietcorus2 said:

Good question , have seen reports of many people who made clean install ................VSS-errors came back , sometimes even after a few days !! Tried everything , nothing did the trick !
Only MS can fix it , so we have to wait.........( how long ??!)

Hi pietcorus2. Got to be patiently impatient. Anyway, thats my attitude with this things.

Bo

I have not seen the errors yet but it has only been 1 day since the in place repair so who knows. I still think because it is so few of us that it may be some configuration that we have in common. Of course that idea would be too hard to hunt down. There would be many more people complaining of this if it was linked to the 1903 upgrade. It is something that did not show up for us in 1809 but the configuration for 1903 set it off in our systems. One person in this thread did a clean install though and reported still having the error so who knows what it can be. It does not seem to have any bad effect though. Still keeping my eyes open for the error although I was only getting them very occasionally, (like 5 to 6 days without them).

- - - Updated - - -

EDIT 6/19

Something interesting in these errors. I just updated the newest cpu microcode and on reboot seen the 2 errors again. First time since I did the inplace upgrade. This happened when the installer requested the reboot. So it seems that Windows may not be getting the VSS ready for a reboot to system updates ( for me anyway) The error vss cannot be started, system shutdown in progress. So anyway even though I do not seem to see them on a regular basis, they occur with windows updates for me. I can correlate them with every update I have done.

" I can correlate them with every update I have done. "...................this prooves its a real 1903-bug !
My system-restore is disabled for all partitions , suddenly I noticed less SSD-space on drive C ( OS) , it appeared system-restore was enabled again , without any notice or approval by me !!
Did not noticed any VSS-errors , untill I disabled system-restore and rebooted , they were both present .............
Remains the question ; what is triggering this VSS to enable its-self , while it was disabled by default !
How to turn this behaviour off ..........??

I wish I knew Pietcorus. i sure would share if I did. I ran vssadmin list writers in admin command prompt just now and all of my writers are stable . Maybe Windows is enabling to make a restore point but then not shutting it down for the reboot. Some sort of odd timing before the reboot happens. I guess I could guess all day on the issue but it still won't fix it. I am just going to have a wait and see approach as it really does not seem to be corrupting anything on my system. I never see a bad sfc and all seems to be working properly.

" Windows is enabling to make a restore point "...……………...it does !
" but then not shutting it down for the reboot. "...……………...right !
" I never see a bad sfc and all seems to be working properly. "...………...yes, agree , here also !
It seems I have to accept these VSS-errors , no choise ………..still not happy with it , coz my eventlog of previous 1809 always clean !!

All we can hope for is it gets straightened out by Microsoft. For some reason I will not hold my breath. :)

Im afraid we have to deal with these event-errors , we have to wait for MS ( reported again , feedback, etc ) ..............
If I know more in future will let you know !

..and I will of course let you know.

For me, stopping the Cryptographic services before restarting or shutting down Windows has eliminated all of my vss errors. I need to stop the service before restarting. If I don't stop Cryptographic services they return. Easiest way to stop Cryptographic services is to create a batch file to stop the service.

Shanedh65 said:

For me, stopping the Cryptographic services before restarting or shutting down Windows has eliminated all of my vss errors. I need to stop the service before restarting. If I don't stop Cryptographic services they return. Easiest way to stop Cryptographic services is to create a batch file to stop the service.

Yes, I had read earlier on that you were doing that. So it seems that Cryptographic services seems to be the culprit here. Did you make a batch file for it then?