How to fix VMware Converter error “FAILED: The VSS snapshots cannot be stored”

While moving some VM’s from Hyper-V to VMware using VMware Converter a VM failed to convert with the error: FAILED: The VSS snapshots cannot be stored.

FAILED: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source machine does not have any NTFS volumes. Error code: 2147754783 (0x8004231F).

Come to find out the System Reserved partition was full. Our soon to be retired Appassure backup application was nice enough to fill up the volume.

Luckily Appassure is being replaced by Veeam and fixing the above VMware Converter error is an easy fix.

Steps on how-to fix VMware Converter “FAILED: The VSS snapshots cannot be stored” error message

  1. Open Computer Management by pressing Windows Key+R and typing in compmgmt.msc, then go to Disk Management.
    computer management
  2. Right click on the System Reserved partition and select Properties.
    system reserved properties
  3. Then click on the Shadow Copies tab and ensure Shadow Copies are disabled for each volume and then close the Properties window.
    system reserved shadow copies
  4. Again, right click on the System Reserved partition and then select “Change Drive Letter and Path…” and assign the partition a drive letter (I’ll be using letter Z).
    system reserved drive letter
  5. Next open the Z: drive in File Explorer and right click on System Volume Information folder and select Properties.
    system reserved z drive
  6. In the System Volume Information Properties window, click on the Security tab then click on Advanced to open the Advanced Security Setting dialog box.
    system volume information advanced
  7. Now add the Everyone group Full control to the folder, subfolders and files.
    advanced security settings
  8. Right click on Start Menu icon and select Command Prompt (Admin) to open a Command Prompt as Administrator.
    command prompt as admin
  9. Now type in the following commands:
    
    Z:
    fltmc unload aafsflt
    cd "System Volume Information"
    del aalog_*
    cd ..
    fltmc load aafsflt
    

    delete logs commands
    Then exit the command prompt.

  10. Finally be sure to remove the Everyone access from the System Volume Information folder (steps 6 & 7) and remove the drive letter (step 4).

Now re-run your VMware Converter task again and the migration should work without issue!

Similar Posts

  • How to upgrade ESXi 6.5 to ESXi 6.7

    VMware released ESXi 6.7 a little while ago, but it’s only been here recently have I started deploying it in my home and work lab environments. Below are two ways to easily upgrade your ESXi 6.5 hosts to ESXi 6.7 using the command line or by using the VMware ESXi offline bundle.

    Read More “How to upgrade ESXi 6.5 to ESXi 6.7”

  • VMware ESXi 5 home lab upgrade

    In the past I’ve been using a single server to run my VMware ESXi home lab. it was slow, old, big and loud. I’ve been meaning to upgrade my home lab for a while and just never got around to it, until now! When looking for new hardware I wanted the servers to be as compact as possible, quiet, and low energy usage as possible while still having some horsepower.

    I debated on going the whitebox solution as I build all my own desktops anyway, I also looked at several other solutions such as the HP ML310e server, Shuttle XH61V barebones machine, but ultimately decided to go with two Intel NUC i5’s.

    Intel NUC i5 and 16GB ram

    Intel NUC i5 DC53427HYE Features:

    • Uses very little energy
    • Completely quiet
    • Supports up to 16GB RAM
    • A dual core CPU that scores nearly 3,600 in PassMark benchmarking
    • Includes vPro which allows me to easily run both NUC’s headless
    • Extremely small, nearly 4 1/2″ inch square footprint

    Read More “VMware ESXi 5 home lab upgrade”

  • Thank you VMware Community!

    VMware vExpert 2014

    So far, 2014 has been a very rewarding year for a number of reasons, two of which has happened in just a week or two span. First, Eric Siebert (@ericsiebert) announced on March 27th, this years results of the 2014 Top VMware & Virtualization Blog voting. My first year entered into voting and made it to 71st place! A huge thanks goes out to not only Eric but just as much so to everyone who voted for me!

    To top it off, yesterday VMware announced 2014’s first quarter VMware vExpert list. While vExpert isn’t a technical certification or even a general measure of VMware expertise. The VMware judges selected people who were engaged with their community and who had developed a substantial personal platform of influence in those communities. There were a lot of very smart, very accomplished people, even VCDXs, that weren’t named as vExpert this year. VMware awarded this title to 754 people this year and on that list of many impressive names you’ll find yours truly, Michael Tabor!

    I’m both honored and humbled by both lists. It’s a great feeling to be recognized by not only my peers through the voting in the Top vBlog but also by VMware themselves through the vExpert title.

    So again THANK YOU very much to the entire VMware community, a spectacular community indeed, and congratulations to everyone else that made the Top vBlog and vExpert lists!

  • VMware vCenter Server 5.5.0a update released

    VMware has released an update to vCenter 5.5 Server. The new updated, numbered 5.5.0a doesn’t appear to add any new features but instead focus on squishing a number of bugs in the 5.5 version – mostly around vCenter Single-Sign-On and the vSphere web client.

    Issues resolved with this release are as follows:

    1. Attempts to upgrade vCenter Single Sign-On (SSO) 5.1 Update 1 to version 5.5 might fail with error code 1603
    2. Attempts to log in to the vCenter Server might be unsuccessful after you upgrade from vCenter Server 5.1 to 5.5
    3. Unable to change the vCenter SSO administrator password on Windows in the vSphere Web Client after you upgrade to vCenter Server 5.5 or VCSA 5.5
    4. VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables

    Read More “VMware vCenter Server 5.5.0a update released”

  • How to Reset VMware vCenter Server Appliance Root Password

    Have you ever forgotten the root password on your VMware vCenter Server Appliance (VCSA) or let the password expire before changing it?

    This is exactly what happened to me in one of my lab environments and in this post I’ll show how to quickly and easily reset the VCSA root password.

    Read More “How to Reset VMware vCenter Server Appliance Root Password”

  • VMware Workstation updated to 9.0.2

    VMware is released a maintenance update for VMware Workstation to version 9.0.2. The update is available for free for all VMware Workstation 9.x customers.

    Mostly just bug fixes and a few improvements, here are a few highlights:

    • Fedora 18 supported as a guest operating system
    • Windows 8 host permissions issues fixed
    • VMware Tool updated to support the latest Linux kernels
    • Improved general host resource management
    • OVF Tool has been updated to version 3.0.2
    • Virtual machine sharing improvements
    • Memory leak which impacted Windows hosts has been fixed

    Read More “VMware Workstation updated to 9.0.2”

Leave a Reply to DecentDiscourse Cancel reply

Your email address will not be published. Required fields are marked *

2 Comments

  1. I resolved this issue another way. I assigned a drive letter to the recovery partition in preparation to remove suspected journal files, however that was not the problem. Opening the drive letter for the recovery partition revealed an installation of Kaspersky anti-virus taking up 73 mb. Removed that , removed the drive letter and I no longer get the Vss shadow copy error. I would recommend people assign a drive letter and see if they see data on the recovery drive which should not be there. Do not delete stuff if you do not know what it is for, such as any files with the word “boot” in them. Also, if you see only a few files which do not add up to 100 mb, google for how to remove journal files. That might be the problem.

  2. If you cannot acces to the system reserved you can open this partition by linux mint live cd. when I opened partition and I delete all recovery folder ( becouse I don’t need this folder. I made backup by acronis wd). after this operation I have 400 MB free space and I can convert machine now. Best regards. Pawel from Poland