VSS Errors 8193 and 13

bo elam said:

I uninstalled Feedback hub when I got my W10, and could reinstall it, but, is it required to have a Microsoft account to use it to for reporting issues? I don't have an account, and I really don't want to sign up for one.

Bo

I was able to report the issue without signing in to my Microsoft account. So I don't think you need an account to report an issue; however, the reason I used it with my Microsoft account was so that the issue would be escalated by up-votes.

On a side note, I did however notice that you need an account to download certain items from the Windows Store that previously didn't require an account in the past to download.

Obviously this is done in tiers.

No Account/Microsoft Account/Microsoft Account Insider; with the very latter having more recognition when a problem is reported.

It seems some people dont have these VSS-errors at all , so if we could compare there VSS , with someone with the errors we can find out whats triggering the errors.
Clean install or just upgrade , with software in tact, Windows Restore enabled/disabled , etc, someone has these errors/ others dont..........
Im sure its a Windows1903-bug , but still there must be a reason why they appear/not appear ......
( next tuesday , cumulative update......with a fix ??? Would be awsome , then I will finally upgrade for good !)

pietcorus2 said:

It seems some people dont have these VSS-errors at all , so if we could compare there VSS , with someone with the errors we can find out whats triggering the errors.
Clean install or just upgrade , with software in tact, Windows Restore enabled/disabled , etc, someone has these errors/ others dont..........
Im sure its a Windows1903-bug , but still there must be a reason why they appear/not appear ......
( next tuesday , cumulative update......with a fix ??? Would be awsome , then I will finally upgrade for good !)

Patch Tuesday updates are usually only Security Updates, but maybe you'll get something for this.

BTW... I don't have any of these VSS errors anywhere, and don't recall ever seeing prior in any previous version. Just FWIW.

I changed this service:



To look like this:



You want the COM+Event System in services to be set to a Local System Account. Make sure the "Allow service to interact with desktop" is not checked. This setting is found in the "Log On" tab.

For some reason Version 1903 switched the service to a "This Account" status with a password and I compared it to a backup of a previous Version of Windows 10 that didn't throw these VSS errors.

So to test the new settings, I made a backup and rebooted and now I have no VSS errors in the Event Viewer:



Hope this works for others.

That, Mr. Eye, is very interesting. Maybe a comparison of what you had, and what you changed, to what I already have (I never touched it, honest!) may shed some light. And maybe another solution. Mine looks just like your "before" pic, but has Local Service pre-filled. Yours was blank. I've never had the errors....ever. Hmmmmmmm.......

f14tomcat said:

That, Mr. Eye, is very interesting. Maybe a comparison of what you had, and what you changed, to what I already have (I never touched it, honest!) may shed some light. And maybe another solution. Mine looks just like your "before" pic, but has Local Service pre-filled. Yours was blank. I've never had the errors....ever. Hmmmmmmm.......

That is the difference. "This Account" did not have "Local Service" in the field parameters, and I have no doubt that was the problem.

EyeInTheSky said:

That is the difference. "This Account" did not have "Local Service" in the field parameters, and I have no doubt that was the problem.

Let's wait for some of the other "victims" to come back, and cross check. I think you unearthed it, though.

sportsfan148 said:

I updated to 1903 from 1809 through Windows Update a couple of days ago. I have System Restore turned on, Fast Boot turned off, Hibernation Disabled. I too am seeing the VSS errors in Event Viewer

Check my post #145 for a possible solution.