EyeInTheSky, so far I rebooted 3 times and haven't gotten any VSS errors, appears that this thing is fixed but probably, is to soon to really know. Need more reboots and shutdowns (I havent done one of this yet) to be certain. Time will tell. Perhaps, other members can tell if they seen any errors after updating.
Bo
COM+ Event System is set to use LocalService in 1809, and 1809 doesn't have the issue.
If a System Restore Point is created, either manually or through Task Scheduler, Event ID 13 and 8193 will be triggered on shutdown.
VSS is not running at that point.
However, one thing I've found in testing that seems to affect Event ID 13 and 8193, is starting VSS before shutdown.
In an elevated Command Prompt:
net start vss
It's a 1903 issue for some, but not everyone.
Just started 1903 this morning , applied latest updates yesterday evening , no errors .
After updating my Office , rebooted and ...............bingo , VSS id=8193 and id=13 , very sad............
O.K. - so what is the result of starting VSS before a shutdown that Event ID 13 and 8193 display differently? Do you get a different error altogether?
I thought it was established earlier in the thread that the VSS service was not closing properly after a backup (whether backing up manually or not), so I'm assuming trying to start it manually (VSS service) when it never shut down/closed properly to begin with, it would throw an entirely different error in the logs.
EDIT:
I can't even force the errors 13 and 8193 to occur since I assigned the COM+Event System Local Account authority.
I honestly don't know why some people are getting them and others are not because there is no one stone that is killing these errors. I also don't understand how I was able to fix it on my system and we all have the COM+Event System service on our machines; yet for others adjusting that service, it doesn't work.
Last edited by EyeInTheSky; 12 Jun 2019 at 08:49.
" VSS service was not closing properly "..............its set to manual ( disabled) after booting , will start when making restore-point.
It will stay enabled untill you reboot , then after reboot its disabled , manual again.
I have my settings the way you adviced , still sometimes ( !!!!???) these errors back in eventviewer ..............
Its almost driving me nuts , why sometimes appearing these errors and sometimes not...............???????
What is triggering these errors.....??? ( if we knew this , then a final solution can be found !)
btw; can not back to the way it was set , before I made the changes , you adviced ( Com Event and Volume Shadow-services )
I understand how the service works. The problem that is making this way more complicated than it is, is the diversity in how people have their systems set up.
Also, I never said to mess with the Volume Shadow Copy Service settings; I was just asking how the settings were set for some people.
The only thing I said I changed in post #145 was the COM+Event System service.
If you can't change them back, then that may have had something to do with the latest update maybe, because I can change the COM+Event System back to the way it was no problem and my event ID 13 and 8193 problems come back.
ok, so setting them back the way they were , does not help us either !
Then WHAT is triggering these errors , what is " routine CoCreateInstance. hr = 0x8007045b " .........?? There must be a reason why these ids ( 8193 and 13 ) sometimes / sometimes not appear ........
Very good question. I think if some answers come about as to what the heck CoCreateInstance with its code is, we might get somewhere. Then again, I think if we knew, we would probably wish we never found out because it is obviously something that can't be fixed on some users computers at this point in time.
Microsoft explains it here, but mentions nothing of an error code being associated with it:
https://docs.microsoft.com/en-us/win...createinstance
Which makes me wonder if these errors we're seeing are a routine call stacking error problem.
I just dont want to ignore these errors , many people advice to do so , because I never had these errors before.........
Just made a restore-point ( my first in1903) , placed on an internal HDD-partition , went fine and no errors in the eventviewer.......
What bothering most is the fact ; these errors appear "unpredictable"............!
I agree. Usually errors in the log have a specific reason that triggers them and these VSS errors are suggesting possible system instability in other areas of the system.
Now you got me wondering about the integrity of the system. I haven't run SFC since I got the Cumulative Update installed last night, so I'm going to do that now.
Quote
