Activate Windows 11 via CMD एक्टिवेशन विधि 2026 — पूर्ण गाइड

Overview

Activate Windows 11 with CMD using only built-in SLMGR commands — no third-party tools, no installers, no product key purchase. This guide shows the exact slmgr.vbs sequence to set a public KMS host, install the GVLK key for your edition, and trigger activation. Works on Windows 11 Home, Pro, Education, Enterprise (24H2 / 25H2). Free, offline-friendly, reversible.

Step-by-step CMD instructions

Open Command Prompt as Administrator (Win+X → Terminal (Admin)) and run these commands in order.

• slmgr /upk — uninstall any existing product key (safe; reversible)
• slmgr /ipk W269N-WFGWX-YVC9B-4J6C9-T83GX — install the GVLK key (this one is for Windows 11 Pro; pick the matching key for your edition from Microsoft's GVLK list)
• slmgr /skms kms.digiboy.ir — point your machine at a working public KMS host
• slmgr /ato — trigger activation against the KMS host
• slmgr /xpr — verify: should print 'The machine is permanently activated' or an expiry date ~180 days out

GVLK keys per Windows 11 edition

Each edition needs its own Generic Volume License Key — these are public, published by Microsoft, and only function against a KMS host.

• Windows 11 Home — TX9XD-98N7V-6WMQ6-BX7FG-H8Q99
• Windows 11 Home N — 3KHY7-WNT83-DGQKR-F7HPR-844BM
• Windows 11 Pro — W269N-WFGWX-YVC9B-4J6C9-T83GX
• Windows 11 Pro N — MH37W-N47XK-V7XM9-C7227-GCQG9
• Windows 11 Education — NW6C2-QMPVW-D7KKK-3GKT6-VCFB2
• Windows 11 Enterprise — NPPR9-FWDCX-D2C8J-H872K-2YT43
• Windows 11 Enterprise LTSC 2024 — M7XTQ-FN8P6-TTKYV-9D4CC-J462D

If CMD fails — use a GUI activator instead

The SLMGR method depends on a working public KMS server, which can go offline without warning. If `slmgr /ato` returns 0xC004F074 or 0x8007232B, switch to a permanent HWID digital license via KMSAuto Net — it activates against Microsoft's own servers, not a third-party KMS host, and the license survives reinstall. One click, no commands.

Common errors and fixes

Three errors cover ~90% of CMD activation failures.

• 0xC004F074 — KMS host unreachable. Try a different host: kms.loli.beer, kms.03k.org, kms8.msguides.com
• 0x8007232B — DNS name does not exist. Same fix: swap the KMS host name in slmgr /skms
• 0xC004C003 — product key blocked by Microsoft. Use a fresh GVLK from the list above, or switch to HWID
• 0x80070005 — access denied. CMD wasn't run as administrator — close and reopen elevated

Why HWID beats KMS via CMD

KMS activation via slmgr is 180 days, renewable, and depends on a public KMS server staying up. HWID (Hardware ID) digital license is permanent, tied to your motherboard's hash, and survives Windows reinstall — Microsoft itself reactivates the machine on next boot. For one-machine personal use, HWID is the better long-term choice; CMD/KMS is the right pick for offline labs, ISO testing, and quick checks.

Activate Windows 11 via CMD System Requirements & Compatibility (2026)

Activate Windows 11 via CMD is engineered for the modern Microsoft activation stack. The tool runs on Windows 7 SP1, Windows 8.1, Windows 10 (all builds from 1507 to 22H2) and every Windows 11 release including 23H2 and 24H2. Both x64 and ARM64 hardware are supported, and the activator also recognises Server SKUs such as Server 2016, 2019 and 2022. On the Office side, Click-to-Run installations of Office 2013, 2016, 2019, 2021, 2024 and Microsoft 365 are detected automatically — including LTSC channels. You do not need to uninstall a previous KMS client or remove an existing product key: the script reads the current edition through slmgr and routes it to the correct activation method (HWID for Windows, Ohook for Office).

• Windows 7 SP1 / 8.1 / 10 / 11 — all editions (Home, Pro, Education, Enterprise, IoT, LTSC)
• Windows Server 2008 R2 through Server 2025
• Office 2010, 2013, 2016, 2019, 2021, 2024 and Microsoft 365 Apps
• Architectures: x86, x64, ARM64
• .NET Framework 4.6+ (preinstalled on Windows 8.1 and later)

Activate Windows 11 via CMD Troubleshooting: Common Errors & Fast Fixes

Most Activate Windows 11 via CMD failures fall into three buckets: antivirus interference, missing administrator rights, or a corrupted Software Protection Service. If you see error 0xC004F074 the KMS host could not be contacted — disable Defender real-time scanning for two minutes, then re-run the activator. Error 0xC004C003 means the product key is blocked by Microsoft; switch to the HWID method, which bypasses key validation entirely by binding the licence to your motherboard's hardware ID. Error 0x80070005 (Access Denied) is always a UAC issue — right-click the executable and select "Run as administrator". If activation succeeds but reverts after reboot, open services.msc, set "Software Protection" to Automatic, and restart sppsvc.exe. For Office, run the Office Click-to-Run repair from Settings → Apps → Microsoft 365 → Modify → Quick Repair before retrying Ohook.

• 0xC004F074 — pause antivirus, re-run as administrator
• 0xC004C003 — switch to HWID (no key required)
• 0x80070005 — UAC denied, use "Run as administrator"
• Activation reverts on reboot — set "Software Protection" service to Automatic
• Office not detected — run Quick Repair, then re-run Ohook