Share via

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

Anonymous
2019-07-10T14:49:36+00:00

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.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous
2019-07-10T18:38:03+00:00

Hi Neil

My name is Andre Da Costa; an Independent Consultant, Windows Insider MVP and Windows & Devices for IT MVP. I'm here to help you with your problem.

What is the exact make and model?

Open Start, type: system information

Hit Enter

Click System summary

Look in the right pane

Copy the system sku info into reply here.

See example: https://imgur.com/qzektpA

If its custom built, what is the make and model of the motherboard?

Its possible you might need to update your BIOS and chipset drivers to resolve this issue.

Which version of Windows 10 is currently installed? See how to verify:

https://answers.microsoft.com/en-us/windows/wik...

In the mean time, try the following:

Press Windows key + R

Type: optionalfeatures.exe

Hit Enter

Uncheck Hyper-V

Click OK

Restart if prompted

Press Windows key + R

Type: optionalfeatures.exe

Hit Enter

Check Hyper-V

Click OK

Was this answer helpful?

1 person found this answer helpful.
0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-07-11T16:14:41+00:00

    Trying to give the 5-stars, but no reply rating option is available.

    However,

    MANY Thx  Andre

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-07-11T16:10:24+00:00

    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. 

     

    SKU from System Info:

    OS Name             Microsoft Windows 10 Pro

    Version 10.0.17763 Build 17763

    Other OS Description      Not Available

    OS Manufacturer             Microsoft Corporation

    System Name    NEILS-LAPTOP

    System Manufacturer     Alienware

    System Model   Alienware 15 R3

    System Type       x64-based PC

    System SKU        0774

    Processor            Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s)

    BIOS Version/Date          Alienware 1.1.9, 05/07/2017

    SMBIOS Version               3.0

    Embedded Controller Version     255.255

    BIOS Mode         UEFI

    BaseBoard Manufacturer             Alienware

    BaseBoard Product         Alienware 15 R3

    BaseBoard Version          A00

    Platform Role    Mobile

    Secure Boot State            On

    PCR7 Configuration         Elevation Required to View

    Windows Directory         C:\WINDOWS

    System Directory             C:\WINDOWS\system32

    Boot Device        \Device\HarddiskVolume4

    Locale   United Kingdom

    Hardware Abstraction Layer        Version = "10.0.17763.529"

    Username           NEILS-LAPTOP\Neil

    Time Zone           GMT Summer Time

    Installed Physical Memory (RAM)             16.0 GB

    Total Physical Memory  15.9 GB

    Available Physical Memory          11.0 GB

    Total Virtual Memory     18.3 GB

    Available Virtual Memory             12.3 GB

    Page File Space  2.38 GB

    Page File              C:\pagefile.sys

    Kernel DMA Protection  Off

    Virtualisation-based security       Running

    Virtualisation-based security required security properties          

    Virtualisation-based security available security properties           Base Virtualisation Support, Secure Boot, DMA Protection, Mode Based Execution Control

    Virtualisation-based security services configured

    Virtualisation-based security services running     

    Device Encryption Support           Elevation Required to View

    A hypervisor has been detected. Features required for Hyper-V will not be displayed.           

    If you wish more than the summary, I can place the data on Dropbox and send you a link.

    My Laptop is a DELL XPS and the problem cannot be hardware-related since Hyper-V was working fine 6 months ago or less and no hardware changes have occurred.

    Device Mgr shows a problem with a:

    Virtual switch extension adapter (whatever that is). Has vmswitch.sys changed recently ?

    .. sending this email incomplete as removing Hyper-V requires a reboot.

    I will update you with the results after the reboot. Thx for your help/interest.

    Email rejected because I didn’t use your REPLY button… (sorry)

    Problem resolved now, after re-enabling Hyper-V.

    Device Mgr now shows:

    You have now made an old man very Happy. 5-stars.!!

    Was this answer helpful?

    0 comments