Windows 10: Macrium viBoot - Create Virtual Machine using Macrium Image

I was planning to do the 14371 upgrade on viiBoot vm. So, 2 days ago I switched my Insider machine to Slow Ring to prevent the update from downloading. But to my surprise, it was still downloading even though it's on slow ring (see gif image below). I did not stop it to avoid corruption and just let it do it's thing.
The viiBoot update I posted above is just a test.

 

Just wondering if the viboot technology-preview is stable enough to use? Has anyone experienced any problems?

 

No issues so far.

I have for instance a Macrium image created from Build 14372, which I upgraded to 14379 with viBoot, then again upgraded to 14385 on Sunday. Restoring the twice upgraded image went without problems and computer where image was restored to runs now 14385 as it should.

Of course I have to admit that I have not tested it extensively. My use of viBoot is quite basic; I have a few base Macrium images, containing a sysprepped customized Windows, which I then upgrade with new builds.

I occasionally add / remove some files and software to these images.

The one and only minor issue is that when modified image is saved it uses a lot of computer resources. On my 12 GB system the available RAM for instance dives down to less than 500 MB when writing the modified image, making the PC almost unusable while the image is being written.

 

viBoot Released! – Macrium Software Blog
Macrium viBoot - Release Notes

Release Date
15th July 2016 Version
6.1.1405 - First production release Download Link
http://updates.macrium.com/viboot/v6...ibootsetup.msi New Features

• Improved support for Windows 10.
• Supports images with up to 64 drives.
• Backup the virtual machine without deleting it (requires Macrium Reflect).
• Added “None” option when selecting virtual switches.
• Optimized the drive mounting process to reduce virtual machine creation time.
• Improved user interface components.
• Automatic CPU count detection.
• Complete overhaul of the logging capabilities and a new log pane view.
• Removed dependency on Microsoft services.

Bug Fixes

• Improved support for booting Windows XP based images.
• Temporary files are now deleted when no longer needed.
• Improved reliability of the Virtual SCSI Adapter device driver.

Known Issues

• Virtual Machines based on images stored on a network share will not persist over a restart of the host computer.

http://updates.macrium.com/viboot/v6...ase_notes.html

 

Thanks Cliff, need to edit tutorial, remove the references for viBoot still being Tech Preview *Smile

 

Tweet



— Twitter API (@user) date[/quote]

 

Hi Kari,

Which version of Windows are you running?

The log file correctly states that viBoot has failed to initialize the Macrium Reflect SCSI adapter. Without the Macrium Reflect SCSI adapter it is not possible to create a Hyper-V VM.

Did you uninstall the tech-preview before installing the released version of viBoot?

Thanks,

Mike.

 

I have viBoot on several machines.

On those machines I have now tried update, clean install, everything. I have tried every known trick to bypass driver signing. viBoot does not work for me at the moment due the before mentioned error.

 

Could you tell me the exact version of Windows that are running on the machines?

 

Windows 10 Education and Pro, Build 14390, although I don't understand what difference it makes.

 

I've tried bcdedit.exe /set nointegritychecks ON, as well as selecting Disable driver signature enforcement in boot options:



Using a restore point which restores my systems to a point before update, using viBoot Tech preview I have no issues.

 

@maqcs, did some more research.

First, I think it's the best to test this with latest Insider build 14390. Official release of Anniversary Update is only two weeks away, that build going to be either this one or one of not yet released builds. There's no use to test this with older builds, MS will start pushing the Anniversary Update to users of stable version quite soon.

That being said, I did two tests. First I installed W10 PRO build 14390 on a Hyper-V vm, enabled nested virtualization to get Hyper-V enabled on that vm, setup Hyper-V, installed viBoot, and when run got these two messages:






Using Hyper-V checkpoint I restored the vm to point before installing viBoot. Disabling driver signature I was this time able to install viBoot and run it but as soon as it started I was shown this:



Repeated this test on a spare HP ProBook laptop, clean installing W10 PRO build 14390. The results were exactly the same. I am totally unable to run viBoot.

I hope Macrium gets this fixed, I really like viBoot and its possibilities. The tutorial needs to be updated but I am postponing it until I know viBoot works.

 

Just an update:

Extracted the viBoot Tech Preview installer from an earlier Macrium image:



Using this installer, viBoot works without MrScsi.sys complaining about driver signature.

It stops working as soon as I update it to official release, this one:

 

According to emails I have received from Macrium, all issues have been fixed and Macrium viBoot works as designed, allowing users to service, update and upgrade their Windows system images. Tutorial has been updated.

It's long time since I've been this enthusiastic and happy with a new software product. Macrium Reflect for imaging, be it free or paid for version, together with viBoot for servicing my images makes a complete, powerful backup system.

An example scenario to show what I mean:

• Install Windows 10, create full backup with Macrium Reflect
• Install your software, create a differential or incremental backup
• Join Windows Insider program opting in for Fast Ring
• When Insiders get a new build, make an ISO of the ESD file (tutorial) and upgrade your PC
• Use viBoot to mount your latest differential or incremental image in Hyper-V
• Upgrade the vm, either from Windows Update or using your ISO
• Using viBoot create a new differential or incremental image
• When time comes (for us geeks it always comes!) to reinstall Windows, use Macrium Reflect instead of clean install restoring your last differential or incremental image made in viBoot. It contains Windows 10 upgraded to last Insider build with all your software already installed. Much faster than clean installing Windows, updating it and then installing all software!
• When the next Insider build is released, repeat steps 4 through 7

That's it. It couldn't be easier *Smile

 

Quote from TF Saturday Live Chat: The Anniversary - Windows 10 Forums: