Annoyance with ViBoot Losing VHD's, Visible but not Usable in Hyper-V Solved

Page 2 of 3 FirstFirst 123 LastLast
  1. Bree's Avatar
    Posts : 11,116
    10 Home x64 (1903) (10 Pro on 2nd pc)
       #11

    hanks said: View Post
    I was trying to export the viboot machine to another location and then import it as a pure Hyper-v machine. It didn't work...
    I'm sure I did get it to work a while ago (It may have been Macrium 7.1 that I was using at that time) but I've just tested it and the export fails.
      My ComputersSystem Spec

  2.    #12

    There used to be a regedit you had to do to get export working properly. I think it was user @slicendice who told me.
      My ComputerSystem Spec

  3. Bree's Avatar
    Posts : 11,116
    10 Home x64 (1903) (10 Pro on 2nd pc)
       #13

    Bree said: View Post
    I'm sure I did get it to work a while ago (It may have been Macrium 7.1 that I was using at that time) but I've just tested it and the export fails.

    @hanks, I've checked back on my posts from that time and it was indeed v7.1 I had, but I've also found that exporting the viBoot VM failed then too (albeit with a different error message). I did however find a way to make a new standard Hyper-V VM from a viBoot VM (and that one can then be exported, if you wish).


    Bree said:
    I find I cannot export any VM created by Macrium 7 viBoot. Using the Hyper-V Manager or Powershell the export goes to 99% then fails with:
    Export-VM : Failed to copy file during export. Failed to copy file from 'C:\ProgramData\Macrium\viBoot\{1E1C75AE-0529-4535-BC46007B6006DF5E}\657FA20E53586408.01791D81.vhdx' to 'D:\VMs\Exported\viBoot_VM\Virtual Hard Disks\657FA20E53586408.01791D81.vhdx': There is not enough space on the disk. (0x80070070).

    The 'not enough space' error doesn't seems to be the true reason for the failure. The destination drive has 130GB free, more than enough. Also, similar VMs that are not made by viBoot export without a problem to the same destination.

    I have found a workaround (of sorts). Open the Settings for the viBoot VM. Edit the hard drive, Merge it to make a new .vhxd, then in Hyper-V Manager create a new VM using that new .vhdx as the virtual disk. This VM can be exported...
    Export Hyper-V Virtual Machine in Windows 10 - Page 2 - | Tutorials


    I've just tested that method today and successfully made a new VM from a viBoot VM.
      My ComputersSystem Spec

  4.    #14

    Bree said: View Post
    @hanks, I've checked back on my posts from that time and it was indeed v7.1 I had, but I've also found that exporting the viBoot VM failed then too (albeit with a different error message). I did however find a way to make a new standard Hyper-V VM from a viBoot VM (and that one can then be exported, if you wish).

    I've just tested that method today and successfully made a new VM from a viBoot VM.
    I assume the 'new' Hyper-V would work OK with checkpoints? The ability to export is secondary -- I just want to be able to use checkpoints with viBoot machines.
      My ComputerSystem Spec

  5. Bree's Avatar
    Posts : 11,116
    10 Home x64 (1903) (10 Pro on 2nd pc)
       #15

    hanks said: View Post
    I assume the 'new' Hyper-V would work OK with checkpoints?.
    Yes, it's a completely normal Hyper-V VM, solely managed by Hyper-V Manager.

    The new VM is fully independent of the viBoot VM you created it from. Once you have edited the viBoot VM's disk to merge it into a new vhd and used that as the virtual disk for the new VM you can delete the original VM in viBoot. You could also delete the original .mrimg (if you wish). The new VM doesn't need any of them.
      My ComputersSystem Spec

  6.    #16

    Bree said: View Post
    Yes, it's a completely normal Hyper-V VM, solely managed by Hyper-V Manager.

    The new VM is fully independent of the viBoot VM you created it from. Once you have edited the viBoot VM's disk to merge it into a new vhd and used that as the virtual disk for the new VM you can delete the original VM in viBoot. You could also delete the original .mrimg (if you wish). The new VM doesn't need any of them.
    Thanks, it worked like a champ.

    Most interesting thing I discovered: My native system occupies about 39 GB, the Hyper-V virtual image I created by merging is about 34 GB, but the virtual disk created by viBoot is 3.5 GB. I never realized that if I kill (or move) the original MR image the viboot machine dies (that's why my conventional data drive thrashes when I start the viboot machine -- all my other virtual machines are stored on a separate SSD). The viBoot vhd is not a 'stand alone' machine, it needs the original MR backup to function.

    viBoot is great for 'temporary' machines, and thanks to @Bree and others I can make true Hyper-V machines from MR backups. Yea!
      My ComputerSystem Spec

  7. Bree's Avatar
    Posts : 11,116
    10 Home x64 (1903) (10 Pro on 2nd pc)
       #17

      My ComputersSystem Spec

  8. storageman's Avatar
    Posts : 631
    Windows 10 Pro 1809 17763.475
       #18

    There is a problem with Bree's fix. If the Disk has a checkpoint, it will not allow you to edit it ????
      My ComputersSystem Spec

  9.    #19

    storageman said: View Post
    There is a problem with Bree's fix. If the Disk has a checkpoint, it will not allow you to edit it ????
    For all my vhd's with checkpoints, they can't be edited. If I remove the checkpoints you can edit. Not sure what the issue is?
      My ComputerSystem Spec

  10. storageman's Avatar
    Posts : 631
    Windows 10 Pro 1809 17763.475
       #20

    hanks said: View Post
    For all my vhd's with checkpoints, they can't be edited. If I remove the checkpoints you can edit. Not sure what the issue is?
    And there in lies the problem. I would have to do a re-update of 1903 to the original 1809 version. I guess I could do it, but its another step.
      My ComputersSystem Spec


 
Page 2 of 3 FirstFirst 123 LastLast

Related Threads
I have a Macrium Reflect Free image backup from my tablet which is uses a 32bit uefi format installation. I tried to open it in viboot but it refused to open it, and got in a loading failed loop. Installs done with 64bit uefi work fine. I...
Solved log-in annoyance in User Accounts and Family Safety
After the Creators Update,the password is deemed to be "incorrect".Following a restart,the same password is accepted and all is normal. I have tried ----dism /online /cleanup-image /restorehealth and sfc /scannow and both returned clear report.Next...
142096 Hello experts, two questions pls 1. I am unable to see viboot feature while restoring in macrium free reflect? Is it restricted to paid version? 2. I tried to viboot in windows 10 machine with windows 7 image and getting attached...
so when i built my win 10 box it was registering roughly 18-19 gb of ram for usable and now its only at 9.95... any ideas? Oh, and ive already done the unchecking of the ram boxes in startup 117633
I got an email to download last night to add Cortana to my Acer laptop. So foolishly I did. In the process I was required to create an email account, so I tried. I used the windows.com ending. Along the way the whole thing went awry, so I finally...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:47.
Find Us