By Bastet - 22 December 2021 6:16 PM
I don’t use viBoot very often but a few months after upgrading to Windows 11 I wanted to check the Windows 10 image. I found that the booted image didn’t show the log in box but showed the log in screen. I waited 5 minutes but it didn’t appear.
I had activated secure boot & turned on password-less sign in while Windows 10 was installed & within Hyper V I did turn on Secure Boot but it didn’t change anything.
Is it just taking a long time to show the log in box? Or is secure boot &/or the password-less sign in the problem? I normally log in using a PIN.
Thanks for any suggestions.
By Balaji - 23 December 2021 9:22 AM
It appears to be Windows Hello PIN issue. Do you experience similar issues with Password based logins?
PIN is tied to the device and therefore the same image wouldn't work in a VM for login. The VM hardware configurations are different from the imaged machine.
Please check the above link for more information.
By Bastet - 23 December 2021 10:14 PM
Thanks. It seems that I cannot boot the image at all as said image would still have the PIN only log in settings.
I even turned off PIN only on my Microsoft account & restored the password option but the log in screen was still blank.
By Danskeman - 1 February 2022 5:29 PM
Is the virtual hard drive in vhd format - if so, connect it to host and create a dual boot entry, so you can turn off Windows Hello, then change account to a local account, detach vhd from host, and restart vmware?
Also, if you are running Windows 11, it will not work without enabling tpm.
By Bastet - 1 February 2022 6:11 PM
It should be if Macrium creates a .vhd file as default.
I only wish to connect to a vhd on rare occasions. In the end I returned to using a password.
Yes I’m running Windows 11 with temp enabled.