VSS Event Log Errors: Event IDs 8193 and 13

After upgrading to Windows 10 v1903, two VSS error entries appear in the Application event log during every shutdown. The Event IDs are 8193 and 13 with the event source as VSS. Along with the two error logs, an informational event (ID: 8224) is also recorded during the user session instead of shutdown. Here are the sample events:

Log Name:      Application
Source:        VSS
Date:          5/22/2019 10:43:47 AM
Event ID:      13
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-JKJ4G5Q
Description:
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.


Log Name:      Application
Source:        VSS
Date:          5/22/2019 10:43:47 AM
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-JKJ4G5Q
Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x8007045b, A system shutdown is in progress.

Log Name:      Application
Source:        VSS
Date:          5/22/2019 11:14:56 AM
Event ID:      8224
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-JKJ4G5Q
Description:
The VSS service is shutting down due to idle timeout. 

VSS Event Log Errors in Windows 10: Event IDs 8193 and 13

It appears that some program or service is trying to start the VSS service during shutdown. Some users say that Acronis True Image or Macrium Reflect cause this. However, the above errors occur in one of my Windows 10 computers where none of the two imaging tools are installed.

The oldest VSS errors (ID: 8193 and 13) date back to May 22, 2019 10:43:47 AM — i.e., within hours after I upgraded to v1903. These errors don’t seem to appear when you shutdown the computer with Fast Startup enabled.

event viewer error - event id 8193



The error code 0x8007045b (return code ERROR_SHUTDOWN_IN_PROGRESS) translates to A system shutdown is in progress. However, it’s unclear what is invoking VSS during the shutdown. I plan to run a boot trace in one of the systems to see if I can find anything. Another thing some users observed is that the automatic Restore Point creation does not work, but creating restore points manually works. Also, turning off the System Restore protection feature stopped the VSS errors from appearing in some systems.

Workaround: Stop the “CryptSvc” service manually before shutdown

I can confirm that the following workaround of stopping Cryptographic Services manually before shutdown prevents the VSS errors from appearing. You can do it by creating a Windows Batch file with the following contents, and run it as administrator.

net stop cryptsvc
shutdown /s /t 0

I shall post more details on this issue if I find anything interesting. Watch this space for further updates.


One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.

1 thought on “VSS Event Log Errors: Event IDs 8193 and 13”

  1. After trying two other solutions posted by others including Microsoft personnel and none of them solved a problem that I encountered, this site finally gave me a solution. Yes, my case involved 2 error codes for VSS (Volume Shadow Copy), 13 and 8193. One service item was set as ‘manual but was not running so I let Service run; other was set automatic and running so I changed to manual. In other words, both are now set ‘manual’ and running. After pc got restarted the Event Viewer shows no logs error. Problem Solved! Thank you!

    Reply

Leave a Reply to BlueUniverse1 Cancel reply