Windows 10: Hyper-V failing to start any of my VM's.

I am having this issue that after doing an update that updating my Bios and windows 11 to: "2025-01 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 24H2 for x64 KB5049622"and"2025-01 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems KB5050009"non of my Hyper-V VM's are starting unless I turn off TPM but then windows 11 won't work. They all give the error saying:I have tried creating new VM's, it did not fix the issue.Does anyone have any idea why this is happening?Dell Inspiron 391012th Gen Intel Core i5-1240032.0 GB RAMWindows 11 HomeVersion: 2

:)

 

How to disable Hyper-V?

I need it for VMware, to start an VM

 

Unable to Import a Hyper-V VM

I built a VM using

Hyper-V Manager: 10.0.26200.5001

Mangement Consol 3.0

Version 24H2 (OS Build 26200.5001)

I am unable to import it onto another system with:

Hyper-V Manager: 10.0.22621.1

Management Console 3.0

Version 23H2 (OS Build 22635.3566)

When I navigate to the folder with the VM, it show no VMs available.

Is there a way to import the VM built using the newer Hyper-V manager version into the older Hyper-V manager? If not, how do I update the Hyper-V Manager to the same version as the version of Hyper-V Manager that I built the VMs with?

 

Windows 10 Hyper-V: VM start fails - "Assertion failure"

Using Hyper-V, I created a Windows-XP VM machine which I have used regularily without problem until earlier this year.

Now, when I try to start my VM, I get:

[Window Title]

Hyper-V Manager

[Main Instruction]

An error occurred while attempting to start the selected virtual machine(s).

[Content]

'NeilsXP VM' failed to start.

Synthetic Ethernet Port (Instance ID F0CADBEB-F85D-420F-8A02-91CF5563C25B): Failed to Power on with Error 'An assertion failure has occurred.'.

[Expanded Information]

'NeilsXP VM' failed to start. (Virtual machine ID 2C05B581-D924-4241-B58B-A853F9072076)

'NeilsXP VM' Synthetic Ethernet Port (Instance ID F0CADBEB-F85D-420F-8A02-91CF5563C25B): Failed to Power on with Error 'An assertion failure has occurred.' (0x8007029C). (Virtual machine ID 2C05B581-D924-4241-B58B-A853F9072076)

[^] Hide details [Close]

I have no idea what an "Assertion Error" might be and have tried restoring Windows to an early April version without improvement.

The event log shows a "System" error that may (only may) be related:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}

and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}

but like most MS events does not volunteer any solution.

Anyone got any suggestions?

I find it annoying that an environment that works well can suddenly fail for no apparent reason. As such, I am blaming a windows upgrade, but without any specific evidence.