Force Windows Activation Command Line

  1. Force Windows Activation Command Line Chrome
  2. Run Command Windows 10 Activation
  • 3Replace Product Key with KMS Client Key
  • 6Activate


This article gives the commands to activate a Windows system to a KMS licensing server. This applies to Vista or later.


  • Windows must have been installed from volume licensing (VL) media.
  • Open Command Prompt as Administrator
Force Windows Activation Command Line

Replace Product Key with KMS Client Key

  • Use the Windows key + R keyboard shortcut to open the Run command. Type changepk.exe and click OK to open the Windows activation client. Enter the 25-digit product key for the version of Windows 10 you want. Click Next to complete the task.
  • Slmgr activate command will force Windows to attempt online activation with Microsoft’s servers. If the system is set up to use a KMS activation server, it will instead attempt activation with the KMS server on the local network.
  • A command prompt window would be opened in the Administrator mode. Step Two: Type the Following Commands. Once you are in the command prompt window, type the following commands as it is, make sure that you press enter after every line and take care of the spaces and tabs. Slm /ipk NG4HW-VH26C-733KW-K6F98-J8CK4. Slmgr /skms lunar21.

Jul 27, 2017 After you configure Active Directory-based activation, start a computer that is running an edition of Windows that is configured by volume licensing. If the computer has been previously configured with a MAK key, replace the MAK key with the GVLK by running the slmgr.vbs /ipk command and specifying the GLVK as the new product key.

Determine if a KMS Client key is installed


VOLUME_MAK_B channel in the description. That stands for Multiple Activation Key and is not a KMS client key.

Obtain a KMS Client Key

The KMS client keys are universal to all customers and a list of them can be found on the Microsoft Technet web site HERE.

Uninstall Current Key (Optional)

The Install command replaces the existing key.

Install KMS Client Key


Take note of the VOLUME_KMSCLIENT channel in the description.

Determine if KMS Host Has Service Record in DNS

Set KMS Server Manually (Skip if in DNS)

If your network does not support DDNS, you need to manually assign a KMS host to your KMS clients. Manually assigning a KMS host disables auto-discovery of KMS on a KMS client.



Static Registered KMS Server Example

Take note of the key name Registered KMS machine name.

Dynamic DNS Registered KMS Server Example

Take note of the KMS machine name from DNS.

Related Articles

  • (Reference) KMS Client Keys


Retrieved from ''

Applies to

  • Windows 10
  • Windows 8.1
  • Windows 8
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Server 2016
  • Windows Server 2019
  • Office 2013*
  • Office 2016*
  • Office 2019*

Looking for retail activation?

Active Directory-based activation is implemented as a role service that relies on AD DS to store activation objects. Active Directory-based activation requires that the forest schema be updated using adprep.exe on a supported server OS, but after the schema is updated, older domain controllers can still activate clients.

Any domain-joined computers running a supported operating system with a Generic Volume License Key (GVLK) will be activated automatically and transparently. They will stay activated as long as they remain members of the domain and maintain periodic contact with a domain controller. Activation takes place after the Licensing service starts. When this service starts, the computer contacts AD DS automatically, receives the activation object, and is activated without user intervention.

Force windows activation command line linux

Force Windows Activation Command Line Chrome

To allow computers with GVLKs to activate themselves, use the Volume Activation Tools console or the Volume Activation Management Tool (VAMT) in earlier versions of Windows Server to create an object in the AD DS forest. You create this activation object by submitting a KMS host key to Microsoft, as shown in Figure 10.

The process proceeds as follows:

  1. Perform one of the following tasks:

    • Install the Volume Activation Services server role on a domain controller and add a KMS host key by using the Volume Activation Tools Wizard.
    • Extend the domain to the Windows Server 2012 R2 or higher schema level, and add a KMS host key by using the VAMT.
  2. Microsoft verifies the KMS host key, and an activation object is created.

  3. Client computers are activated by receiving the activation object from a domain controller during startup.

    Figure 10. The Active Directory-based activation flow

For environments in which all computers are running an operating system listed under Applies to, and they are joined to a domain, Active Directory-based activation is the best option for activating all client computers and servers, and you may be able to remove any KMS hosts from your environment.

If an environment will continue to contain earlier volume licensing operating systems and applications or if you have workgroup computers outside the domain, you need to maintain a KMS host to maintain activation status for earlier volume licensing editions of Windows and Office.

Run Command Windows 10 Activation

Clients that are activated with Active Directory-based activation will maintain their activated state for up to 180 days since the last contact with the domain, but they will periodically attempt to reactivate before then and at the end of the 180 day period. By default, this reactivation event occurs every seven days. Full undertale ost download torrent.

When a reactivation event occurs, the client queries AD DS for the activation object. Client computers examine the activation object and compare it to the local edition as defined by the GVLK. If the object and GVLK match, reactivation occurs. If the AD DS object cannot be retrieved, client computers use KMS activation. If the computer is removed from the domain, and the computer or the Software Protection service is restarted, the operating system will change the status from activated to not activated, and the computer will try to activate with KMS.

Step-by-step configuration: Active Directory-based activation


You must be a member of the local Administrators group on all computers mentioned in these steps. You also need to be a member of the Enterprise Administrators group, because setting up Active Directory-based activation changes forest-wide settings.

To configure Active Directory-based activation on Windows Server 2012 R2 or higher, complete the following steps:

  1. Use an account with Domain Administrator and Enterprise Administrator credentials to sign in to a domain controller.

  2. Launch Server Manager.

  3. Add the Volume Activation Services role, as shown in Figure 11.

    Figure 11. Adding the Volume Activation Services role

  4. Click the link to launch the Volume Activation Tools (Figure 12).

    Figure 12. Launching the Volume Activation Tools

  5. Select the Active Directory-Based Activation option (Figure 13).

    Figure 13. Selecting Active Directory-Based Activation

  6. Enter your KMS host key and (optionally) a display name (Figure 14).

    Figure 14. Entering your KMS host key

  7. Activate your KMS host key by phone or online (Figure 15).

    Figure 15. Choosing how to activate your product


    To activate a KMS Host Key (CSVLK) for Microsoft Office, you need to install the version-specific Office Volume License Pack on the server where the Volume Activation Server Role is installed.

  8. After activating the key, click Commit, and then click Close.

Verifying the configuration of Active Directory-based activation

To verify your Active Directory-based activation configuration, complete the following steps:

  1. After you configure Active Directory-based activation, start a computer that is running an edition of Windows that is configured by volume licensing.

  2. If the computer has been previously configured with a MAK key, replace the MAK key with the GVLK by running the slmgr.vbs /ipk command and specifying the GLVK as the new product key.

  3. If the computer is not joined to your domain, join it to the domain.

  4. Sign in to the computer.

  5. Open Windows Explorer, right-click Computer, and then click Properties.

  6. Scroll down to the Windows activation section, and verify that this client has been activated.


    If you are using both KMS and Active Directory-based activation, it may be difficult to see whether a client has been activated by KMS or by Active Directory-based activation. Consider disabling KMS during the test, or make sure that you are using a client computer that has not already been activated by KMS. The slmgr.vbs /dlv command also indicates whether KMS has been used.

    To manage individual activations or apply multiple (mass) activations, please consider using the VAMT.

See also