Windows 10: Error message 'There is not enough disc space to create the volume shadow copy'.

Hello,


I have a brand new 1TB External Hard Drive. I've checked and there are no disc partitions or disc errors. There is 'allocated' space of 931.38GB. I'm trying to back up '213.97'GB.


I get an error message telling me 'there is not enough disc space to create the volume shadow copy'


I have already checked for disc errors using the 'prompt command' and by using the 'properties>tools>disc check' tool.


Both disc checks came back with 'no errors were found'


What else can I do?


Thanks

:)

 

Volume Shadow Copy Error?

when i try to make a system restore my computer says:

"The volume shadow copy service used by system restore is not working"
and error number 0x81000202

how do i fix this?

 

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered.

I am getting a bunch of errors in the application log related to the Volume Copy Service. I first noticed it when I tried to create a recovery drive and the error simply said that "A problem occurred while creating the recovery drive"

I examined the application log and noticed that this error occurs periodically, not only when I try to create the drive. I included the four errors below.

What do I need to do to fix this?

I am using a Surface pro 4, windows 10 with up to the minute patches. I also have installed carbonite but I doubt this is the cause as I did not encounter this problem on previous PCs

Thanks in advance for any assistance

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance
on class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} and Name SW_PROV is [0x80040154, Class not registered

].

Operation:

Obtain a callable interface for this provider

List interfaces for all providers supporting this context

Check If Volume Is Supported by Provider

Add a Volume to a Shadow Copy Set
Context:

Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}

Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}

Snapshot Context: 4194304

Snapshot Context: 4194304

Execution Context: Coordinator

Provider ID: {00000000-0000-0000-0000-000000000000}

Volume Name: \\?\Volume{acda900a-c1f6-4b66-831d-a54d0f93e6db}\

Execution Context: Coordinator

Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, Class not registered

].
Operation:

Obtain a callable interface for this provider

List interfaces for all providers supporting this context

Check If Volume Is Supported by Provider

Add a Volume to a Shadow Copy Set

Context:

Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}

Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}

Snapshot Context: 4194304

Snapshot Context: 4194304

Execution Context: Coordinator

Provider ID: {00000000-0000-0000-0000-000000000000}

Volume Name: \\?\Volume{acda900a-c1f6-4b66-831d-a54d0f93e6db}\

Execution Context: Coordinator

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from
CoCreateInstance on class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} and Name SW_PROV is [0x80040154, Class not registered

].
Operation:

Obtain a callable interface for this provider

Add a Volume to a Shadow Copy Set

Context:

Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}

Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}

Snapshot Context: 4194304

Execution Context: Coordinator

Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, Class not registered

].
Operation:

Obtain a callable interface for this provider

Add a Volume to a Shadow Copy Set
Context:

Provider ID: {74600e39-7dc5-4567-a03b-f091d6c7b092}

Class ID: {3e02620c-e180-44f3-b154-2473646e4cb8}

Snapshot Context: 4194304

Execution Context: Coordinator

 

Shadow Copy With Storage Spaces?

1 Create shadow storage

1.1 The System protection tab in System Properties

• this GUI only lists NTFS volumes, so you can't create shadow storage for ReFS volume there
  
• instead try one of:
  
  • vssadmin add shadowstorage /for=D: /on=D: /maxsize=100GB (Windows Server only)
    
    • alternatively for non-server Windows editions try vssadmin resize shadowstorage /for=D: /on=D: /maxsize=10% that will add shadow storage if it does not exist and thus is comparable to vssadmin add
      
  • wmic shadowstorage call create Volume=D:\ DiffVolume=D:\ MaxSpace=20
    
    • if this command returns ReturnValue = 10 (which is Unknown error) workaround follows
      
  • wmic shadowcopy call create Volume=D:\
    
    • creating shadow copy on disk without shadow storage will create one automatically
      
    • you can resize the shadow storage with vssadmin resize shadowstorage /for=D: /on=D: /maxsize=10%
      

1.2 List shadow storages

• make sure the shadow storage is there and configured using one of:
  
  • vssadmin list shadowstorage
    
  • wmic shadowstorage list
    

2 Create shadow copy

2.1 Create shadow copy

• you want to use scheduled system protection feature, but for now just take a snapshot manually:
  
  • wmic shadowcopy call create Volume=D:\
    

2.2 List shadow copies

• verify the snapshot was created:
  
  • vssadmin list shadows /for=D:
    

3 Mount shadow copy

• since you are using Storage Spaces, you won't see snapshots in Previous versions tab in disk/file properties
  
• but the snapshots exists and can be mounted as a folder
  
• this shortage apply for both NTFS and ReFS Storage Spaces
  
• to mount a snapshot you will need shadow ID, shadow path and temporary folder
  

3.1 Get shadow copy ID

• vssadmin list shadows /for=D:
  
  • look for something like this Shadow Copy ID: {5cc29315-0379-415e-8496-69923618e3de}
    

3.2 Get shadow copy path

• wmic shadowcopy where "ID='{5cc29315-0379-415e-8496-69923618e3de}'" get DeviceObject
  
• or vssadmin list shadows /for=D:
  
  • look for Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy624
    

3.3 Mount shadow copy as folder

• mklink /j %tmp%\shadow \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy624\
  
  • note the extra \ at the end
    
  • the shadow copy is now available in %tmp%\shadow