VSS Errors 8193 and 13

sportsfan148 said:

Just to let you know. I did a clean install of 1903 and the VSS errors still pop...not on a daily basis but Im still seeing them

clean install which build of 1903 (build 18362.30 or 18362.175), sportsfan148?

I seem to have gotten those VSS errors 8193 when installing 1903 (18362.175) from custom install media created from a uup dump using uup to iso converter or W10ui batch tools from abbodi of MDL forums [I could not install any new CUs and get error 0x800f0988 when trying to do so]. I ended up downloading a "1903 refresh" (build 18362.175) ESD directly from MS and created an ISO image and clean installed from that one but this time I still get those VSS 8193 errors but much less frequently than before. and installing the KB4501375 (build 18362.207) update seemed to have kept them at bay for now - I'll have to check again in July to see if they come back or not

humbird said:

Ah well spoke too soon. They are still there after all. Last night I shut down and took a look this morning. Well dang it anyway. I am glad I make regular backups. At least it doesn't seem to affect anything else. Let me know if you see it again. I am reluctant hide it and would rather just ignore. I would like to watch it to see if it gets fixed at some point.

I also got them at last night shutdown. So, they still here after update to 207. Like you, I also prefer to leave them alone and ignore them rather than hide them.

Bo

bo elam said:

I also got them at last night shutdown. So, they still here after update to 207. Like you, I also prefer to leave them alone and ignore them rather than hide them.

Bo

I just clean installed windows. I had other issues so decided to clean it up. Don't expect vss errors to go away though. Me too I would rather see what is going on in case a legitimate fix, either through windows update or other happens I then know it is fixed. Windows is a pickle. It installed all drivers but I couldn't get my fingerprint to work for login so I had to download all drivers that are required for the reader from Huawei. So now it works.

erpster4 said:

clean install which build of 1903 (build 18362.30 or 18362.175), sportsfan148?

I seem to have gotten those VSS errors 8193 when installing 1903 (18362.175) from custom install media created from a uup dump using uup to iso converter or W10ui batch tools from abbodi of MDL forums [I could not install any new CUs and get error 0x800f0988 when trying to do so]. I ended up downloading a "1903 refresh" (build 18362.175) ESD directly from MS and created an ISO image and clean installed from that one but this time I still get those VSS 8193 errors but much less frequently than before. and installing the KB4501375 (build 18362.207) update seemed to have kept them at bay for now - I'll have to check again in July to see if they come back or not

Hi erpster4, My clean install was 18362.175. I did a full clean install..deleting all partitions etc. I downloaded the ISO using the media creation tool, mounted it and copied across onto a USB flash drive. Ive only had a few of those VSS errors so far but I am still getting them. I was offered CU KB4501375 this morning but Ive chosen not to install it so Im still on OS build 18362.175

With the solution of Shanedh65 you dont hide the VSS-errors , but you eliminate them for good ! The errors just dont occur anymore coz you stop the Crytographic Services BEFORE the reboot/shut-down .
So , there is a big difference between "hiding" ( they still excist !) , or eliminate them ( they just dont occur anymore )...............

pietcorus2 said:

With the solution of Shanedh65 you dont hide the VSS-errors , but you eliminate them for good ! The errors just dont occur anymore coz you stop the Crytographic Services BEFORE the reboot/shut-down .
So , there is a big difference between "hiding" ( they still excist !) , or eliminate them ( they just dont occur anymore )...............

Ah yes that would be true. The darn thing with windows is though you never know when you may , unknowingly, break another part of it. It does seem a good fix for you the time being though. I do hope Microsoft fixes the VSS errors though as they are a bit worrisome.

" I do hope Microsoft fixes the VSS errors though as they are a bit worrisome. "............for sure !
But MS seems to be not in a hurry for fixing these evenlogs , you can easily use the gpedit-fix , coz you dont change anything and very easy to undo this fix.
Will use it untill MS will wake up and make things right.................

humbird said:

Ah yes that would be true. The darn thing with windows is though you never know when you may , unknowingly, break another part of it. It does seem a good fix for you the time being though. I do hope Microsoft fixes the VSS errors though as they are a bit worrisome.

That's why I don't want to manually apply the fix either. Im not going to mess with things in case it breaks something else. Exactly like you though I don't like these VSS errors in Event Viewer one bit. They don't appear to be causing any issues that I can see so Im waiting for Microsoft to fix it (hopefully!!)

sportsfan148 said:

That's why I don't want to manually apply the fix either. Im not going to mess with things in case it breaks something else. Exactly like you though I don't like these VSS errors in Event Viewer one bit. They don't appear to be causing any issues that I can see so Im waiting for Microsoft to fix it (hopefully!!)

He he... I really do know what you mean. Windows 10 just gets more and more complicated. If Microsoft would just clean up some of the old code that lingers in it we would probably see a much better experience with it. Lol I did a complete format and clean install and still seeing all the old errors and warnings as before. I am totally up to date with windows and still I see same old **** that I have been seeing since windows 95.

humbird said:

He he... I really do know what you mean. Windows 10 just gets more and more complicated. If Microsoft would just clean up some of the old code that lingers in it we would probably see a much better experience with it. Lol I did a complete format and clean install and still seeing all the old errors and warnings as before. I am totally up to date with windows and still I see same old **** that I have been seeing since windows 95.

Don't worry mate..you're not on your own. I know exactly what you mean. My PC was a brand spanking clean install just a couple of days ago. And Im still getting one error every single morning in event viewer when I turn my PC on. Its been there forever so I know its not an issue but I haven't a clue what causes it. Ive just posted a new thread to see if anyone else is seeing it.
Anyone else get Event 2 Kernel-Event Tracing error in Event Viewer?