Skip to main content

Win 10 HDD to NVME Clone Tried Every Solution to All Error Codes. No Fix.

Thread needs solution
Regular Poster
Posts: 198
Comments: 120

I apologize from the start that this is rather long and erratic. I included the Acronis VSS doctor report, as I know just an explanation helps nothing. A few days ago I got a WD nvme off amazon, I put it in, used acronis and cloned everything from my hdd to my new ssd. Booted and worked. I then realized I bought the wrong nvme on amazon, it was a 560 MB/s instead of 2400. So I ordered the fast one and did a transfer back to the hdd. Booted and worked. I put in the new nvme and went to do the same. It ran same as before but this time when I did it, the nvme did not boot. After hours of thinking I broke my hdd and lost everything the hdd came back and repaired itself.

After being very weary I tried to clone again, I tried doing a backup and recover, but nothing will work. I completely uninstalled acronis, tried other programs, completely uninstalling before installing new ones btw. I ran into a bunch of different errors for VSS stuff, I followed all instructions and solutions that anyone had, including restarting VSS in the services, doing a chkdsk in cmd, DISM tool? in cmd, and I checked to make sure the provider was correct in the cmd, as well as regedit. I also wanted to mention that I've restarted my pc everytime i would uninstall or install a new cloning program. Its been two days and I can't seem to find a fix. I hope I am just missing something but I am just lost.

For some specifics I got the WDSN550 NVME, and the drive it is currently on is a WD server hard drive formatted in GPT. If anyone can actually help I'd be happy to try and provide more information if needed. Thanks. 

 

 

To Follow up after doing a chkdsk on my C: drive: I ran it, it took about 5 hours to complete, there were about 2 million files or whatever it was repairing that got repaired. I've since ran the VSSDoctor again, and I am now down to one error only I believe. VSS Error 8193, I searched it via the VSSDoctor link, and tried going into regedit and change permissions, rebooted, and still giving me the error. I have included my latest VSSDoctor report below.What I did find was something about each partition must be 1024 MB to backup or clone because of VSS? Is that true? If so how did I do two clones prior without any trouble? Thanks for the help.

0 Users found this helpful

Tony, welcome to these public User Forums.

What version of ATI are you using here?  Is this ATI 2021 per this forum, or are you using a free OEM version of ATI provided by WD with your new SSD?

If the latter then see KB 2201: Support for OEM Versions of Acronis Products which applies to all OEM versions of ATI supplied with hardware purchases.

Next, how are you doing the cloning here?  Are you cloning from the HDD to the SSD from within Windows (using Acronis Active Clone which uses Microsoft VSS to capture snapshot data)?

Are you booting into Windows after cloning with both the HDD and SSD drives still present?  If so this is not recommended as can cause a disk signature clash and can result in corruption!

You look to have a number of drives installed in your PC (as indicated in the VSS Doctor report) including a H: drive which is being reported as having zero free space?

Ideally, I would recommend disconnected all unrelated drives that are not needed to perform the clone operation before starting - this for safety to avoid any potential loss of data etc, plus to keep the operation as simple as possible.

After cloning, the original source drive should be removed while testing whether the cloned new SSD will boot correctly into Windows.

For the VSS errors, if the VSS Doctor tool offers any options to fix issues it identifies, then you should allow it to do so.

If you still see the VSS Shadow Storage error, then again, try disconnecting any drives that are not needed (including H:) then repeat running the tool to see if the same error is given?

Beyond that, open an Administrator command prompt (or Powershell window) and try using the vssadmin commands to get further detailed information about VSS status, in particular for shadow storage.

C:\WINDOWS\system32>vssadmin /?
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

---- Commands Supported ----

Delete Shadows        - Delete volume shadow copies
List Providers        - List registered volume shadow copy providers
List Shadows          - List existing volume shadow copies
List ShadowStorage    - List volume shadow copy storage associations
List Volumes          - List volumes eligible for shadow copies
List Writers          - List subscribed volume shadow copy writers
Resize ShadowStorage  - Resize a volume shadow copy storage association

C:\WINDOWS\system32>vssadmin delete shadows /?
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Delete Shadows /For=ForVolumeSpec [/Oldest] [/Quiet]
Delete Shadows /Shadow=ShadowId [/Quiet]
Delete Shadows /All
    - For the given ForVolumeSpec deletes all matching shadow copies.
    If /Oldest is given, the oldest shadow copy on the volume is deleted
    If /All is given, then all shadow copies on all volumes that can be
    deleted will be deleted.  If /Shadow=ShadowId is given, the shadow copy
    with that Shadow Copy ID will be deleted.  Only shadow copies that have
    the ClientAccessible type can be deleted.
    - The Shadow Copy ID can be obtained by using the List Shadows command.
    When entering a Shadow Copy ID, it must be in the following format:
       {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}
    where the X's are hexadecimal characters.  This ID can be obtained
    through the List Shadows command.

    Example Usage:  vssadmin Delete Shadows /For=C: /Oldest

