How can I resolve this error

Question

How can I resolve this error

C Townsend 0

Scoping unsuccessful for shadowcopy \?\GLOBALROOT\Device\HarddiskVolumeShadowCopy15 with error 0x80070057.

0 comments

2 answers

Your answer

Answer 1

Sin-D 10,025 Microsoft External Staff Moderator

Hi C Townsend,

Thanks for reaching out to Microsoft Q&A Forum. I understand you are encountering the error “Scoping unsuccessful for shadowcopy … with error 0x80070057” related to Volume Shadow Copy on Windows Home.

Before proceeding, I’d like to narrow this down a bit:

Which Windows version and build are you currently running?
Does this error occur during a specific operation, such as a scheduled backup, app update, or system maintenance task?

In the meantime, you can try these steps:

1, Check the status of VSS writers

Open Command Prompt as administrator
Run vssadmin list writers
Confirm all writers show as Stable with no errors

2, Reset the Volume Shadow Copy components

Open an elevated Command Prompt
Stop the Volume Shadow Copy and Microsoft Software Shadow Copy Provider services
Restart both services and then reboot the device

3, Verify shadow storage allocation

In an elevated Command Prompt, run vssadmin list shadowstorage
If the allocated space is very low or zero, increase it using vssadmin resize shadowstorage

4, Temporarily disable third‑party security or backup software

Some antivirus or backup tools can interfere with VSS operations
Disable them briefly and test whether the error still occurs

5, Check disk format and integrity

Confirm the affected volume is formatted as NTFS
VSS does not function correctly on unsupported file systems

6, Perform a clean restart and retest

Restart Windows normally without launching additional applications
Retry the operation that triggers the error

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Sin-D 10,025 Reputation points Microsoft External Staff Moderator

2026-03-03T04:30:04.19+00:00

Hi C Townsend,

Have you had the chance to check my answer yet?

Please do keep me updated.
C Townsend 0 Reputation points

2026-03-11T20:31:15.1966667+00:00
No ERRORS in VSS Writers

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: 'ASR Writer'

Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Instance Id: {8022b4fa-16b4-423b-9193-0627fb9ab414}

State: [1] Stable

Last error: No error

Writer name: 'System Writer'

Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

Writer Instance Id: {b4692263-605c-425a-8a06-073d5d7eec3e}

State: [1] Stable

Last error: No error

Writer name: 'MSSearch Service Writer'

Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}

Writer Instance Id: {aeb4a22d-2625-452d-9669-c126be9b285e}

State: [1] Stable

Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Writer Instance Id: {8b01a4d2-d8c4-43b7-acef-06d656e73277}

State: [1] Stable

Last error: No error

Writer name: 'Registry Writer'

Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

Writer Instance Id: {75b7b896-2986-42ab-83fb-cd610ff5f440}

State: [1] Stable

Last error: No error

Writer name: 'COM+ REGDB Writer'

Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

Writer Instance Id: {4ac17cc2-dced-44c3-a274-a2c04a2aed2e}

State: [1] Stable

Last error: No error

Writer name: 'BITS Writer'

Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

Writer Instance Id: {5f3021c7-1996-423d-8194-0f4d69980df8}

State: [1] Stable

Last error: No error

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Writer Instance Id: {9560ac78-9fdd-4e01-a9e9-bbeba7053a03}

State: [1] Stable

Last error: No error

vssadmin list shadowstorage

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: (D:)\?\Volume{a77bbc2e-4f08-4438-97d2-6af5cc6df751}\

Shadow Copy Storage volume: (D:)\?\Volume{a77bbc2e-4f08-4438-97d2-6af5cc6df751}\

Used Shadow Copy Storage space: 966 MB (0%)

Allocated Shadow Copy Storage space: 1.38 GB (0%)

Maximum Shadow Copy Storage space: 10.0 GB (0%)

Shadow Copy Storage association

For volume: (C:)\?\Volume{c58e692b-eb8b-4ee9-9c60-421821d9e243}\

