Hello Steve Rankine,
Welcome to Microsoft Q&A forum.
Before we proceed, can you please run chkdsk F: /scan and let me know its output?
I'm waiting for your reply.
Windows 10 64-bit computer (under ESU) with a recurring VSS failure affecting backup program.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 77%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
Steve Rankine
0
Reputation points
I have a Windows 10 64-bit computer with ESU with a recurring VSS failure affecting my backup program, Acronis True Image. I have already restarted and collected vssadmin list writers, vssadmin list providers, vssadmin list shadows, vssadmin list shadowstorage. If possible, I would like the issue escalated to a Windows technical support specialist if first-line troubleshooting cannot identify the failed writer, provider conflict, shadow-storage problem, or component-store issue.
These are VSS related command responses from command line prompts on sept 28 2026.
Commands issued:
vssadmin list writers
vssadmin list providers
vssadmin list shadows
vssadmin list shadowstorage
Response:
Microsoft Windows [Version 10.0.19045.7548]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'MSSearch Service Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {PII removed}
Writer Instance Id: {PII removed}
State: [1] Stable
Last error: No error
C:\WINDOWS\system32>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
C:\WINDOWS\system32>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Contents of shadow copy set ID: {8477492c-b5b9-4737-8d4b-e24994a5958d}
Contained 1 shadow copies at creation time: 9/25/2026 10:41:52 AM
Shadow Copy ID: {bf40e859-6766-442a-b04b-c09f5ab2faec}
Original Volume: (C:)\\?\Volume{19ced0c4-95cf-11e3-b3e5-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: DOWNSTAIRS
Service Machine: DOWNSTAIRS
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered
```C:\WINDOWS\system32>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Shadow Copy Storage association
For volume: (F:)\\?\Volume{8de41420-7745-44b7-bbdf-e8fbe902eed5}\
Shadow Copy Storage volume: (F:)\\?\Volume{8de41420-7745-44b7-bbdf-e8fbe902eed5}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: UNBOUNDED (2147654065%)
Shadow Copy Storage association
For volume: (E:)\\?\Volume{a597d60b-4196-4dd5-bc0c-a98f9797dddf}\
Shadow Copy Storage volume: (E:)\\?\Volume{a597d60b-4196-4dd5-bc0c-a98f9797dddf}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: UNBOUNDED (3225172315%)
Shadow Copy Storage association
For volume: (I:)\\?\Volume{7a08148f-fce5-4313-ae77-5d623d825dde}\
Shadow Copy Storage volume: (I:)\\?\Volume{7a08148f-fce5-4313-ae77-5d623d825dde}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: UNBOUNDED (3239813291%)
Shadow Copy Storage association
For volume: (D:)\\?\Volume{1591f0e8-80a8-469c-9978-5eb2584292d9}\
Shadow Copy Storage volume: (D:)\\?\Volume{1591f0e8-80a8-469c-9978-5eb2584292d9}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: UNBOUNDED (1844547373%)
Shadow Copy Storage association
For volume: (C:)\\?\Volume{19ced0c4-95cf-11e3-b3e5-806e6f6e6963}\
Shadow Copy Storage volume: (C:)\\?\Volume{19ced0c4-95cf-11e3-b3e5-806e6f6e6963}\
Used Shadow Copy Storage space: 14.5 GB (0%)
Allocated Shadow Copy Storage space: 50.0 GB (2%)
Maximum Shadow Copy Storage space: UNBOUNDED (928596482%)
Shadow Copy Storage association
For volume: (J:)\\?\Volume{8cfa51f6-0000-0000-0000-a08fce010000}\
Shadow Copy Storage volume: (J:)\\?\Volume{8cfa51f6-0000-0000-0000-a08fce010000}\
Used Shadow Copy Storage space: 0 bytes (0%)
Allocated Shadow Copy Storage space: 0 bytes (0%)
Maximum Shadow Copy Storage space: UNBOUNDED (100%)
C:\WINDOWS\system32>
**Acronis Customer Central identified the issue to be VSS after the following:**
1. Took remote session and noticed that the entire Pc backup has failed with "Failed to create volume snapshot" 2. Ran VSS Doctor tool and found VSS errors 3. Increased the J partition size to 12GB, but the issue persists 4. Explained the following: - The error message you're seeing relates to the Volume Shadow Copy Service (VSS), used by Windows to create snapshots of your volumes for backup purposes.
The last attempt at running the Acronis backup was September 23, 2026.
**VSS Doctor tool displayed the following errors:**
**(The text below was extracted accurately from screenshots.** Repetition of entries by the tool have been left in, just in case the repetition is meaningful for analysis**)**
6 Disk I/O Load
An error occurred when performing a check
Invalid query
o Event Log
Some VSS-related errors or warnings occurred during the previous day
2026-09-28 12:42:01, Diskeeper, Error
The Diskeeper defragmentation was cancelled due to an internal error 0x0000000c
2026-09-28 11:59:43, Ntfs, Error
A corruption was discovered in the file system structure on volume F:. The exact nature of the
corruption is unknown. The file system structures need to be scanned online.
2026-09-28 01:47:37, vss. Error
Volume Shadow Copy Service information: The COM Server with CLSID
{4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started.
[0x8007045b, A system shutdown is in progress. ]
2026-09-28 01:47:37, vss. Error
Volume Shadow Copy Service error: Unexpected error calling routine CoCreatelnstance. hr = 0x8007045b, A system shutdown is in progress. .
2026-09-28 01:47:37, vss. Error
Volume Shadow Copy Service information: The COM Server with CLSID
{4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started.
[0x8007045b, A system shutdown is in progress. ]
2026-09-28 01:47:37, vss. Error
Volume Shadow Copy Service information: The COM Server with CLSID
{4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started.
[0x8007045b, A system shutdown is in progress.
-------------------------------------------------------
2026-09-28 01:47:37, vss. Error
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress. ]
2026-09-28 01:47:37, vss. Error
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress. ]
2026-09-28 01:47:37, vss. Error
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress. ]
2026-09-27 21:28:50, Diskeeper, Error
The Diskeeper defragmentation was cancelled due to an internal error 0x0000000c
Windows for home | Windows 10 | Recovery and backup
-
Steve Rankine 0 Reputation points
2026-10-01T02:51:35.3133333+00:00 Hoping someone can help me here. It would be greatly appreciated. It's not a good feeling being unable to run a computer backup.
-
Steve Rankine 0 Reputation points
2026-10-01T16:42:02.0366667+00:00 Thank you to the specialist from Microsoft Forum at [email protected] who replied with the suggestion to provide output from the command chkdsk F: /scan.
The output was
Microsoft Windows [Version 10.0.19045.7548]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>chkdsk F: /scan
The type of the file system is NTFS.
Volume label is 320G.
Stage 1: Examining basic file system structure ...
88448 file records processed.File verification completed.
Phase duration (File record verification): 1.13 seconds.
469 large file records processed.Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.Phase duration (Bad file record checking): 0.26 milliseconds.
Stage 2: Examining file name linkage ...
3574 reparse records processed. 95598 index entries processed.Index verification completed.
Phase duration (Index verification): 2.67 seconds.
0 unindexed files scanned.Phase duration (Orphan reconnection): 9.06 milliseconds.
0 unindexed files recovered to lost and found.Phase duration (Orphan recovery to lost and found): 0.80 milliseconds.
3574 reparse records processed.Phase duration (Reparse point and Object ID verification): 10.50 milliseconds.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 3.63 milliseconds.
3576 data files processed.Phase duration (Data attribute verification): 0.68 milliseconds.
CHKDSK is verifying Usn Journal...
33567520 USN bytes processed.Usn Journal verification completed.
Phase duration (USN journal verification): 236.13 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
838794236 KB total disk space.
561568104 KB in 46631 files.
18448 KB in 3577 indexes. 0 KB in bad sectors. 213348 KB in use by the system. 65536 KB occupied by the log file.276994336 KB available on disk.
4096 bytes in each allocation unit.209698559 total allocation units on disk.
69248584 allocation units available on disk.
Total duration: 4.08 seconds (4080 ms).
C:\WINDOWS\system32>
-
Steve Rankine 0 Reputation points
2026-10-01T16:51:59.1666667+00:00 Hi Carl-L, see above comment for copy-and-paste output of chkdsk command. Apologies if my process of submitting the answer is not according to the established process. This is my first time in this forum.
Sign in to comment
1 answer
Sort by: Newest
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 72%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECL%3C/text%3E%3C/svg%3E)
Carl-L 23,080 Reputation points Microsoft External Staff Moderator2026-10-01T06:24:34.51+00:00 -
Steve Rankine 0 Reputation points
2026-10-01T17:04:23.61+00:00 Hi Carl-L, see above comment for copy-and-paste output of chkdsk command. Apologies if my process of submitting the answer is not according to the established process. This is my first time in this forum.
Microsoft Windows [Version 10.0.19045.7548]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>chkdsk F: /scan
The type of the file system is NTFS.
Volume label is 320G.
Stage 1: Examining basic file system structure ...
88448 file records processed.File verification completed.
Phase duration (File record verification): 1.13 seconds.
469 large file records processed.Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.Phase duration (Bad file record checking): 0.26 milliseconds.
Stage 2: Examining file name linkage ...
3574 reparse records processed. 95598 index entries processed.Index verification completed.
Phase duration (Index verification): 2.67 seconds.
0 unindexed files scanned.Phase duration (Orphan reconnection): 9.06 milliseconds.
0 unindexed files recovered to lost and found.Phase duration (Orphan recovery to lost and found): 0.80 milliseconds.
3574 reparse records processed.Phase duration (Reparse point and Object ID verification): 10.50 milliseconds.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 3.63 milliseconds.
3576 data files processed.Phase duration (Data attribute verification): 0.68 milliseconds.
CHKDSK is verifying Usn Journal...
33567520 USN bytes processed.Usn Journal verification completed.
Phase duration (USN journal verification): 236.13 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
838794236 KB total disk space.
561568104 KB in 46631 files.
18448 KB in 3577 indexes. 0 KB in bad sectors. 213348 KB in use by the system. 65536 KB occupied by the log file.276994336 KB available on disk.
4096 bytes in each allocation unit.209698559 total allocation units on disk.
69248584 allocation units available on disk.
Total duration: 4.08 seconds (4080 ms).
C:\WINDOWS\system32>
-
Steve Rankine 0 Reputation points
2026-10-01T17:07:12.48+00:00 Sorry about the duplication above. Trying to figure out the proper process here!
-
Carl-L 23,080 Reputation points Microsoft External Staff Moderator
2026-10-02T13:43:45.48+00:00 Hello Steve Rankine,
Thanks for replying.
So it doesn't seem like disk issue, next, can you please reproduce an error one more time. Then, without restarting, open an elevated PowerShell and type vssadmin list writers and press Enter. Please note the entries from the time of the failure onward.
-
Steve Rankine 0 Reputation points
2026-10-03T05:40:38.96+00:00 Hello Carl,
The only error appearing after running Acronis VSS Doctor tool was Disk I/O Load. It stated "An error occurred when performing a check. Invalid Query."
The event log stated:
Some VSS-related errors or warnings occurred during the previous day
2026-10-02 09:55:29, Diskeeper, Error
The Diskeeper defragmentation was cancelled due to an internal error 0x0000000c
Output from command vssadmin list writers while in elevated Powershell was:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\WINDOWS\system32> vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {b084d409-3534-43bb-9281-671df6f1bc18}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {f3aa46c2-61d8-4dec-9ad4-6094f1c975fc}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {ccf5c2ca-a1e8-4489-90c0-3503562b803e}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {5b34abe4-fb7d-42f6-8fda-49fddf8baa7d}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {308e68b3-dfb8-4227-9370-4a3c3a732651}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {35674484-71bc-4a30-ba62-da1727da251c}
State: [1] Stable
Last error: No error
Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {1d9ae165-271b-4519-84d4-1b4ec548f57a}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {1cfcaca6-61ee-49e8-94ce-386ef0f7b86b}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {d1ec1ac9-1d59-49a7-9952-5c2a85bbd3e0}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {e358a2bb-43f4-40ea-b121-1b07bc758db2}
State: [1] Stable
Last error: No error
PS C:\WINDOWS\system32>
Not sure if I have answered your request to "note the entries from the time of the failure onward." I ran VSS Doctor, did the PowerShell vssadmin command and immediately copied the results into this comment space.
-
Carl-L 23,080 Reputation points Microsoft External Staff Moderator
2026-10-03T13:24:50.8833333+00:00
Sign in to comment -