VSS Errors 8193 and 13

Page 38 of 41 FirstFirst ... 283637383940 ... LastLast

  1. Posts : 773
    Windows 10 Home x64 - Version 21H2 (OS Build 19044.2006)
       #371

    parsonm said:
    I did it after the 18363.752 update, so we will have to wait for the next update to see what happens.
    I got the VSS error 13 after upgrading to build 18363.815

    I'm going to have to look at the DIAG permissions again to see if they reset after the upgrade. Obviously they did, so it looks like the fix I had in place and was working, got wiped out by the upgrade to the new build number.

    If you recall, the DIAG permission change alone worked for me that you suggested. I didn't have to change anything else.

    After the build upgrade, I noticed the "Only apply these permissions to objects and/or containers within this container" was unchecked, so I rechecked it like in the article you linked - The upgrade unchecked it and I know for a fact I had it checked like in my snap-shot.

    VSS Errors 8193 and 13-diag.jpg
    Last edited by EyeInTheSky; 23 Apr 2020 at 11:54.
      My Computer


  2. Posts : 71
    Windows 10 Home Premium v21H2 64bit OS Build 19044.1889
       #372

    Yes, my system reverted as well giving duplicate entries again for both Event ID's. I tracked one of the problems down to a change of permission for the Volume Shadow Copy Service in DCOMCNFG.Under launch and activation, the Local Service had " local activation" not set, although local launch was. I know it was as I kept a record of what I had done. Having changed it back, I have again lost the duplicate entries.
      My Computer


  3. Posts : 211
    Windows10 21H2 x64 Home, Single language, build 19044.1706
       #373

    I am still running that Task at shutdown (Type : On Event Basic, Log : System, Source : User32, EventID : 1074) that stops CryptSvc: 1 week now and no errors (no critical, no errors, no warnings). I also installed the last update KB4550945 without problems. The task return code is constant: 0x0, no issues.
      My Computer


  4. Posts : 773
    Windows 10 Home x64 - Version 21H2 (OS Build 19044.2006)
       #374

    Just saw this for Macrium Reflect backup bug fixes. Maybe it wasn't Microsoft's job to fix this one after all. I wonder if this patch will fix some folks VSS errors?

    VSS Errors 8193 and 13-macrium.jpg
      My Computer


  5. Posts : 1,862
    Windows 10 Pro 2004 20H1
       #375

    The VSS issue seems to be resolved in Windows 10 2004.

    I was unable to reproduce it using the same testing paths in 1909.

    However, there are currently several issues with 2004 -

    https://docs.microsoft.com/en-us/win...indows-10-2004

    Known and Resolved issues for Windows 10 May 2020 Update version 2004

    After a couple days of testing, I rolled back to 1909.
      My Computer


  6. Posts : 655
    Windows 10 Home
    Thread Starter
       #376

    OldNavyGuy said:
    The issue seems to be resolved in Windows 10 2004.
    Yes, I think so too. I haven't gotten any VSS errors since the update to 2004 last Thursday 28th of May.

    Bo
      My Computer


  7. Posts : 1,961
    Windows 10 Pro x64
       #377

    Finally.........pfffffff, after 6 months MS fixed it !!
      My Computer


  8. Posts : 211
    Windows10 21H2 x64 Home, Single language, build 19044.1706
       #378

    pietcorus2 said:
    Finally.........pfffffff, after 6 months MS fixed it !!
    Not on my system W10-1909 x64 Home. I disabled the task that stops CryptSvc at shutdown and right now got the two VSS errors back out of the blue, no backup or restore done in weeks.
    VSS Errors 8193 and 13-vss2.pngVSS Errors 8193 and 13-vss1.pngVSS Errors 8193 and 13-vss.png
    I will turn on the task again.
    Frank
      My Computer


  9. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #379

    FrankW said:
    Not on my system W10-1909 x64 Home. I disabled the task that stops CryptSvc at shutdown and right now got the two VSS errors back out of the blue, no backup or restore done in weeks.
    VSS Errors 8193 and 13-vss2.pngVSS Errors 8193 and 13-vss1.pngVSS Errors 8193 and 13-vss.png
    I will turn on the task again.
    Frank
    He was referencing it was fixed on 2004, you are still on 1903/1909.
      My Computers


  10. Posts : 773
    Windows 10 Home x64 - Version 21H2 (OS Build 19044.2006)
       #380

    f14tomcat said:
    He was referencing it was fixed on 2004, you are still on 1903/1909.
    And........even more intriguing; and yet confusing, it was something more than just a bad piece of code associated with the Cryptographic Service. The errors were hit or miss on my system even if the Cryptographic .bat file that was posted earlier in the thread for Pro users was used religiously. I modified the .bat file to a Hot-Key configuration so that every shutdown stopped the Cryptographic Service first because Windows 10 Home users could not automate the .bat file like the Pro users could because of the lack of the Group Policy Editor.

    Even the task scheduler lacked the authoritative power to run a .bat file at shutdown for Home users that liked to tweak tasks with the scheduler.

    This is what the Home Users modified .bat had to look like in order to automate it and as I mentioned, I set it to a Hot-Key configuration in order to automate it further. I had to first create the .bat file and then make a shortcut for it and the tricky part was finding a place in the system that allowed both the shortcut and actual .bat to exist in the same directory which ended up being this:

    C:\ProgramData\Microsoft\Windows\Start Menu\Programs

    This is the actual .bat file:

    net stop cryptsvc
    shutdown /s /t 0


    So when I posted what Macrium Reflect had patched in post #374, I thought the problem would go away; because as I mentioned, there was something going on other than a bad piece of micro-code.

    Still the problem persisted with or without use of the Crypto .bat file. and the Macrium patch.

    So if Microsoft has this fixed in the 2004 upgrade, then obviously it was entirely on their end and long overdue to actually acknowledge it was a problem. But then again, I'm still left wondering why my system would go weeks without producing the errors (I shut my computer down every time I'm done with it) and then some days throw the errors every shutdown.

    There was no systematic way to troubleshoot the error because it did not occur on any based set of rules on my system. They would occur whether or not the .bat file was used or not. They would occur whether or not there was a backup done or not. Whether a restart was done or not. No set of parameters in any sequence either triggered nor defined when the result would occur in the form of the VSS errors or not occur.

    It was truly a defined set of circumstances for Pro users and something else entirely for the Home users.
    Last edited by EyeInTheSky; 09 Jun 2020 at 16:08. Reason: Additional Information.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:09.
Find Us




Windows 10 Forums