Unable to login with windows live account after creating VIBOOT instance from my backup


Author
Message
TerminatedProcess
TerminatedProcess
New Member
New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)
Group: Forum Members
Posts: 4, Visits: 9
So my Windows 11 box has two accounts. One is associated with my online windows outlook email. It's an admin account. The other is a local admin account I usually create as a backup. I don't use it though. I mounted and spun up a instance of my backup using viBoot. It only gives me the option to sign into my local account. But what I wanted to get was actually in my windows live login. I confirmed my DEFAULT SWITCH network was working so it's not a network issue. Any ideas? 
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)
Group: Forum Members
Posts: 14K, Visits: 85K
If the account linked to your Microsoft account relies on Windows Hello, that won't work in a viBoot scenario because Windows Hello authentication methods rely on data embedded in the system's TPM, and although a VM can have its own virtual TPM, it won't have direct access to the host's physical TPM, which would have the necessary data from when Windows Hello was enabled for that account.  That will therefore break any authentication methods that rely on Windows Hello, which would even include things like PIN authentication for a regular local account.  I can't say for certain that this is the cause of your issue since I don't use Windows accounts linked to Microsoft accounts and therefore I don't know if Windows Hello is a required element of that login method, but I wanted to point this out since other viBoot users have been stuck wondering why things like their PIN won't work in a viBoot scenario.



TerminatedProcess
TerminatedProcess
New Member
New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)New Member (5 reputation)
Group: Forum Members
Posts: 4, Visits: 9
jphughan - 23 August 2022 3:53 AM
If the account linked to your Microsoft account relies on Windows Hello, that won't work in a viBoot scenario because Windows Hello authentication methods rely on data embedded in the system's TPM, and although a VM can have its own virtual TPM, it won't have direct access to the host's physical TPM, which would have the necessary data from when Windows Hello was enabled for that account.  That will therefore break any authentication methods that rely on Windows Hello, which would even include things like PIN authentication for a regular local account.  I can't say for certain that this is the cause of your issue since I don't use Windows accounts linked to Microsoft accounts and therefore I don't know if Windows Hello is a required element of that login method, but I wanted to point this out since other viBoot users have been stuck wondering why things like their PIN won't work in a viBoot scenario.



Thanks for the response. I figured it was something about authentication. I'll have to look into reverting to the regular login method. This isn't a show stopper or anything, I was just wondering why i couldn't log in. Thanks
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search