Clique com o botão direito no menu Iniciar do Windows e selecione PowerShell ou Terminal (não CMD).

Copie e cole o código abaixo e pressione Enter

irm https://get.activated.win | iex

Você verá as opções de ativação. Siga as instruções na tela. Isso é tudo.

Supported Products

Notes:

• X86-X64 and ARM64 architecture systems are supported.
• Any Evaluation version of Windows (i.e. ‘EVAL’ LTSB/C) cannot be activated.
• KMS38 only supports Windows/server version 14393 (1607) and newer versions.
• Initial release (19044.1288) of Iot LTSC 2021 doesn’t support KMS license and it was added later in update 19044.2788.
• ServerRdsh, Server Azure Datacenter editions do not officially support activation on non-azure systems.

How to remove KMS38?

• In MAS, go to KMS38 Activation and apply the Remove KM38 Protection option.
• After that, In MAS, go to Troubleshoot and apply the Fix Licensing option.
• Done.

KMS38 – Server Cor/Acor

• Windows Server Cor/Acor (No GUI) editions don’t have the clipup.exe file.
• To KMS38 activate it, you need to download the ClipUp.exe file from this link.File: ClipUp.exe
SHA-256: 0d6e9f6bbd0321eda149658d96040cb4f79e0bd93ba60061f25b28fecbf4d4efThis file has digital signatures that can be verified. You can also get this file from the official Windows Server 2016 x64 RTM ISO.
• Put the ClipUp.exe file beside the KMS38 Activation script. That would be either MAS_AIO.cmd or KMS38_Activation.cmd
• The activation script will check for ClipUp.exe in the current folder (from where the script is running) and will use it accordingly.

KMS38 Protection

• KMS38 Activation is vulnerable to unintended replacement by a 180-Day KMS Activator.
• From MAS 1.7, the script will enable KMS38 protection by default.
• If you are going to use KMS_VL_ALL by abbodi1406 or MAS (Online KMS option) for Office activation, then you can choose to remove this protection.
• Below is the explanation for how the script protect KMS38.
• In the KMS activation method, Windows first checks the KMS IP registered as a specific KMS, and if that is not defined, then it checks the Global KMS IP. Another fact is that if Localhost (IP range 127.0.0.0/8) is defined as the KMS IP in Windows 8 and later OS, then Windows will not accept it as a valid KMS IP. This script simply utilizes the above facts to protect the KMS38 activation from being overwritten by any alternative ‘normal’ 180-Day KMS Activation, and at the same time, that KMS activator can be used for Office activation.
• Script steps-
  • Set the Windows edition-specific KMS IP to Localhost (127.0.0.2)
  • Protect the below Registry from edit and delete
  • Done.

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\55c92734-d682-4d71-983e-d6ec3f16059f\XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX\