Windows Backups Failing with Associated VSS 8193 Errors



AskPFEPlat is in the process of a transformation to the new Core Infrastructure and Security TechCommunity, and will be moving by the end of March 2019 to our new home at (hosted at Please bear with us while we are still under construction!

We will continue bringing you the same great content, from the same great contributors, on our new platform. Until then, you can access our new content on either as you do today, or at our new site Please feel free to update your bookmarks accordingly!

Why are we doing this? Simple really; we are looking to expand our team internally in order to provide you even more great content, as well as take on a more proactive role in the future with our readers (more to come on that later)! Since our team encompasses many more roles than Premier Field Engineers these days, we felt it was also time we reflected that initial expansion.

If you have never visited the TechCommunity site, it can be found at On the TechCommunity site, you will find numerous technical communities across many topics, which include discussion areas, along with blog content.

NOTE: In addition to the AskPFEPlat-to-Core Infrastructure and Security transformation, Premier Field Engineers from all technology areas will be working together to expand the TechCommunity site even further, joining together in the technology agnostic Premier Field Engineering TechCommunity (along with Core Infrastructure and Security), which can be found at!

As always, thank you for continuing to read the Core Infrastructure and Security (AskPFEPlat) blog, and we look forward to providing you more great content well into the future!



Hi, this is Michael Koeppl again. I’m with the Premier Mission Critical (PMC) Team and assisting customers when they hit OS issues in their critical infrastructure, and today I wanted to talk with you about an interesting Windows Backup issue I encountered.

My customer realized that his System State Backups ( on one of his DCs stopped working and asked if I could have  a look.

In the Application Event Log was a prominent VSS error saying something about a ConvertStringSidToSid function which failed.


Here’s the original text for better searchability:

Log Name:      Application
Source:        VSS
Date:          27.06.2017 21:00:21
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A

Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid(S-1-5-21-2828234547-00000000000-1509355905-1125.bak).  hr = 0x80070539,
The security ID structure is invalid.

OnIdentify event
Gathering Writer Data

Execution Context: Shadow Copy Optimization Writer
Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Name: Shadow Copy Optimization Writer
Writer Instance ID: {74a61a33-665e-4041-b325-726825b2bf8e}

This was followed by a 521 Event from Windows Backup telling you that the Backup operation failed.



The hint was already in the event details from the VSS error:


Can you spot the SID with the BAK extension at the end?

So we looked at the ProfileList regkey on that machine.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

And here it is:


We followed this KB (947215) and ultimately removed the Profile with the BAK extension and started another Windows SystemState Backup, which succeeded without any errors.

The User Profile Service failed the logon. User profile cannot be loaded

Here’s an automated way to clean up the old profiles from that list.

Script to fix issues described in KB947215 (PowerShell)

Hope you enjoyed the quick excursion from VSS to profiles with an easy solution at the end.