Macrium Viboot problem

I have been using Macrium Reflect 8 to make (and sometimes restore) backups for some years without a problem. I thought I would try Viboot. All goes well, the image boots as far as the lock screen below. Then I can't do anything. Ctl-Alt-Del takes be back to the host OS. I'm missing a trick somewhere.
Any suggestions ?

Select Action > Ctrl+Alt+Delete or use the key combination CTRL+ALT+END.

DennisG said:

I thought I would try Viboot. All goes well, the image boots as far as the lock screen below. Then I can't do anything. Ctl-Alt-Del takes be back to the host OS. I'm missing a trick somewhere.

Click to expand...

What are you using viBoot with to run the VM? Is it Hyper-V?. If so, then Ctrl+Alt+Del will always be intercepted by the Host OS. If you want to send a Ctrl+Alt+Del to the guest OS then, as @FreeBooter has said, you can do that from the Action menu or by using Ctrl+Alt+End.

Thankyou both for your help. I used ctl-alt-end as suggested and that allowed me to log in. It didn't like my pin but I switched to password and that worked. The VM won't connect to my wifi so still trying to figure out that one.

DennisG said:

Thankyou both for your help. I used ctl-alt-end as suggested and that allowed me to log in. It didn't like my pin but I switched to password and that worked. The VM won't connect to my wifi so still trying to figure out that one.

Click to expand...

Have look at Device Manager for your network card if its functioning, then problem Hyper-V network setting.

DennisG said:

The VM won't connect to my wifi so still trying to figure out that one.

Click to expand...

By default viBoot creates a VM that has no network adapter and is not connected to the network. You need to change that in the 'Hyper-V VM Settings' when you set up the image to boot from. Connect the Virtual Switch to the Default Switch and your VM will have internet access through the Host's adapter. It will also be able to see any shares on the Host machine, but not any other PCs on your network.



Alternatively, in the Settings for your existing viBoot VM you can add a network adapter. With the VM shut down, select File > Settings.





If you want the VM to see any other PCs on your network then you need to create a new Virtual Switch in the Hyper-V Manager's Virtual Switch Manager and connect your VM to that instead.

G'day Bree, I have never played with viBoot and I know nothing about Hyper V. Have always been a VMware-baby / vSphere user. Getting all sorts of issues with VMWare workstation with latest W11 updates so I guess I need to switch?
Bree, can you recommend what is the best to use now, with v8 or v10? Virtual Box I am sure can read disk images from Hyper-V?
Just appreciate your insight as you are so well versed, plus I love your articulate answers and helpful attitude on the forums.
Thanks mate

Bree said:

By default viBoot creates a VM that has no network adapter and is not connected to the network. You need to change that in the 'Hyper-V VM Settings' when you set up the image to boot from. Connect the Virtual Switch to the Default Switch and your VM will have internet access through the Host's adapter. It will also be able to see any shares on the Host machine, but not any other PCs on your network.

Click to expand...

Flipmode said:

G'day Bree, I have never played with viBoot and I know nothing about Hyper V. Have always been a VMware-baby / vSphere user. Getting all sorts of issues with VMWare workstation with latest W11 updates so I guess I need to switch?
Bree, can you recommend what is the best to use now, with v8 or v10? Virtual Box I am sure can read disk images from Hyper-V?
Just appreciate your insight as you are so well versed, plus I love your articulate answers and helpful attitude on the forums.
Thanks mate

Click to expand...

Thank you for your kind words.

If you want to use viBoot then it only supports using Hyper-V or VirtualBox. For Reflect v8 viBoot supports VirtualBox 6 and 6.1, ReflectX (10) adds support for VirtualBox 7 and 7.1.

Hyper-V and VirtualBox only have one disk format in common, the VHD file format. Hyper-V uses VHDX by default and VirtualBox's native format is VDI. It is possible to convert VHDX to VDI....

...but if you have Reflect available and the Hyper-V VM is a Windows guest, then it's probably simpler/easier to use Reflect to make an image of the Hyper-V VM, then boot an empty new VirtualBox VM from the Reflect rescue ISO and restore the Reflect image to it. You can make a Reflect rescue ISO with Reflect's Rescue Media Builder.

Note that each VM, Hyper-V or VirtualBox, is a new machine as far as Windows activation is concerned. If you transfer an activated W10/11 VM from one to the other the new VM won't be activated. You may be able to reactivate it using the Activation Troubleshooter if you were previously signing in on the old VM with your Microsoft account.