Shadow Copy Storage volume: (C:)\?\Volume{c58e692b-eb8b-4ee9-9c60-421821d9e243}\

Used Shadow Copy Storage space: 18.3 GB (1%)

Allocated Shadow Copy Storage space: 18.7 GB (2%)

Maximum Shadow Copy Storage space: 18.6 GB (2%)

CHKDSK

C:\Windows\System32>chkdsk

The type of the file system is NTFS.

Volume label is Windows.

WARNING! /F parameter not specified.

Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...

1775360 file records processed.

File verification completed.

Phase duration (File record verification): 20.22 seconds.

70847 large file records processed.

Phase duration (Orphan file record recovery): 45.55 milliseconds.

0 bad file records processed.

Phase duration (Bad file record checking): 0.87 milliseconds.

Stage 2: Examining file name linkage ...

6951 reparse records processed.

2256008 index entries processed.

Index verification completed.

Phase duration (Index verification): 30.30 seconds.

C:\Windows\System32>chkdsk d:

The type of the file system is NTFS.

Volume label is New Volume.

WARNING! /F parameter not specified.

Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...

442112 file records processed.

File verification completed.

Phase duration (File record verification): 10.13 seconds.

468 large file records processed.

Phase duration (Orphan file record recovery): 1.08 milliseconds.

0 bad file records processed.

Phase duration (Bad file record checking): 0.71 milliseconds.

Stage 2: Examining file name linkage ...

1323 reparse records processed.

542206 index entries processed.

Index verification completed.

Phase duration (Index verification): 1.56 minutes.

0 unindexed files scanned.

Phase duration (Orphan reconnection): 452.93 milliseconds.

0 unindexed files recovered to lost and found.

Phase duration (Orphan recovery to lost and found): 0.45 milliseconds.

1323 reparse records processed.

Phase duration (Reparse point and Object ID verification): 7.81 milliseconds.

Stage 3: Examining security descriptors ...

Security descriptor verification completed.

Phase duration (Security descriptor verification): 55.42 milliseconds.

50048 data files processed.

Phase duration (Data attribute verification): 0.71 milliseconds.

CHKDSK is verifying Usn Journal...

35419064 USN bytes processed.

Usn Journal verification completed.

Phase duration (USN journal verification): 510.56 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.

3815429 MB total disk space.

1904469696 KB in 390921 files.

101148 KB in 50049 indexes. 0 KB in bad sectors. 662067 KB in use by the system. 65536 KB occupied by the log file.

2001767408 KB available on disk.

4096 bytes in each allocation unit.

976750079 total allocation units on disk.

500441852 allocation units available on disk.

Total duration: 1.75 minutes (105154 ms).
Sin-D 10,025 Reputation points Microsoft External Staff Moderator

2026-03-14T07:13:05.09+00:00
Hi C Townsend,

Thanks for your updates. Please try these additional steps

1, Clear existing shadow copies on the affected volume

Open Command Prompt as administrator

Run vssadmin delete shadows /for=C: /all

Repeat for D: if the error references that volume

Disclaimer: The steps below may result in permanent data loss. Please ensure important data is backed up before proceeding.

2, Re‑register VSS components

Open an elevated Command Prompt

Restart the Volume Shadow Copy and Microsoft Software Shadow Copy Provider services

Then reboot Windows and test again

3, Check Event Viewer for provider‑specific errors

Open Event Viewer

Review Application and System logs around the time the error occurs

Look specifically for VSS or VolSnap entries with the same timestamp

Answer 2

Arlene D 36,055 Independent Advisor

Hi. Are you running a backup or System Restore when it happens?

Make sure Volume Shadow Copy service is running.

Check the drive has enough free space.

Run sfc /scannow in an elevated Command Prompt.

Run chkdsk /f /r on the affected drive.

Check Event Viewer under “Application” for VSS errors.

Let me know how it goes, have a great day!

C Townsend 0 Reputation points

2026-03-11T20:32:04.62+00:00

There is no backup running when the system blue-screens

Share via

How can I resolve this error

2 answers

Your answer