C:\WINDOWS\system32>vssadmin delete shadows /For=C: /Oldest
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Do you really want to delete 1 shadow copies (Y/N): [N]? Y

Successfully deleted 1 shadow copies.

C:\WINDOWS\system32>vssadmin delete shadows /For=C: /Oldest
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Do you really want to delete 1 shadow copies (Y/N): [N]? Y

Successfully deleted 1 shadow copies.

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{0ba1d081-19d6-4315-83ff-5c8afda79bb6}\
   Shadow Copy Storage volume: (C:)\\?\Volume{0ba1d081-19d6-4315-83ff-5c8afda79bb6}\
   Used Shadow Copy Storage space: 7.59 GB (3%)
   Allocated Shadow Copy Storage space: 13.0 GB (6%)
   Maximum Shadow Copy Storage space: UNBOUNDED (100%)

Shadow Copy Storage association
   For volume: (D:)\\?\Volume{deea6c64-6f61-4c25-a982-25f9cf2c57e5}\
   Shadow Copy Storage volume: (D:)\\?\Volume{deea6c64-6f61-4c25-a982-25f9cf2c57e5}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: UNBOUNDED (1868251646%)

Tony,

Looking at your VSS Doctor log I find several errors.  I believe that one error is essentially causing the others.

Early on in the log I find this:

Disk Free Space Available

Status: Warn
Description: Some disks have insufficient free space. Perform a cleanup.

This indicates that available free space is insufficient for the VSS service to create the required shadow copy for the backup.  Notice that the suggested remedy is to Perform a cleanup.

Next I find this:

NTFS Volume Access Control Configuration

Status: Warn
Description: Some volumes have incorrect access control configuration

The log result goes on to show that all disk volumes have access by Windows "System".  This is correct so the error suggests that you may be attempting to run the TI application as a regular Windows user without Admin privileges.  TI requires that it be run in an Admin instance so I must ask, did you install the application by selecting "Run as administrator"?  I am going to assume that you installed the product correctly and suggest that this error is the result of corruption on disk.

The next error I find is this:

\\?\Volume{ea10c0b6-0000-0000-0000-100000000000}\
InstanceId: 12293

The Volume shown here is that of the non-lettered partition on your System disk suggesting that insufficient space and/or corruption exist on that volume.  I suggest that you assign a drive letter to this partition and run command line tool chkdsk to check for file system and disk errors since you are working with an HDD.  

To assign a drive letter temporarily to the partition and then remove that letter easily after chkdsk is run you can use the Acronis VSS Doctor tool.  Open and run the tool then after the diagnostic is finished, any problems will be shown in the GUI.  Look under the "Disk Free Space Available" section and locate the volume above.  You will see what looks like a link below the volume entry that is underlined and reads "Assign drive letter"  Click there to assign a letter to the volume.  The tool will assign a letter to the volume and it will likely open in Explorer showing as empty.

The next step is to open either an admin command prompt or and admin PowerShell window.  At the prompt type the following:

chkdsk X: /r   where X is the drive letter that was assigned by VSS Doctor.  Make note of the output of the command for any errors and fixes applied.  If it is reported that no errors were found and/or no corrections were made then it is advisable that you use a disk partitioning tool such as MiniTool which we recommend here for the purpose of resizing the space allocation to this partition.  If you need to do this then applying the minimum allowable additional space for the partition should fix the space issue.

Having said the above I believe chkdsk will find errors and correct them in which case you can close out your command prompt or powershell window, go back to the VSS Doctor tool, locate the volume in the list and click on the link "Unassign drive letter" to remove the temporary letter assigned, you may receive a confirmation dialogue that you wish to remove the letter from the volume click Yes.

At this point you can again attempt the Clone procedure hopefully this time to a success.

Regular Poster
Posts: 198
Comments: 120

To answer your question Mr. Smith I am on ATI 2021. I ran the VSSDoctor again, which came up with fewer errors, which I have provided again. I don't know why the previous drive assigned H was full, it wasn't a separate drive, and it was also only allowed read privileges, I wasn't able to do anything for that last night but after shutting down and restarting the VSS doctor does not show it or have errors for it. I assigned the last unassigned partition, which is now coming up as H. I will attempt at the chkdsk again, it wasnt coming up with anything before but I will do that now. 

