EC2 Windows: Recovering Server Manager After Uninstalling .NET

Do not treat ".NET Framework 4 Features" as a regular application and uninstall it on Windows Server. It is a dependency for many management components, including Server Manager, PowerShell modules, and IIS/WCF-related features. Disabling it by mistake can cause both Server Manager and Install-WindowsFeature to stop working.

Symptoms

After unchecking .NET Framework 4 in Server Manager's "Remove Roles and Features" and rebooting the instance:

• Server Manager won't open.
• PowerShell reports the ServerManager command is not recognized.
• Install-WindowsFeature reports the feature name doesn't exist.
• Some PowerShell management capabilities stop working.

Example error:

ServerManager : The term 'ServerManager' is not recognized

Root Cause

Windows Server's Server Manager and related PowerShell modules depend on NetFx4-OC-Package. Unchecking .NET Framework 4 Features in the GUI actually disables a batch of OC packages that depend on NetFx4.

This is not the same as the .NET Framework 4.8 runtime version. The registry may still show .NET 4.8 is present, but the Windows optional component NetFx4 has been disabled.

Additionally, NetFx3 cannot substitute for NetFx4. Running:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

will not restore Server Manager, which depends on .NET 4.

Recovery Steps

Before proceeding, it is recommended to create an AMI backup. All commands should be run as administrator.

1. Enable NetFx4

DISM /Online /Enable-Feature /FeatureName:NetFx4 /All

2. Enable Server Manager GUI Management Components

DISM /Online /Enable-Feature /FeatureName:Server-Gui-Mgmt /All

3. Reboot the Instance

shutdown /r /t 0

Verify after rebooting.

4. Restore Other Dependent Components as Needed

If your workload uses IIS, WCF, PowerShell ISE, or DSC, enable them as needed:

DISM /Online /Enable-Feature /FeatureName:NetFx4Extended-ASPNET45 /All
DISM /Online /Enable-Feature /FeatureName:WCF-HTTP-Activation45 /All
DISM /Online /Enable-Feature /FeatureName:WCF-TCP-PortSharing45 /All
DISM /Online /Enable-Feature /FeatureName:IIS-ASPNET45 /All
DISM /Online /Enable-Feature /FeatureName:IIS-NetFxExtensibility45 /All
DISM /Online /Enable-Feature /FeatureName:MicrosoftWindowsPowerShellISE /All
DISM /Online /Enable-Feature /FeatureName:DSC-Service /All

Verification

ServerManager
Get-Command Install-WindowsFeature
DISM /Online /Get-Features | findstr /I "NetFx4 Server-Gui PowerShell"

Summary

To meet .NET version compliance requirements, the correct approach is to install .NET cumulative updates, not to disable .NET Framework 4 Features. The latter does not make .NET "safely disappear" from the system — instead, it breaks the Windows Server management toolchain.

During recovery, enabling NetFx4 alone is not enough — you must also enable Server-Gui-Mgmt and reboot.