VSS Errors 8193 and 13

parsonm said:

I did it after the 18363.752 update, so we will have to wait for the next update to see what happens.

Unfortunately, I started to get these errors again on the previous Cumulative Update and did the fix you posted only after updating to 18363.752 myself, so I'll have to wait and see also.

I could restore an older image to check the integrity of the registry to the new edits, but I'm not going to mess with something that is working.

I hope others see your posted fix because it is working and they would probably appreciate not having to rely on an automated .bat file to correct something that was obviously overlooked by us all.

Thanks again!

parsonm said:

I have to report that something strange has happened. Prior to changing the permissions as advised, I was seeing duplicate Event ID entries for 13 and 8193 in the Event Log for VSS all with identical times. After changing the permissions for DIAG and VSS, the events disappeared only to reappear a few days later but are now different. There is now only one entry for each event. The only explanation I can come up with is the fact that there were two problems both giving identical Event entries and I have solved one and the other still exists. i.e. there is only one error report for each reported event no matter what it is.

Event ID 13 refers to CLSID 4e14fba2-2e22-11d1-9964-00c04fbbb345. When looking at the Advanced Security Settings in the registry, the owner is TrustedInstaller, which also has Full control. System, Administrators, Users, All Application Packages and Account Unknown are all set to read only. There is no mention of Local Service or Network Service at all. As it was the latter that was missing in VSS and DIAG I will add and see what happens. I will report back later.

Are you getting the event entry error after doing a backup and restarting the computer or are you just getting the entry errors because of the fix itself being incomplete?

The only time event ID 13 and 8193 showed up for me is when a Macrium Reflect full backup was performed and either the computer was shut down or restarted after completion of the backup.

I have seen neither since changing the permissions on only the DIAG alone.

parsonm said:

I am not doing anything extra other than what Windows does of its own accord. The event entry errors always appear in the log after a power down and start and that has always been the case for me. In other words, as you stated, I think the errors are still being recorded because the fixes so far have not yet resolved the problem on this PC and I believe it is possibly incorrect security settings in that CLSID which I am going to investigate.

If you are getting the errors without even doing a backup, I would strongly advise doing an sfc /scannow from an Administrative Command Prompt, because after the upgrade to 18363.752 I had the lovely corrupt files that come along with each Cumulative Update.

I have had to repair corrupted files for months now after every Cumulative Update. Microsoft really needs to look into why the Cumulative Updates are corrupting system files every time there is a major revision to the OS. I'm getting sick and tired of nursing along a self destructing platform. It is ethically and professionally ignorant of Microsoft to push updates and have the integrity/audacity to state in their documentation of the update that there are "No Known Issues with this Update"

If there are no known issues with the update, then why after the update is my system corrupt? Every single Cumulative Update does it every time. As I said, it is pure and simple evidence of a self destructing platform and yet Microsoft is sitting there in the background patting themselves on the back thinking they are doing everyone a favor because there are limited options for a everyday OS without jumping through hoops for some psychotic nose picker sitting at a desk thinking this crap up.

Furthermore, the system is so corrupt after a Cumulative Update that I've had to run sfc three times in a row with restarts in-between to clear the rubbish they pushed into the system files. On top of that, a DISM command was the only thing that worked quite a few times.

parsonm said:

Maybe Microsoft got something right for a change.

Yes maybe; but for how many people?

Just the ones that they feel have important enough systems that are newer than most people running Windows 10 on older systems?

I understand Microsoft was gracious enough to offer Windows 10 free to those whose systems were compatible. My point being that if your computer passed the same tests as mine to qualify for the upgrade than why is mine suffering dire consequences of Cumulative Updates and yours is not this time?

You are running Windows 10 Home Premium - is that somehow different than just Windows 10 Home?

It is as though there is a tier system in which updates do what to whose system - yet if the system qualified for the upgrade, then obviously they had figured out what they were going to do with future updates; or maybe not.

It is like they are trying to think so far ahead that they are collapsing their own platform.