Hyper-V VM was repaired and will now boot but, can only login locally cause the loss of trust to the domain

Question

I have a Physical host running 2019 Windows Server with a half dozen Virtual Machines attached to it. I believe that two of the hosts went through updates last evening and were hard down this past morning. 1 of 2 host were 'repaired' with the help of MS support. The VM went from going directly into automatic repair mode to post repair where it is now trying to boot but just "spinning"

Just now got it to actually boot but, now I'm having domain trust issues and can only login locally.

Any help?

Answer 1

You could try

Test-ComputerSecureChannel -Repair  

otherwise simply rejoin the domain.

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Hello

Thank you for your question and reaching out. I can understand you are having query\issues related to VM Trust relationship.

This can be happened due to Windows updates , Please try to uninstall recent Windows updates, if there is still issue. Please Disjoin and Rejoin to AD Domain.

--If the reply is helpful, please Upvote and Accept as answer--

Answer 3

Hi.
Try running Get-NetConnectionProfile and see which profile applies to your network adapter.
If it's public, set it to private. You're not able to set it to DomainAuthenticated, this will happen automatically when Windows detects it is actually joined.
Reboot computer, then run Test-ComputerSecureChannel -Repair
If it fails, rejoin to domain, but check NetConnectionProfile (and set to private if needed) before doing so.