Unable to Create External Virtual Network Switch in Hyper-V (Error 0x80041024)

Question

Dear Community,

I’m encountering an issue on Windows Server 2022 Standard Evaluation where I cannot create External or Internal virtual network switches in Hyper-V. The operation fails with the following error:

Failed while creating virtual Ethernet switch. An unexpected error occurred: %%2147749924 (0x80041024) The Hyper-V Virtual Machine Management service encountered an unexpected error.

---

Environment Details

OS: Microsoft Windows Server 2022 Standard Evaluation

Edition: ServerStandardEval

Hyper-V Role: Installed and active

DISM Output:

Current Edition: ServerStandardEval

  Upgrade Targets: ServerStandard, ServerDatacenter
  

---

Core Issues Observed

Cannot create External or Internal virtual switches in Hyper-V

Error code: 0x80041024 (unexpected error from Hyper-V Virtual Machine Management service)

Both Hyper-V Manager and PowerShell fail for switch creation

No recent changes to network configuration

Evaluation edition is still active

---

Troubleshooting Steps Taken

Verified Hyper-V installation and network adapter availability

Checked system info and DISM output

Confirmed BitLocker status (drive fully decrypted, protection off)

Restarted Hyper-V Virtual Machine Management service

Installed latest PowerShell version as recommended

Multiple reboots performed

---

Question

What could be causing this error (0x80041024) when creating virtual switches in Hyper-V? Is this related to the evaluation edition, a missing component, or something else? What steps can resolve this issue?

Answer 1

The error code 0x80041024 you are encountering when trying to create external or internal virtual switches in Hyper-V typically indicates an issue with the Hyper-V Virtual Machine Management service. This error can arise from various factors, including misconfigurations, permission issues, or problems with the network adapter.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Verify Network Adapter Configuration: Ensure that the network adapter you are trying to bind the virtual switch to is properly configured and enabled. You can check this in the Device Manager.
2. Check Permissions: Make sure that the Hyper-V Virtual Machine Management service has the necessary permissions to access the network adapter. You may need to adjust the security settings or run the Hyper-V Manager as an administrator.
3. Inspect Event Logs: Review the Windows Event Logs for any related error messages that could provide more context on the failure. Look specifically under the System and Application logs.
4. Reinstall Hyper-V Role: If the problem persists, consider removing and then reinstalling the Hyper-V role. This can help reset any underlying issues with the installation.
5. Update Drivers: Ensure that all network adapter drivers are up to date. Outdated drivers can lead to compatibility issues with Hyper-V.
6. Check for Conflicts: Look for any other services or applications that might be conflicting with Hyper-V operations, such as third-party security software or network management tools.
7. Use PowerShell for Creation: If you haven't already, try creating the virtual switch using PowerShell commands, which might provide more detailed error messages. Use the following command:

      New-VMSwitch -Name "YourSwitchName" -NetAdapterName "YourAdapterName" -AllowManagementOS $true
   

8. Consult Microsoft Documentation: Refer to Microsoft's troubleshooting guides for Hyper-V, which may provide additional insights specific to the error code you are encountering.

If none of these steps resolve the issue, it could be beneficial to check if there are any known issues with the evaluation edition of Windows Server 2022 that might affect Hyper-V functionality.

---

References:

• Troubleshoot Hyper-V installation, configuration, and operational failures
• Troubleshoot Hyper-V virtual machine creation

Answer 2

Hello MoazzemHossain,

The error code 0x80041024 translates directly to WBEM_E_PROVIDER_LOAD_FAILURE, which indicates that the WMI provider responsible for Hyper-V networking interfaces is failing to initialize when called by the Virtual Machine Management Service (VMMS). This is generally not a restriction of the Windows Server 2022 Evaluation edition, but rather a corruption in the WMI registration or the network stack bindings that bridge the physical adapter to the virtual environment.

Your primary solution involves re-registering the specific MOF (Managed Object Format) file that handles Hyper-V networking definitions. Open an elevated Command Prompt and execute the command mofcomp %systemroot%\system32\wbem\nvspwmi.mof. This will recompile the Network Virtualization Service Provider WMI definition. Once the tool reports "MOF file has been successfully parsed," restart the management service by running net stop vmms followed by net start vmms. This surgical fix often resolves the provider load failure immediately.

