Windows Server Evaluation editions allow administrators to test features such as file services, virtualization, networking, and server management before purchasing a full license.
When testing is complete, a supported Windows Server Evaluation installation may be converted to a fully licensed edition using DISM and a genuine product key. The conversion can preserve existing roles, applications, settings, and data when the target edition is supported.
Important: Always create a tested backup before changing the server edition. Do not interrupt the process after it starts, and do not use a product key that does not match the target Windows Server edition.
Before Converting Windows Server
Edition conversion is a system-level change. Review the server role, license, backup status, and supported upgrade path before running DISM.
Important Domain Controller Limitation
Microsoft does not support converting a Windows Server Evaluation Domain Controller directly to a retail or fully licensed edition.
If the Evaluation server is a Domain Controller, the supported approach is to install a new licensed Windows Server, join it to the domain, promote it to a Domain Controller, transfer the FSMO roles, verify replication, and then demote and remove the old Evaluation Domain Controller.
Do not run the edition-conversion command on a production Domain Controller unless Microsoft documentation and your migration plan specifically support the scenario.
Back Up the Server
Before starting the conversion:
- Create a full system or image backup.
- Back up application databases and shared folders separately.
- Record installed server roles and features.
- Record network settings, IP addresses, DNS settings, and firewall rules.
- Confirm that you can restore the backup before changing the edition.
- Schedule maintenance time for one or more restarts.
Confirm Administrator Access
You must use an account with local administrator privileges. On a remote server, confirm that you have console or out-of-band recovery access in case the server does not restart normally.
Disconnecting a remote session during the conversion can prevent you from seeing restart prompts. Use a reliable console connection whenever possible.
Check the Current and Supported Editions
Never assume that every Evaluation edition can convert directly to every retail edition. DISM must report the target edition as supported.
Get the Current Edition
Open an elevated Command Prompt or Windows Terminal and run:
DISM /Online /Get-CurrentEditionRecord the edition returned by DISM. It may be an Evaluation edition such as ServerStandardEval or ServerDatacenterEval.
Get the Supported Target Editions
Run the following command:
DISM /Online /Get-TargetEditionsReview the list returned by DISM. Continue only when the intended target edition appears in the results.
Use a Supported Conversion Path
If the target edition is not listed by Get-TargetEditions, do not force the conversion. Use a clean installation or a documented migration path.
Match the Product Key
The product key must correspond to the Windows Server version and target edition selected in the DISM command.
Convert Windows Server with DISM
After confirming the supported target edition and preparing a backup, apply the genuine product key with the DISM Set-Edition command.
Open Command Prompt as Administrator
- Open the Start menu.
- Search for Command Prompt.
- Right-click the result.
- Select Run as administrator.
- Select Yes if User Account Control appears.
You can also open an elevated Command Prompt using the on-screen keyboard:
- Press Ctrl + Shift + Esc to open Task Manager.
- Select File > Run new task.
- Enter
cmd. - Select Create this task with administrative privileges.
- Select OK.
Convert to Server Standard
Use this command only when ServerStandard appears in the supported target editions and your product key is for the matching Windows Server Standard version.
DISM /Online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEulaReplace the placeholder with your genuine 25-character product key. Do not include brackets or quotation marks.
Convert to Server Datacenter
Use this command only when ServerDatacenter appears in the supported target editions and your product key is for the matching Windows Server Datacenter version.
DISM /Online /Set-Edition:ServerDatacenter /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEulaDo not attempt to convert between unsupported editions. For example, a Datacenter Evaluation installation may not support a direct conversion to Standard Retail.
Restart the Server
DISM may request a restart or restart the server automatically.
- Save all open work before running the conversion.
- Do not shut down the server while DISM is processing.
- Allow every restart to finish.
- If DISM asks for confirmation, press Y only after verifying the maintenance window.
- Reconnect to the server after Windows starts normally.
The conversion may take several minutes depending on the installed roles, storage performance, and server hardware.
Verify the Edition and Activation
Check the Installed Edition
Open an elevated Command Prompt and run:
DISM /Online /Get-CurrentEditionThe result should show the intended full edition, such as ServerStandard or ServerDatacenter, instead of an Evaluation edition.
Check Windows Server Activation
A successful edition change does not automatically prove that activation is complete. Verify the activation state separately using the Windows Server activation interface or the appropriate licensing command for your environment.
Check the following:
- The installed edition matches the purchased license.
- The product key was accepted without an error.
- The server can reach the required activation services.
- The system date and time are correct.
- The server is not using an expired evaluation license.
Verify Server Roles and Services
After the restart, confirm that critical services are operating normally.
- Open Server Manager.
- Review the installed roles and features.
- Check DNS, DHCP, file services, IIS, Hyper-V, or other installed roles.
- Confirm that shared folders and business applications are available.
- Review Event Viewer for new servicing or activation errors.
Troubleshoot Conversion Failures
| Problem | What to Check | Next Action |
|---|---|---|
| Unsupported target edition | Run DISM /Online /Get-TargetEditions. |
Use only a target edition listed by DISM or perform a supported migration. |
| Invalid product key | Confirm that the key belongs to the exact Windows Server version and edition. | Correct the key or contact the license supplier. |
| Pending restart | Check Windows Update and recently installed server roles. | Restart the server, verify normal operation, and retry only if the target remains supported. |
| Component-store error | Review the complete DISM error and servicing logs. | Repair Windows components before attempting the edition conversion again. |
| Activation problem | Verify connectivity, time settings, edition, and product key status. | Resolve activation separately after confirming that the edition conversion succeeded. |
If DISM Returns an Error
- Record the complete error code and message.
- Confirm the output of
Get-CurrentEdition. - Confirm that the target appears in
Get-TargetEditions. - Verify that the product key matches the target edition.
- Check for a pending restart.
- Review the DISM and Windows servicing logs.
- Restore the server from backup if the system becomes unstable.
Production Server Precautions
For a production server, test the conversion on a backup or lab system first. Confirm application compatibility, maintenance-window duration, recovery access, and rollback procedures before changing the production installation.
After the Conversion
- Run
DISM /Online /Get-CurrentEditionagain. - Verify Windows Server activation.
- Check all installed server roles.
- Confirm network connectivity and DNS resolution.
- Test file shares, applications, databases, and scheduled tasks.
- Review Event Viewer for critical errors.
- Install current security and hardware updates.
- Create a new backup after the server is confirmed healthy.
- Record the new edition and license information for future administrators.
Frequently Asked Questions
Why is only my Windows key not working?
A gaming keyboard’s Win Lock feature, keyboard remapping software, or a Scancode Map Registry value may be disabling the key. Check those settings before repairing Windows.
How do I unlock the Windows key on a gaming keyboard?
Look for a Win Lock, Gaming Mode, Windows-logo, lock, or controller key. The shortcut may require the Fn key. Check the keyboard manufacturer’s instructions for the exact combination.
What does it mean if the on-screen Windows key works?
It indicates that Windows can process the key and that the problem is probably related to the physical keyboard, its driver, a Win Lock function, or keyboard-control software.
What if the Windows key works but the Start menu does not open?
Restart Windows Explorer, test another user account, and run DISM followed by System File Checker. The Start menu or user profile may be damaged.
Is it safe to delete Scancode Map from the Registry?
Only delete it after exporting a backup and confirming that it was not intentionally created by a keyboard-remapping tool. If the value does not exist, do not create or change anything in that location.
Will SFC or DISM delete my personal files?
These tools repair Windows components and normally do not delete personal files. You should still maintain a current backup before performing system repairs.
Can restarting the computer fix the Windows key?
Yes. Restarting can reload keyboard drivers, Windows Explorer, background services, and device-control software. Use Restart rather than shutting down and immediately turning the computer back on.
Can I continue using Windows 10 after support ends?
Windows 10 will continue to operate, but regular support ended on October 14, 2025. Unsupported systems face increasing security, software, and hardware compatibility risks.
Conclusion
Converting Windows Server Evaluation to a full licensed edition with DISM can avoid a complete reinstall when the target edition is supported. The process requires administrator access, a genuine matching product key, a verified backup, and a planned restart window.
Always run Get-CurrentEdition and Get-TargetEditions before applying the edition-change command. After the restart, verify the edition, activation, server roles, applications, network services, and event logs.
For Domain Controllers and other critical production systems, use a documented migration plan instead of attempting an unsupported direct conversion.
Need a genuine Windows Server license? View Windows Server products.
