Macrium viBoot - Create Virtual Machine using Macrium Image  

badrobot said:

Tried the viiBoot. I used the 14366 image that I want to upgrade to 14367. Problem is, the upgrade isn't showing up in viiBoot.

Here a viBoot Hyper-V vm from build 14342 image, upgrade downloaded, Windows preparing it:

Ready to restart and upgrade:

Over two hours later (I forgot that vm was running in the background ), upgraded and ready to go:

Thanks Kari. I will try again on the next build. I hope there will be one before I fly this Friday to Asia for a 4-week vacation.

@Kari , I just found out last night that if you accidentally close the Macrium viiBoot or Hyper-V (without properly turning it off) or messed up with it in any way, it can corrupt the image and render it useless. This is going to be the case for newbies. I tried restoring my 14367 machine last night with Macrium image (which I used with viiBoot) but the restoration process won't even start because of the reportedly corrupt image.
Somewhere along your tutorial, there should be a warning about this by making a separate copy of the image for viiBoot and keep the original one as backup.
Not a problem for me because I have other images to work with. :)

Good point. I will do some tests and edit tutorial accordingly.

Kari said:

Good point. I will do some tests and edit tutorial accordingly.

Thanks, YMMV though. But that's the only thing I can remember that might have corrupted the image. This is the first time I had a corrupted image and using it with viiBoot is the only reason I can think of why it got messed up.
Don't get me wrong Kari. I am in no way blaming you or your tutorial. Just giving you some feedback. :)

EDIT.

One question @Kari , does the viiBoot Hyper-V vm had to be activated to get the windows insider build upgrade to show up?

badrobot said:

Does the viiBoot Hyper-V vm had to be activated to get the windows insider build upgrade to show up?

No, I've successfully upgraded mine several times, normal Hyper-V virtual machines as well as viBoot machines. Because my PCs have digital entitlement, I always get an activation error with viBoot virtual machines. It's of course logical, the digital entitlement of the machine image was created from cannot be transferred to vm.

Kari said:

No, I've successfully upgraded mine several times, normal Hyper-V virtual machines as well as viBoot machines. Because my PCs have digital entitlement, I always get an activation error with viBoot virtual machines. It's of course logical, the digital entitlement of the machine image was created from cannot be transferred to vm.

I see. I know the digital entitlement stays with the physical machine. That's why I tried to activate the viBoot vm with my multi-activation key from my MSDN account. Just because I thought it's necessary to activate viiBoot vm first to get the upgrade to show up. So, okay. No need to activate. Thanks.

@Kari , I can see the update now inside viiBoot vm..

Good! Sometimes you just have to wait. Build 14371 from yesterday, took hours yesterday for it to appear for me on other editions than PRO, still early this morning my PRO setups haven't received it.

Kari said:

Good! Sometimes you just have to wait. Build 14371 from yesterday, took hours yesterday for it to appear for me on other editions than PRO, still early this morning my PRO setups haven't received it.

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.