Macrium viBoot - Create Virtual Machine using Macrium Image  

@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.

Kari

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:

   Information

The tutorial has been completely rewritten to better introduce now officially released Macrium viBoot (released three days ago), screenshots replaced with new ones better showing the new viBoot interface.

There is a small glitch with a driver, please read the below note (quote from tutorial step 1.2). I will remove the note from tut and delete this post when issue has been fixed.

   Note

PLEASE NOTICE!

viBoot official release was on Friday, I am writing this on Monday night. We here at Ten Forums were first to notice that latest Windows Insider builds caused an issue with Macrium's virtual SCSI adapter required for viBoot to run.

Kudos to Macrium, they started working on the issue on weekend. On Monday I received an email from them telling they have identified the culprit:

We have identified that issue lies with a change in the driver certification logic with newer technical preview kernel builds. The reason that the original viBoot release works is that this was signed by a 'legacy' authenticode certificate; binaries signed using this method are exempted from strict validation to maintain compatibility.

I am sure an updated installer will be available soon. Until that happens, please unselect Run viBoot when installer is ready before closing it!

Before launching viBoot first time download this small ZIP archive from my OneDrive: viBoot SCSI drivers. The ZIP archive is safe to download, it comes directly from Macrium, I received it in an email from their support.

Extract the archive, copy all three files and paste them in C:\Program Files\Macrium\viBoot folder replacing existing files with same name:

Select Do this for all current items and click Continue to paste the files:

Now you can launch viBoot, it will work perfectly :)

Kari

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:

1. Install Windows 10, create full backup with Macrium Reflect
2. Install your software, create a differential or incremental backup
3. Join Windows Insider program opting in for Fast Ring
4. When Insiders get a new build, make an ISO of the ESD file (tutorial) and upgrade your PC
5. Use viBoot to mount your latest differential or incremental image in Hyper-V
6. Upgrade the vm, either from Windows Update or using your ISO
7. Using viBoot create a new differential or incremental image
8. 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!
9. When the next Insider build is released, repeat steps 4 through 7

That's it. It couldn't be easier :)

Kari

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

Kari said:

BTW geeks, Part 3 of the TF Saturday Live Chat: The Anniversary will include a live presentation of Macrium viBoot, a new free application from Macrium Software which let's you mount Macrium Reflect system images in Hyper-V to service, edit, update and upgrade them. The presentation will start 30 minutes after the start of Part 3 (see first post for start time in your time zone) and will last about 10 to 15 minutes.

More about Macrium viBoot: Macrium viBoot - Create Virtual Machine using Macrium Image - Windows 10 Forums

The part of log visible in your screenshot shows that the vm is running?

sunandoghosh said:

Any comments / suggestions?

I am sorry, I have somehow missed your last posts.

I can only say that after running some tests I am unable to reproduce your issue: Windows 7 images I have tested mount without issues as Hyper-V virtual machines.

What about disk space? If your Windows 7 image is from a 512 GB HDD, it needs 512 GB free space on disk where the image is stored. You cannot mount an image as vm if the disk where image is stored has less space than what the image requires.