Windows 10: 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.

:)

 

Hyper-V feature failing to start VMSwitch, looks like a broken driver?

I've been running docker on my computer for weeks, but yesterday my Hyper-V installation broke and docker fails to start. My computer was shut-off the previous night unexpectedly, so that might have been the cause. After digging in further Hyper-V manager
cant load the VM switch manager. The failed drivers seem to point to this isn't related to Docker at all as I've also completely uninstalled docker and am still getting errors. I can open Hyper-V Manager, but clicking on Virtual Switch Manager errors with
"An error occurred while trying to retrieve a list of virtual switches. The generic operation on computer 'XXX' failed: generic failure." I cant create VMs because VMSwitch is failing to start.

Event logs show the following

Warning (source Kernel-PnP): The driver \Driver\VMSP failed to load for the device ROOT\VMS_VSMP\0000.
Error (source Hyper-V-VmSwitch): Failed to initialize VMSwitch driver due to error {Operation Failed}

Removing and re-adding Hyper-V features (Turn Windows features on and off) did not do anything

Tried the command and it did not resolve the issue: netcfg -d

I'm on Windows 10 Enterprise 1809

 

Hyper-v fails to import VM


My Hyper-V storage drive broke down, have backups for that drive, so I have files for VMs. Replaced drive copied files from backup but Hyper-v manager doesn't see any VMs. Trying to import VMs from those files gets me error Unspecified error (0x8004005).
Both Restore and Register Import options fail Copy succeeds but it says that it will create new ID is that bad? If windows license is tied to that VM will it require reactivation?
Any ideas why import fails, maybe because it was disk failure Hyper-v still somehow remembers VMs that was on failed drive and dont let me import same IDs? Get-VM doesn't show any VMs also Hyper-v Manager shows up empty.

 

Hyper-V PowerShell module fails to create new vm

I have a problem with Hyper-V PowerShell module, it fails to create a New-VM on my machine.

It worked fine until I had to reinstall Hyper-V feature in Windows 10.

Since then cannot create VM with powershell cmdlets, creating a VM in GUI works

I receive the following error

New-VM : Hyper-V encountered an error trying to access an object on computer ...... because the object was not

found. The object might have been deleted, or you might not have permission to perform the task. Verify that the

Virtual Machine Management service on the computer is running. If the service is running, try to perform the task again

by using Run as Administrator.

I am the Administrator on local PC, and I checked Hyper-V Virtual Machine Management service, and it is in a running state.

Tried to rebuild MOF file

MOFCOMP %SYSTEMROOT%\System32\WindowsVirtualization.V2.mof

also tried to uninstall Hyper-V feature and reinstall it with powershell, and still no success.

Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

Any other ideas?

I have Windows 10 Pro, version 1709

Regards,

Igor