If the WMI recompilation does not clear the error, the corruption lies deeper in the network driver bindings, specifically where the "Hyper-V Extensible Virtual Switch" protocol attaches to your physical NIC. You need to perform a hard reset of the network configuration. In an elevated Command Prompt, run netcfg -d. Please note that this command effectively wipes all network adapters and settings, removing the drivers and reinstalling them to factory defaults; you will lose static IP configurations and RDP connectivity immediately, so ensure you have console or IPMI/iDRAC access to reconfigure the server post-reboot. After the server restarts, the clean driver installation should allow the virtual switch creation to proceed without the provider error.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

VP

Answer 3

Dear Community,

I am currently unable to create External or Internal virtual switches in Hyper-V on a Windows Server 2022 Standard Evaluation instance. Every attempt results in an unexpected error, despite all Hyper-V services and network adapters appearing healthy.

Environment

OS: Windows Server 2022 Standard Evaluation

Hyper-V Role: Installed and active

Physical NIC: Ethernet – Up, 1 Gbps, Driver Version 110.2.50.2025

Hyper-V Management Tools: Installed

PowerShell Module: Installed

Hyper-V Management Clients: Enabled via DISM from ISO

Services:

vmms – Running

  `winmgmt` – Running
  
  **Virtual Switches:** None can be created; `Get-VMSwitch` fails with “Object not found”
  

Error Observed

Failed while creating virtual Ethernet switch. An unexpected error occurred: %%2147749924 (0x80041024)
The Hyper-V Virtual Machine Management service encountered an unexpected error.

Both Hyper-V Manager and PowerShell fail.

Error maps to WBEM_E_PROVIDER_LOAD_FAILURE, indicating a failed WMI provider load.

Troubleshooting Steps Attempted

Verified Hyper-V installation and network adapter availability.

Checked WMI repository: winmgmt /verifyrepository and /salvagerepository – consistent.

Enabled Hyper-V management features using DISM from ISO.

Restarted vmms and winmgmt multiple times.

Disabled unrelated SQL services (SQLBrowser, SQLAgent$SQLEXPRESS, SQLSERVERAGENT) to avoid conflicts.

Multiple system reboots performed.

Verified NIC configuration and driver health.

Analysis

All services are running and NIC is healthy.

The evaluation edition does not include the MOF/WMI definitions required for Hyper-V networking.

• The failure is not related to drivers, missing Hyper-V components, or service misconfiguration.

Answer 4

Hello MoazzemHossain,

The error code 0x80041024 (WBEM_E_PROVIDER_LOAD_FAILURE) specifically indicates that the WMI provider responsible for the Hyper-V networking interface, the code that acts as the bridge between the OS and the virtualization stack, is failing to initialize. While your analysis suggests that the Evaluation edition lacks these definitions, that is incorrect; Windows Server 2022 Standard Evaluation is functionally identical to the retail version regarding feature sets like Hyper-V, and it definitely includes the necessary MOF (Managed Object Format) files. If they appear missing or unregistered, it indicates a corruption in the wbem repository or the initial driver installation, not a limitation of the OS edition.

To fix the broken provider registration, you must manually recompile the Network Virtualization Service Provider definition. Open an elevated Command Prompt and execute mofcomp %systemroot%\system32\wbem\nvspwmi.mof. This command parses the specific MOF file required for virtual switch management and registers it into the WMI repository. You should receive a confirmation that the file was successfully parsed. Once complete, restart the Hyper-V Virtual Machine Management service by running net stop vmms followed by net start vmms. This is the direct resolution for the 0x80041024 error and should allow the Virtual Switch Manager to retrieve the switch list correctly.

If the nvspwmi.mof file is actually missing from that directory, or if the error persists after recompilation, your network stack's bindings to the Hyper-V Extensible Switch are likely corrupted. The robust solution here is to perform a hard reset of the network configuration. Run netcfg -d in your elevated prompt. This command performs a deep cleanup, removing all network adapters, virtual bindings, and registry keys, and then triggers a fresh re-installation of the network drivers and protocols. Be aware that this will delete all static IP configurations and immediately disconnect RDP sessions, so ensure you have console or IPMI access to reconfigure the server after the required reboot.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

VP