• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1662
  • Last Modified:

Cannot load a virtual machine configuration: The security ID structure is invalid. (0x80070539). (Virtual machine ID BF1F425E-BE12-4901-8F71-8BE48EA34F27)

Hi guys.

I'm not 100% certain what caused it, but when I start my Hyper-V Virtual Machine Management on a 2012 server, virtual machines are listed. When I check the event logs, I get the following message:

Cannot load a virtual machine configuration: The security ID structure is invalid. (0x80070539). (Virtual machine ID BF1F425E-BE12-4901-8F71-8BE48EA34F27)

What I believe may have broken was that this hyper-v was a member of the domain and I dropped it off. After I restarted, I could no longer see the VMs and I got the above message.
I also had SCVMM installed on the box, and removed, don't know if that could have had anything to do with it.

In saying that, the VM was created while the hyper-v was on the workgroup, but the snapshots were created when the hyper-v was a member of the domain. I thought of a permission issue but I checked all the files and the permissions (seems) are correct.

I need help URGENTLY as I need this server up within the next 7 hours.

I thought of just re-creating the VM and pointing to the VHDX as this is intact, but unfortunately the box had two snapshots, so if I do this, it will revert back to the oldest state.

How do I fix this problem OR restore the machine and keep the snapshot? I am afraid to say the guest OS is the Primary Domain Controller so I need this fixed urgently.

Thanks
0
Black-Knight
Asked:
Black-Knight
  • 2
1 Solution
 
giltjrCommented:
The error 0x80070539 is typically related to trying to find a SID.  Not knowing anything about how Hyper-V works, I would assume that there is some SID that is associated with this VM and that when you removed the host from the domain that SID was deleted or at least put in a state that the host OS no longer has access to it.

To me the fix would be to get the host OS back to a state where it was still a member of the domain or somehow get back the SID on the host OS where the host OS could access it.
0
 
Black-KnightAuthor Commented:
Thanks for the info.

After some brainstorming and testing, what I did to fix was to edit the disk and manually merge the snapshots with the vhdx file. Then I re-created the VM, pointed to the virtual drive, and all seems ok.

Thanks.
0
 
Black-KnightAuthor Commented:
I end up sorting out the issue
0

Featured Post

When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot has fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now