Net Framework 4.0 V 30319 Windows 10

[Marine Farinha]

ApplicationServerManager.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.BadImageFormatException

at Microsoft.Windows.ServerManager.AppLoader.Load(Microsoft.Windows.ServerManager.Common.ArgumentsProcessor)

at Microsoft.Windows.ServerManager.SingleInstanceAppLauncher.StartApplication(Microsoft.Windows.ServerManager.Common.ArgumentsProcessor)

at Microsoft.Windows.ServerManager.MainApplication.Main(System.String)

If the above does not resolve the issue, you may consider switching to an alternative option, which is using RSAT on any other Windows machine to manage that server remotely -us/download/details.aspx?id=45520 .

Even better option would be using the new Windows Admin Center -us/windows-server/windows-admin-center for management purposes. It is web-based and does not require RDP, just your favorite browser. Installation and configuration are extremely easy and straightforward -admin-center-for-windows-server-2019-getting-started .

Playing around with .NET Framework never worked for me in terms of fixing something but may completely break lots of things within Windows Server so do it carefully. A perfect decision to make a backup prior to reinstalling it.

Some applications just do not co-exist alongside, especially those legacy ones mentioned. That said, consider using Windows Admin Center or RSAT running on a different machine. That can be a virtual one, obviously, or any of your Windows 10 laptops. You may need to adjust the configuration on the server for remote access to work correctly Allow Remote Connections on Another Computer .

@Yoann same issue here. Clean install of Windows Server 2019 latest build, install .NET Framework offline installer 4.8, reboot and boom. Many native control panels, like Server Manager, requesting some 4.0.... version of .NET framework instead, failing to load.

I had the same issue and received zero help or support from Microsoft. Dell support googled and read back to me everything I had googled and tried already. Importing the above registry information fixed it without a reboot.

@DavidSherrill This is the exact fix! For us, our RMM tool stopped working on a server 2019 standard server. It's services wouldn't start. Event Viewer complained about .net. Also server manager wouldn't open with the exact message you mentioned. Applying this fixed it all. thanks!!

YOU ARE AN ABSOLUTE LEGEND! THANK YOU! THIS IS THE ONLY SOLUTION THAT WORKED! Every other solution I've googled of this problem has been some variation of "turn net framework on/off in the "turn windows features on or off" app" or "reinstall the newest version of .net" or "did you try restarting your computer?" (OF COURSE I TRIED RESTARTING MY COMPUTER!! DO THEY THINK I'M AN INFANT??)

Please excuse my novice status displayed in this question, but does one simply copy/paste the text in your registry update file, and does the resulting text file require the line number entries as displayed in your post?

3a8082e126