It looks like these errors come up when the computer is shutting down or restarting and system restore is working. If you are sick of seeing these errors I have a solution. This will only stop the errors in the event log. Please backup before you edit the registry.
Start regedit, goto Hkey_local_machine/system/current controlset/services/vss
Change Error control from 1 to 3
Vss continues to run but doesn't display any errors.
VSS 13 and 8193 errors have been around forever.
Nothing to get overly concerned about.
As long as restore points are being created, and the points can be restored (my testing shows it does).
Keep in mind that 1903 is basically for "seekers" (people who have actively gone out and downloaded the ISO) at this time, and is on slow release.
Roll back to 1809 and wait for a patch.
Yes , errors appeared today again , did not see them yesterday , so thought all fixed !
Using " Start regedit, goto Hkey_local_machine/system/current controlset/services/vss
Change Error control from 1 to 3 "..................seems to me the best working solution ( until finally really fixed !).........
Hi there
VSS errors can occur if there's a lack of disk space in your system - I'm never sure how much space VSS requires but if it's taking a system restore point or whatever it probably needs a fair % of your current "C" drive Windows allocation.
I'm not saying that that's the cause of your problem but it's an area that IMO is worth looking at.
I'm not sure though why you need to enable system restore points --if you image your system regularly these aren't necessary at all.
Cheers
jimbo
Diskspace is out of the question , 5TB HDD space and SSD with 200GB left .
Must be other reason , strange , a real working solution seems not to be found still , while lots of people encountering these two errors in the eventviewer ( 8193 and 13 )...............
Earlier today I got a different type of VSS Error 8193. The description of the event (see picture below) is different than the description of the event when I posted the opening post. Same number (Error 8193) but different description. This time the error wasn't logged during shutdown of the computer but a while after the computer had booted. I think this time, there is a hint of why the problem is taking place.The last 3 words of the description (Controlador no valido) means "The driver is not valid" or something like that. The Spanish Microsoft uses in computers is terrible, is as bad or worst than translated movies. But is likely, its referring to a driver. Note. Nothing looks out of order or with yellow flags in Devices.
In the picture below, it can be seen in Events log, that this Error 8193 took place immediately after a System restore was attempted to be created automatically by the system. According to the Event (left picture, bottom), the restore point was created, but it wasn't (look at picture of System restore at Right hand.
So, I gather, this issue don't allow the system to create System restore points automatically. A few days ago I had noticed this but wanted to make sure that indeed this was happening, so I was in the lookout to see if it happened again, and now I know for sure that the system cant create points automatically. I also know, that points can be created manually, and according to what I saw today, the points created before an error, are not being deleted when the error takes place.
I dont want to test to see if points created before an error takes place, are still good, not corrupted. Perhaps they become corrupted, I dont know. But it would be nice to know whether they become corrupted or not.
I hardly ever use System restore, perhaps once a year. In the 2 years I had W10, I used it once. My computer is static. No changes from my end. But I usually keep 1 and after 10 days or so I delete it and create a new one. Thats my routine with SR.
Hopefully, 1. OldNavyGuy is correct when he confirmed that points can be restored (link below), and 2. Microsoft does something about this issue as a lot of users depend on System restore and the issue probably affects a large amount of users.
VSS Errors 8193 and 13
Bo
.
The second Event Log error you posted is for Event ID 8194, not 8193.
As mentioned previously, I am able to create restore points both manually and automatically, and restore them.
That doesn't mean it will work for everyone.
Making frequent disk images, and backing up personal data on a daily basis is your best defense against any type of issue.
And still NO real solution , MS should take action , there are maaaaany people with these errors.............!!
btw; after setting " Error Control " from 1 to 3 ( VSS in regedit ) , Im stil getting 8193 and 13 ...!!
Maybe we should set this key from 1 to 0 ????
Even though I am not seeing these errors anymore I have been searching for an answer that makes sense but this does not seem widespread . Maybe as more people get 1903 there will be more questions asked about this error and maybe an answer, or a forthcoming fix from Microsoft. It seems a bit weird that not many people are reporting this and makes me think it is (was) in my case a configuration error in our systems. I did mention that I deleted all backups and formatted my external usb ssd . Then deleted restore points and created a new one. Then I clean reinstalled Macrium and made new backups. I also set the core scheduler in windows because it was set incorrectly to protect me from CVE-2018-3646. The only things I have really found on the errors were some pretty old posts and had to do with user.bak account in the registry. I have checked and did not have that entry . So hopefully something comes along about this .
Quote
