Fix 'Server Manager not available' on Server 2016

Quick answer: Delete the contents of C:\Windows\System32\ServerManager\ and restart Server Manager. If that doesn't work, reinstall .NET Framework 4.7 and run DISM.

I know this error is infuriating. You click the Server Manager tile on the taskbar, and instead of the dashboard, you get a pop-up saying "Server Manager is not available." It feels like the whole OS is broken, but it's not. This usually happens after a Windows Update or when .NET Framework gets corrupted. The server itself is fine—it's just the management console that's choking.

Here's the thing: Server Manager depends on .NET Framework 4.7 and a bunch of cached XML and DLL files. If those files get locked or corrupted—often after a reboot following an update—the console refuses to start. The fix is straightforward, but you have to do it in the right order.

Fix Steps

Clear the Server Manager cache. This is the quickest fix and works most of the time. Stop the Server Manager process first:
```
Stop-Process -Name ServerManager -Force
```
Then delete the contents of the cache folder:
```
Remove-Item C:\Windows\System32\ServerManager\* -Recurse -Force
```
Wait a few seconds, then start Server Manager from the Start menu. The cache rebuilds automatically.
Check .NET Framework 3.5 and 4.7. Server Manager relies on both. Open PowerShell as admin and run:
```
Get-WindowsFeature NET-Framework-Core, NET-Framework-45-Core
```
If either shows Removed or Disabled, install them:
```
Install-WindowsFeature NET-Framework-Core, NET-Framework-45-Core
```
You might need the installation media if the source isn't local.
Run DISM and SFC. Corruption in system files can break Server Manager. In an admin command prompt:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
After that finishes, run:
```
sfc /scannow
```
Reboot and test.
Reset the Server Manager service. Yes, Server Manager runs as a service, even though you don't see it. In PowerShell:
```
Restart-Service -Name ServerManager -Force
```
If the service doesn't exist, you might need to re-enable it:
```
Set-Service ServerManager -StartupType Automatic; Start-Service ServerManager
```

Alternative Fixes If the Above Fails

If clearing the cache and repairing .NET didn't do it, try these in order:

Create a new user profile. A corrupted profile can block Server Manager. Create an admin user, log in as that user, and see if Server Manager opens. If it does, migrate your settings and ditch the old profile.
Use DISM with the Windows Server 2016 ISO. If SFC can't repair files, mount the ISO and use the source option:
```
DISM /Online /Cleanup-Image /RestoreHealth /Source:wim:E:\Sources\install.wim:1 /LimitAccess
```
Replace E: with your DVD drive letter.
Install the latest cumulative update. Microsoft patched several Server Manager bugs in 2018 and 2019 updates. If you're running an older build, that alone could be the issue. Check your build number with winver and install updates from Microsoft Update Catalog.

Prevention Tip

The number one cause of this error is a botched Windows Update that leaves .NET Framework in a weird state. To prevent recurrence, make sure your server has the latest updates installed, and if you're using WSUS, verify the .NET Framework branch is approved. Also, don't kill Server Manager processes manually unless you're troubleshooting—sometimes that leaves stale locks.

Another thing: if you're running Server Core (no GUI), Server Manager is not available by design. You need to use PowerShell or RSAT. But since you're seeing the error on a full GUI install, that's not the case here.

I've seen this error pop up randomly even on healthy servers. Nine times out of ten, clearing the cache fixes it in under a minute. If you're still stuck after trying everything, consider a repair install of Windows Server—but that's a last resort. Most people don't need to go that far.

Hope this gets you back to managing your server. Let me know in the comments if you're still seeing the error—I'll help you dig deeper.