1. Verify Network Connectivity:
Ensure your system is connected to the internet or corporate network. Use ping to test basic connectivity:
ping google.com
ping <your_kms_server>
2. Flush and Reset DNS Cache:
Open Command Prompt as Administrator and run:
ipconfig /flushdns
ipconfig /registerdns
3. Set KMS Server Manually (If Known):
If your organization uses a custom KMS host:
slmgr.vbs /skms kms.yourcompany.com
slmgr.vbs /ato
4. Temporarily Disable Firewall/Proxy:
Disable any third-party firewalls, antivirus, or VPNs that may block port 1688 used by KMS.
5. Switch to MAK Activation (for non-KMS users):
If you’re not part of a domain or don’t have a KMS host, use a MAK key:
slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
slmgr.vbs /ato
6. Ensure Required Services Are Running:
Open services.msc and check the following:
- Software Protection (sppsvc) – Running
- Network Location Awareness – Running
- Restart these services if they are stopped.
7. Check Domain Membership (Enterprise Only):
Go to Settings → System → About and ensure the device is joined to your organization’s domain.
8. Use the Activation Troubleshooter:
Go to Settings → Update & Security → Activation → Troubleshoot.
This tool can detect and fix common activation issues automatically.
9. Use VAMT for Bulk or Remote Activation:
For IT admins, Microsoft’s Volume Activation Management Tool (VAMT) helps track and manage multiple KMS clients and troubleshoot errors.
10. Contact Microsoft Support if Issue Persists:
If none of the above works, especially in licensed environments, contacting Microsoft support can help resolve backend licensing issues.