Fix ERROR_NOT_SUPPORTED_ON_STANDARD_SERVER (0X00002188)
This error shows up on Standard Windows Server when you try a feature that needs Datacenter edition. The fix is checking your SKU and swapping licenses.
When does this error appear?
You'll see error 0X00002188 — ERROR_NOT_SUPPORTED_ON_STANDARD_SERVER when you try to enable a feature that only works on Windows Server Datacenter edition. The most common triggers are:
- Enabling Storage Spaces Direct (S2D) in Failover Cluster Manager
- Configuring Storage Replica for a Hyper-V replica
- Running a PowerShell cmdlet like
Enable-ClusterStorageSpacesDirect - Setting up Shielded VMs or Host Guardian Service
The error itself is straightforward: the OS checks its edition at runtime and says "nope, you're on Standard." It's not a corrupt file or driver issue — it's an edition check that fails.
Root cause in plain English
Windows Server comes in two main flavors: Standard and Datacenter. Standard is cheaper and good for most workloads. But features like Storage Spaces Direct, Storage Replica, and Shielded VMs are Datacenter-only. Microsoft locks them at the kernel level. When you try to call those APIs on Standard, the OS returns 0X00002188.
There's no workaround, no registry hack, no DLL swap that'll bypass it. The real fix is to upgrade your edition. Period.
Fix: Upgrade from Standard to Datacenter
Here's the step-by-step. You'll need a valid Datacenter license key.
- Check your current edition. Open Command Prompt as Administrator (right-click and run as admin). Type:
You should see output likeDISM /online /Get-CurrentEditionServerStandard. If it saysServerDatacenter, you're already on the right edition and the error is from something else — skip to the troubleshooting section below. - See what edition you can upgrade to. Type:
Look forDISM /online /Get-TargetEditionsServerDatacenterin the list. If you don't see it, your current installation doesn't support a direct upgrade — you'll need to reinstall using Datacenter media. That's rare, but possible if you're on a very old build. - Start the edition upgrade. Type this command, replacing
XXXXX-XXXXX-XXXXX-XXXXX-XXXXXwith your actual Datacenter key:
Hit Enter. This runs silently for about 5–10 minutes. After it finishes, you'll see a message like "The operation completed successfully."DISM /online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula - Restart the server. Type:
The server reboots. This is a normal restart — not a full reinstall. Your roles, features, files, and settings stay intact.shutdown /r /t 0 - Verify the edition after reboot. Log back in and run:
It should now sayDISM /online /Get-CurrentEditionServerDatacenter. You can also check in System Properties (Win + Pause/Break) — it'll show "Windows Server Datacenter." - Try your original action again. Go back to whatever triggered the error (e.g., enable Storage Spaces Direct). It should work without the 0X00002188 error.
What if it still fails?
If the error persists after upgrading, a few things could be wrong:
- You upgraded to the wrong channel. Check if you're on Server Core vs Desktop Experience. The error can also appear if you try to add a GUI component on Core — run
Get-WindowsFeaturein PowerShell to see installed features. - You're running an Insider or evaluation build. Those sometimes have edition flags that don't match. Run
slmgr /dlvand look at the description. If it says "Evaluation" or "Insider", you need a retail license. - You're hitting a different error with the same code. Unlikely, but possible. Check the System event log (Event Viewer > Windows Logs > System) for additional details around the time of the error.
- The feature still needs extra configuration. For example, Storage Spaces Direct also requires a cluster setup with matching hardware. The edition error is gone, but now you need to meet the hardware requirements (SSDs, networking, etc.).
If you've confirmed you're on Datacenter and the error still appears, open a support case with Microsoft. Include the output of DISM /online /Get-CurrentEdition and the exact command that triggers the error.
Was this solution helpful?