Windows 10: Windows 10: Event log full of VSS 12293 errors and System Restore fails with 0X81000203

Windows 10 Pro v. 2004 Build 19041.508



Windows 10: Event log full of VSS errors and System Restore is broken



This has apparently been going on for a long time, but the system shows no external indication of any problems. Nightly backups Acronis True Image 2021 work, with no errors in the logs.



I've tried all of the solutions suggested here and anywhere else I could think to check.



Here's all the info and evidence I can think of.



Windows 10 Pro v. 2004 Build 19041.508

The C: drive is a factory installed 1TB conventional hard drive with an Intel Optane solid state device.

The D: and E: drives are partitions on a single 1TB hard drive.



VSS services are now set to "Automatic" and are running [Default setting was "manual."]

SFC /scannow shows no problems.

CHKDSK /F of all three drives show no errors.



System Restore setting fails with 0X81000203, and the setting and display fields in the System Protection dialog are all grayed out.



[The volume mentioned in the VSS errors that I've looked at is always the D: drive.]

Numerous VSS 12293 errors in Application event log, like this:



Log Name: Application
Source: VSS
Date: 10/3/2020 8:46:59 AM
Event ID: 12293
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Dellbox-IV
Description:
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

Context:
Execution Context: Coordinator
Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
Volume Name: \\?\Volume{17319d75-0000-0000-0000-607074000000}\
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">12293</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-10-03T13:46:59.9486163Z" />
<EventRecordID>110771</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Dellbox-IV</Computer>
<Security />
</System>
<EventData>
<Data>{b5946137-7b9f-4925-af80-51abd60b20d5}</Data>
<Data>IVssSnapshotProvider::IsVolumeSupported failed with 0x8000ffff</Data>
<Data>0x8000ffff, Catastrophic failure
</Data>
<Data>

Operation:
Check If Volume Is Supported by Provider

Context:
Execution Context: Coordinator
Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
Volume Name: \\?\Volume{17319d75-0000-0000-0000-607074000000}\</Data>

:)

 

System Restore Error 0x81000203 - can't create shadow copies

Please help me to diagnose and fix my VSS errors. Symptoms include:

• When visiting the System Protection tab in System Properties, I get the error message: "There was an unexpected error in the property page. System Restore encountered an error. Please try to run System Restore again. (0x81000203) Please close the property page and try again."
• In the event log I get an error with event ID 12293: "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 ProviderContext: Execution Context: Coordinator Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5} Volume Name: \\?\Volume{48a79008-0000-0000-0000-100000000000}\

The Volume ID refers to my system volume.

So far, I have tried the following:

• vssadmin list writers — no errors shown
• sfc /scannow — no errors found
• chkdsk c: /f — no errors found
• I've even done a repair install of Windows, which didn't fix it.
• I enabled VSS tracing (trace attached), which identified at least the following errors:
  • THROW[CVssMachineInformation::GetMinDiffAreaOnVolume] Could not send the IOCTL 0x00534058 on device \\?\Volume{48a79008-0000-0000-0000-100000000000} - 0x000001cc. [0x00000001]
  • Cannot retrieve minimum diff area for volume \\?\Volume{48a79008-0000-0000-0000-100000000000}\ [0x8000ffff]. Using the default value 335544320

However, despite plenty of googling, I'm none the wiser at trying to fix those errors, and I'd be grateful for any help.

Thanks in advance.

 

Help With Macrium Reflect - VSS Errors

Hi, what's your Windows build number? The forum prompted you for this so we don't have to keep asking.

Suggest you start with basics:
a. Disk- Run HDTune v2.55 (free) - Health and Error Scan tabs.
b. If ok run
chkdsk c: /scan
from an admin command or Powershell prompt
c. If ok similarly run
sfc /scannow

and post the summary result.

If those pass, your physical disk and file system and system files are ok.

See e.g.
[SOLVED] Recurring VSS error in event log with event ID 12293 - Windows Server - Spiceworks
- makes reference to truecrypt volumes; similar could apply to veracrypt.

(I searched using your error message
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {b5946137-7b9f-4925-af80-51abd60b20d5} if volume is supported. [0x8000ffff] [hr = 0x8000ffff, Catastrophic failure ]
)
More if needed:
TeraByte Unlimited Knowledge Base

You could try Tweaking.com's free repair tool following the preparatory steps, and run repair 18 (VSS). Be selective.

 

System Restore, Error 0x81000203

Hi, it looks like you've done what this suggests
Actual Solution for System Restore Error Code 0x81000203 | Windows Forum
Note this (obviously older post) indicates some 3rd party software can interact adversely with system restore.
Please help re: System Restore encountered an error (0x81000203) Solved - Windows 7 Help Forums

A VERY long post where this error message was generated ended up with an in-place upgrade repair install
Macrium Reflect Backup Failures

Noting your comments about services, it may be something's been changed there: you could try
Tweaking.com's free cautious repair tool and run just the repairs related to services.