If, in your Event Log, you encounter a VolSnap error
The shadow copies of volume \\?\Volume{XXXXXXXX} were aborted during detection because a critical control file could not be opened.
You might want to check if the system ran into Disk warnings and/or other service errors earlier. Those may be causing this as a consequential error or the error may result from having too many shadows or the host is simply taking too much time to create a VSS shadow.
There are several ways to fix this issue:
Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. 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: (C:)\\?\Volume{1d14ab39-af32-45bd-a7f8-8ba039aef229}\ Shadow Copy Storage volume: (C:)\\?\Volume{1d14ab39-af32-45bd-a7f8-8ba039aef229}\ Used Shadow Copy Storage space: 9,34 GB (1%) Allocated Shadow Copy Storage space: 9,64 GB (2%) Maximum Shadow Copy Storage space: 10,0 GB (2%) C:\WINDOWS\system32>vssadmin resize shadowstorage /For=c: /On=c: /MaxSize=UNBOUNDED vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2013 Microsoft Corp. Successfully resized the shadow copy storage association C:\WINDOWS\system32>