I have crashing Hyper-V Manager

Question

I have crashing Hyper-V Manager

It is crashing when I click on Hyper-V Settings / Replication Configuration - it stuck for couple of seconds and Hyper-V Manager crash. In event viewer, new Error appears at this moment.

Application error,

Event ID: 1000,

Faulting app name: mmc.exe , ver 10.0.20348.2520,

Faulting module clr.dll, ver: 4.8.4749.0,

Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll,

Local ID: 1033.

Operating system: Microsoft Server 2022 std

Please, help me to fix it. Thanks

Answer 1

Hello

Thank you for posting in Microsoft Community forum.

The crash you're experiencing with Hyper-V Manager when accessing the Hyper-V Settings or Replication Configuration is associated with an application error (Event ID: 1000) involving mmc.exe and clr.dll. This issue can be related to various factors, including corrupted settings, problematic configurations, or issues with the .NET Framework. Here are some steps you can try to resolve the issue:

Check for Updates: Ensure that your Windows Server 2022 and Hyper-V Manager are up to date with the latest patches and updates. Sometimes, updates can resolve underlying issues.

Reset Hyper-V Settings: You can try resetting the Hyper-V settings to default. This can be done by deleting specific registry keys related to Hyper-V. However, be cautious when modifying the registry, and consider backing it up first. The keys to look for are:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmsmp\parameters\NicList

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmsmp\parameters\SwitchList

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HNS

Network Reset: Perform a network reset to clear any network-related issues. Go to Settings -> Network & Internet -> Advanced Network Settings -> Network Reset -> Reset Now.

Winsock Reset: Reset the Winsock catalog to a clean state. Open Command Prompt as an administrator and run the command: netsh winsock reset.

Check Event Viewer: Review the Event Viewer logs for any additional errors or warnings that might provide more insight into the issue. Look for related events around the time of the crash.

Procmon Analysis: Use Process Monitor (Procmon) to capture detailed logs of the crash. This can help identify the specific operations or registry keys causing the issue.

Process Monitor - Sysinternals | Microsoft Learn

Best Regards,

Wesley Li