VSS Errors 8193 and 13

[QUOTE=bo elam;1652821]It took two days after recent MS update to get the errors again, but they are back. pietcorus2, when you ran sfc /scannow, did the result show errors or not?

Hi Bo, I have run SFC, Dism, check disk many times and they always come up clean. There still are not many posts about this issue after 1903 upgrade. I would think there would be more people complaining of this. I would like to know if pietcorus2 had errors or not also. I have just given up really looking for an answer to this. If it is a windows problem perhaps they will catch and fix it.

- - - Updated - - -

Shanedh65 said:

I just did an experiment and clean installed 1903. After a restart both vss errors have returned. I only installed chipset and Nvidia drivers. I am now thinking I am going to abandon 1903 and return to 1809 until this thing is fixed.

So it has to be a Windows error but why are there not many complaints I wonder.

humbird said:

Hi Bo, I have run SFC, Dism, check disk many times and they always come up clean. There still are not many posts about this issue after 1903 upgrade. I would think there would be more people complaining of this. I would like to know if pietcorus2 had errors or not also. I have just given up really looking for an answer to this. If it is a windows problem perhaps they will catch and fix it.

Hi Humbird, the internet is not loaded with people complaining about this issue but I found a thread from early in the year in a German forum, and a post here at tenforums in an insider thread about this issue in 1903. The issue was identical in those threads than what we have reported and described here. Microsoft knows about it.

Why they dont fix it but fix things that sounds less important (like Night light), I dont know. In my personal case, my W10 is running great, the errors dont affect anything I do, and I am happy to have updated to 1903. I didn't like 1809, but I like this version. I rather have 1903 with this errors than 1809 (updated twice to it, and reverted twice back to 1803) without them. If I was to revert, I ll have to do it to 1803 (my favorite W10 version), but as we know, its becoming old. So, I am willing to live with this errors. Is possible MS continues to ignore fixing this errors, as they done with other errors in W10, and is also possible that if they are not fixed in 1903, they get fixed in the next upgrade 6 months from now. I am not going to let this errors bother my computer experience.

I like to hear what pietcorus2 has to say about what I asked him, but I am not willing to change Services when my services are set the same as users who don't experience the issue have theirs set.

Greetings

Bo

Hi EyeinTheSky. Yep that is what mine (Com+Event System and Volume Shadow Copy service) look like. Already had checked your posts. I am mot too worried . I am only seeing these when I shut down after an update to windows and I think Windows is failing to close VSS before shut down. It is only after an update. It is not preventing backing up with Macrium so guess I will just hang tight till they get it fixed.(one of these days)

- - - Updated - - -

bo elam said:

Hi Humbird, the internet is not loaded with people complaining about this issue but I found a thread from early in the year in a German forum, and a post here at tenforums in an insider thread about this issue in 1903. The issue was identical in those threads than what we have reported and described here. Microsoft knows about it.

Why they dont fix it but fix things that sounds less important (like Night light), I dont know. In my personal case, my W10 is running great, the errors dont affect anything I do, and I am happy to have updated to 1903. I didn't like 1809, but I like this version. I rather have 1903 with this errors than 1809 (updated twice to it, and reverted twice back to 1803) without them. If I was to revert, I ll have to do it to 1803 (my favorite W10 version), but as we know, its becoming old. So, I am willing to live with this errors. Is possible MS continues to ignore fixing this errors, as they done with other errors in W10, and is also possible that if they are not fixed in 1903, they get fixed in the next upgrade 6 months from now. I am not going to let this errors bother my computer experience.

I like to hear what pietcorus2 has to say about what I asked him, but I am not willing to change Services when my services are set the same as users who don't experience the issue have theirs set.

Greetings

Bo

Hi Bo , yes that is the way I feel. I am not having any hiccups at all and I like 1903 better too. I get that! Lets fix night lite but not VSS. Lol that's Microsoft for you. Only reason I even knew about the errors at all is I have a habit of checking event viewer after updates. Maybe I will quit that unless I am having obvious problems. :)

Congratulations !
Just made a new sfc /scannow and Dism-repair health , also chkdsk c: /r .......will see !
Im not going back to 1809 anymore ( like I did before ) , for these errors , that wont help .
MS finds it clearly not important enough , for fixing these VSS-errors !!
Problem is ; these errors dont always occur , sometimes they do , sometimes you dont see them anymore .
These errors are the most difficult to repair.............

Shanedh65 said:

I just did an experiment and clean installed 1903. After a restart both vss errors have returned. I only installed chipset and Nvidia drivers. I am now thinking I am going to abandon 1903 and return to 1809 until this thing is fixed.

On your clean install did you format windows ?

humbird said:

On your clean install did you format windows ?

Hi, yes I deleted the partition and formatted before installing. I am also looking at updating all drivers and a new bios update to see how it helps.

f14tomcat said:

Check them regularly. No VSS errors. 1809, 1903, or any Insider.

I have been checking Microsoft Forums insiders thread and the 1903 Mega thread on Reddit. The posts in the mega thread are over 1.3k strong and not one has said anything about vss errors. Most of them on Reddit in the mega thread are insiders and if any were having this problem they would say so. Same on Microsoft forums. I have found a handful of older posts about this but the fixes mentioned have not applied .
There is one upvote in Feedback hub on my post. Of course this upgrade is rolling out slowly but you really would think that some insiders would have seen this error. It really makes no sense that not one has reported this error for 1903. So I may be doing a format and fresh install after more of the issues are fixed. I keep thinking it may be something in common that us few people here have in common in our setup. Ah well as long as there are not many with the error microsoft will never fix it because it is not a common error which points to a bug in the operating system. There has to be a lot of people with the same error for them to recognize it as a bug. Maybe as it rolls out more will show up with the error.