Most system admins and developers are complaining about the System.NullReferenceException error message, which basically crashes the console when users try to access virtual machines or change their properties. All the impacted users confirm everything was working perfectly fine before the upgrade, and concluded the Anniversary Update is the element that ruined it all.
Windows 10 v1607 crashes virtual machine admin consoles
I upgraded my Admin PC to Windows 10 1607. When i open the VMM console and try to open the properties of a VM the console crashes. We reinstalled Windows 10 and VMM console on one PC with the ISO from the VLSC. Same thing happens. [..]Changing the language of the console to english doesn’t help. The console worked fine in Windows 10 1511 before the upgrade.
The error looks like this in the event log:
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Microsoft.VirtualManager.UI.WpfControls.ElementHostGC.GetFieldValue[[System.__Canon, mscorlib, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Type, System.String)
It appears these crashes are caused by incompatibility issues between the VMMs and Windows 10 v1607 since so many users are plagued by the same issue immediately after upgrading to the latest Windows version. All evidence indicates that Microsoft doesn’t support installing the VMM Admin Console on Windows 10 v 1607, but no official information is available yet.
Microsoft hasn’t acknowledged this issue yet. It’s indeed a bug and not a compatibility issue. We’ve scoured the internet hoping to find a fix for these crashes, but we couldn’t find any.
If you’ve found a workaround for these VMM Admin Console crashes on Windows 1607, share it with the community in the comment section below.
RELATED STORIES YOU NEED TO CHECK OUT: