Windows 10: Windows 10 VSS Event ID 13

Hi,


I recently got this error, and haven't found a similar question asked. If anyone knows if this is serious or how to fix I would love to hear it, of course.


VSS Event ID 13

Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.


Thank You!

:)

 

VSS Errors 8193 and 13

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.

 

VSS Errors 8193 and 13

O.K. - I just used Macrium to make a backup and the Event Viewer did not report a VSS error 13 or 8193.

However, after a reboot from running Macrium backup software the VSS errors 13 and 8193 did appear in the Event Viewer.

The problem isn't with the Macrium software, it is with the actual Volume Shadow Service not fully shutting down no matter what is using it such as Windows Backup or Acronis or Macrium.

I was using the Windows Steps Recorder; however, during a reboot, the recorder cannot continue to run to record the actual service not shutting down properly.

I think it has already been established that the Volume Shadow Service is the problem and a possible workaround would be to manually shut the service down before a reboot or shutdown of the computer. We shouldn't have to do that, so ultimately it would fall into Microsoft's hands to apply a patch to shut down the VSS application correctly after a program uses it.

 

VSS Errors 8193 and 13

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. *Think