VSS Event ID 12293: 0x8000ffff Catastrophic failure

Antonio Ceccato 6 Reputation points
2021-09-18T21:35:55.693+00:00

Hello,

I'm running Windows 10 Pro 19042.1110.
After some weird behaviors I noticed (an MSI installer that wouldn't ever go further than the first preparation window, plus an extreme event today in which, after plugging in a USB SD card reader, multiple devices got disabled/unrecognized including one of my secondary drives), I checked the Event Viewer and found multiple instances of this error:

Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::IsVolumeSupported() failed with 0x8000ffff [hr = 0x8000ffff, Catastrophic failure].

Operation:
Check If Volume Is Supported by Provider
Add a Volume to a Shadow Copy Set

Context:
Execution Context: Coordinator
Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
Volume Name: \?\Volume{cc00bf99-eb73-4799-81b2-b311f10d500f}\
Execution Context: Coordinator

\?\Volume{cc00bf99-eb73-4799-81b2-b311f10d500f}\ is my C: volume.

Once I started reading about VSS, I tried opening "System Protection" or "Create a restore point" and got this error plus a set of three additional errors, identical to the one above, but there was one for each of my drives/volumes (C:, D:, E:).

One major thing I noticed is that "vssadmin list volumes" returns "No items found that satisfy the query". On another working system, this command returns at least the C: volume.

This system has been working fine since April, when I rebuilt it. No major software installations were done lately (apart from Wireguard updates), nor do I use utilities like CCleaner.
I don't have backup software installed, since they seem to be often related to this error.

I already tried DISM, SFC and various other suggestions I found online (like a missing "UpperFilters" registry key) to no avail.
Running a disk check throws an error and logs the same error in the Event Viewer. Running an offline disk check makes no difference.
I also tried enabling VSS debug tracing via registry, but the trace file never showed up.

Update: it also now decided that it doesn't want to shutdown... It looks like it's doing its thing ("shutting down" screen) but then, after a brief black screen, the desktop pops back in and automatic startup applications are started!
The error in event viewer is: volmgr Event ID 45 "The system could not sucessfully load the crash dump driver."

Any suggestions on how to troubleshoot this issue?
Thanks

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,618 questions

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Docs 15,141 Reputation points
    2021-09-19T04:28:18.643+00:00

    Run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive:

    https://www.windowsq.com/t/bsod-posting-instructions.17/
    https://www.windowsq.com/resources/v2-log-collector.8/
    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    .
    .
    .
    .
    .
    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .

  2. Docs 15,141 Reputation points
    2021-09-19T21:09:26.167+00:00

    Endless time can be spent troubleshooting systems that have unexpected behavior.
    So consider starting with a clean install at times to be an excellent start.

    If you still want to troubleshoot then you can run:

    https://www.bleepingcomputer.com/download/farbar-recovery-scan-tool/
    (Please post share links for each text file)

    Run administrative command prompt: vssadmin list writers
    (post a share link)

    Run:
    https://www.lifewire.com/free-bootable-antivirus-tools-2625785
    (post share links from three different software (they have different databases)

    How come Windows Recovery Environment was disabled?

    There were many BSOD.

    .
    .
    .
    .
    .
    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .

    0 comments
  3. Limitless Technology 39,356 Reputation points
    2021-09-20T13:15:15.413+00:00

    Hi there,

    I can see the number of issues you are facing, I would recommend you to try the In-place update or the best clean install to sort this out.
    If your Windows 10 installation is demonstrating unusual behavior such as built-in apps not working or launching, you can perform a repair upgrade to fix the problem.

    https://answers.microsoft.com/en-us/windows/forum/all/how-to-perform-a-repair-upgrade-using-the-windows/35160fbe-9352-4e70-9887-f40096ec3085?auth=1

    If an Answer is helpful, please click "Accept Answer" and upvote it : )

  4. Maxym Zayarnyuk 1 Reputation point
    2023-03-22T13:07:29.2266667+00:00

    looks like related to :

    https://www.reddit.com/r/Dell/comments/78abzl/beta_feature_in_windows_update/

    https://social.technet.microsoft.com/Forums/en-US/9054b832-d001-4543-b3b0-bcbb729d5f24/esediskflushconsistency-win10-1709?forum=win10itprogeneral

    I think something with access rights can be too;

    disable indexes looks like not help;

    looks like depends if use app like acronis or easeUS backups;

    on some corruption no app but provider still there;

    tried install - uninstall that toll and now have onlu ms vss provider but if disable protection in settings got that errors;

    will recheckand try to find solution;

    how to check why it try access that volume;

    maybe is uefi or not partiontion or gpt etc

    0 comments