The only thing puzzling me is: 

VSS Shadow Storages Status

Status: Error
Description: An error occurred when performing a check

Error occurred:
System.Management.ManagementException: Provider failure 

 I know I also may need to do more fixes as you Mr. Smith and Enchantech seem to know a heck of a lot more about VSS than me.

Attachment Size
565230-210398.txt 11.58 KB

Tony, the next step that I see from your latest VSS Doctor report is to follow the link shown for the multiple error entries at the bottom of the report.

SearchLink: https://www.google.com/#newwindow=1&q=VSS+event+id+8193

This has a lot of hits (33,000) in the Google search results that should help you narrow down on the cause and solve this issue. You can add extra search arguments to focus in on the results, i.e. "event 8193 vss windows 10"

The other continuing error from the report is:

===========================================================
VSS Shadow Storages Status

Status: Error
Description: An error occurred when performing a check

Error occurred:
System.Management.ManagementException: Provider failure 
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Acronis.Utilities.VSSDoctor.Collectors.ShadowStoragesCollector.Collect()
   at Acronis.Utilities.VSSDoctor.Launcher.Worker_DoWork(Object sender, DoWorkEventArgs e)


===========================================================

When I run the VSS Doctor on my own Win 10 PC, the above section of the report is shown as below, which is how yours should be looking in terms of general layout.

===========================================================
VSS Shadow Storages Status

Status: OK
Description: All VSS shadow storages are configured correctly

Storages:

ForVolume: C:\
OnVolume: C:\
Used: 5621 MB
Allocated: 11 GB
Maximum: UNBOUNDED
Minimum: 320 MB
VolumeSize: 200 GB
Available: 115 GB
TargetMaximum: 20 GB
MaximumGreaterThenMinimum: True
MaximumIsEnough: True
MaximumIsNotReached: True
AvailableIsEnoughForMaximum: True
IsOk: True
Description:

ForVolume: D:\
OnVolume: D:\
Used: 0 B
Allocated: 0 B
Maximum: UNBOUNDED
Minimum: 320 MB
VolumeSize: 919 GB
Available: 478 GB
TargetMaximum: 91 GB
MaximumGreaterThenMinimum: True
MaximumIsEnough: True
MaximumIsNotReached: True
AvailableIsEnoughForMaximum: True
IsOk: True
Description:

===========================================================

This brings us back to looking at the vssadmin commands from my earlier post

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{0ba1d081-19d6-4315-83ff-5c8afda79bb6}\
   Shadow Copy Storage volume: (C:)\\?\Volume{0ba1d081-19d6-4315-83ff-5c8afda79bb6}\
   Used Shadow Copy Storage space: 5.52 GB (2%)
   Allocated Shadow Copy Storage space: 11.4 GB (5%)
   Maximum Shadow Copy Storage space: UNBOUNDED (100%)

Shadow Copy Storage association
   For volume: (D:)\\?\Volume{deea6c64-6f61-4c25-a982-25f9cf2c57e5}\
   Shadow Copy Storage volume: (D:)\\?\Volume{deea6c64-6f61-4c25-a982-25f9cf2c57e5}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: UNBOUNDED (1868251646%)

The above matches with the output from the VSS Doctor, showing that only my C: drive has any actual used shadow storage space (of 5.52 GB equating to 2%).

I can easily clear this used space, if needed by using another command:

C:\WINDOWS\system32>vssadmin delete shadows /For=C: /Oldest
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Do you really want to delete 1 shadow copies (Y/N): [N]? Y

Successfully deleted 1 shadow copies.

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{0ba1d081-19d6-4315-83ff-5c8afda79bb6}\
   Shadow Copy Storage volume: (C:)\\?\Volume{0ba1d081-19d6-4315-83ff-5c8afda79bb6}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: UNBOUNDED (100%)

Shadow Copy Storage association
   For volume: (D:)\\?\Volume{deea6c64-6f61-4c25-a982-25f9cf2c57e5}\
   Shadow Copy Storage volume: (D:)\\?\Volume{deea6c64-6f61-4c25-a982-25f9cf2c57e5}\
   Used Shadow Copy Storage space: 0 bytes (0%)
   Allocated Shadow Copy Storage space: 0 bytes (0%)
   Maximum Shadow Copy Storage space: UNBOUNDED (1868251646%)

Note: Shadow Storage is also used for Windows System Protection, so deleting shadows will also remove system restore points if system protection is enabled.

Tony,

The 8193 error is rather generic thus the 33,000 hits on Google.  It basically means an unexpected error has occurred.  You may wish to re-register the VSS writers on your system to see if that will remedy the 8193 error.

Check your messages in your Forum account.