How to Activate Windows with PowerShell: Complete Guide in 2026

Windows activation can feel like a roadblock when you’re setting up a new computer or reinstalling your operating system. PowerShell offers a straightforward command-line method to activate Windows without clicking through multiple settings menus. This guide shows you exactly how to do it.

Quick answer: You can activate Windows using PowerShell by opening PowerShell as administrator and running specific commands with your product key. The basic command is slmgr.vbs /ipk YOUR-PRODUCT-KEY followed by slmgr.vbs /ato to complete activation.

Let me walk you through everything you need to know.

Understanding Windows Activation Through PowerShell

PowerShell is Windows’ powerful command-line shell that lets you manage your system through text commands. When you activate Windows through PowerShell, you’re using the Software Licensing Management Tool (slmgr.vbs), a built-in script that handles activation tasks.

This method works for:

• Windows 11 (all editions)
• Windows 10 (Home, Pro, Enterprise, Education)
• Windows Server versions

You need a valid product key. PowerShell simply provides a faster route to enter it and complete activation.

Before You Start: What You Need

Valid Product Key

Your 25-character Windows product key is essential. You can find it:

• On a sticker attached to your computer (for pre-installed Windows)
• In your email confirmation (for digital purchases)
• On the Windows packaging (for retail versions)
• Through your Microsoft account (for digital licenses)

Administrator Access

PowerShell commands for activation require administrator privileges. You must run PowerShell as an admin, or the commands will fail.

Internet Connection

Windows contacts Microsoft’s activation servers to verify your key. A stable internet connection is necessary.

Step-by-Step: Activating Windows with PowerShell

Method 1: Basic Activation with Product Key

This is the standard process most people will use.

Step 1: Open PowerShell as Administrator

Press Windows + X on your keyboard. Select “Windows PowerShell (Admin)” or “Terminal (Admin)” from the menu. On Windows 11, you might see “Windows Terminal (Admin)” instead.

If you see a User Account Control prompt, click “Yes” to proceed.

Step 2: Install Your Product Key

Type this command, replacing XXXXX-XXXXX-XXXXX-XXXXX-XXXXX with your actual product key:

slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Press Enter. A dialog box will appear confirming the key was installed successfully.

Step 3: Activate Windows

Now run the activation command:

slmgr.vbs /ato

Press Enter. Windows will contact the activation servers and activate your copy. You’ll see a confirmation message when it’s done.

Step 4: Verify Activation

Check your activation status with:

slmgr.vbs /xpr

This displays whether Windows is permanently activated.

Method 2: Using KMS Activation (For Volume Licenses)

Organizations with volume licensing use Key Management Service (KMS) servers. This method applies to enterprise environments.

Step 1: Set the KMS Server

Replace kms.server.address with your organization’s KMS server:

slmgr.vbs /skms kms.server.address

Step 2: Install the KMS Client Key

Your IT department provides this key:

slmgr.vbs /ipk YOUR-KMS-KEY

Step 3: Activate Against KMS Server

slmgr.vbs /ato

The system connects to your KMS server for activation.

Common PowerShell Activation Commands Explained

Here’s a reference table of useful commands:

Command	Purpose	When to Use
slmgr.vbs /ipk	Install product key	Entering a new key
slmgr.vbs /ato	Activate Windows	After installing key
slmgr.vbs /dli	Display license info	Check current status
slmgr.vbs /xpr	Check activation expiration	Verify permanent activation
slmgr.vbs /upk	Uninstall product key	Removing old key
slmgr.vbs /cpky	Clear product key from registry	Security/privacy purposes
slmgr.vbs /rearm	Reset activation timer	Troubleshooting (limited uses)

Troubleshooting Activation Issues

Error: Product Key Invalid

Problem: You see “Error: 0xC004F050” or similar.

Solutions:

• Double-check your product key for typos
• Verify you’re using the correct key for your Windows edition
• Confirm the key hasn’t been used on too many devices

Error: Can’t Connect to Activation Server

Problem: “Error: 0x8007232B” appears.

Solutions:

• Check your internet connection
• Temporarily disable your firewall and try again
• Ensure your network allows connections to Microsoft servers
• Try activating by phone as an alternative (use slui.exe 4)

Error: Access Denied

Problem: Commands fail with permission errors.

Solutions:

• Restart PowerShell as administrator
• Check if your user account has admin rights
• Disable any third-party security software temporarily

Already Activated But Shows Not Activated

Problem: Windows was activated but now shows as unactivated.

Solutions:

Run these commands in order:

slmgr.vbs /upk
slmgr.vbs /cpky
slmgr.vbs /ipk YOUR-PRODUCT-KEY
slmgr.vbs /ato

This removes the old key and reinstalls it fresh.

Activating Different Windows Editions

Windows 11 Home vs Pro

The process is identical, but you need the correct key for your edition. You cannot activate Windows 11 Pro with a Home key.

To check your edition, run:

Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion

Upgrading from Home to Pro

If you want to upgrade editions:

Step 1: Purchase a Windows Pro key

Step 2: Install the Pro key:

slmgr.vbs /ipk YOUR-PRO-KEY

Step 3: Activate:

slmgr.vbs /ato

Windows will upgrade to Pro automatically after activation completes.

Phone Activation as a Backup Method

Sometimes online activation fails due to network issues or server problems. Phone activation provides an alternative.

Step 1: Open the Phone Activation Wizard

slui.exe 4

Step 2: Select your country

Step 3: Call the number displayed

Step 4: Follow the automated system

You’ll read a long installation ID to the system. Microsoft provides a confirmation ID in return.

Step 5: Enter the confirmation ID in the wizard

Your Windows will activate immediately.

Checking Activation Status Through PowerShell

Beyond the basic commands, you can get detailed information.

View Complete License Information

slmgr.vbs /dlv

This shows:

• License status
• Remaining rearm count
• Grace period
• Partial product key

Quick Status Check

Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | Where-Object { $_.PartialProductKey } | Select-Object Name, Description, LicenseStatus

This PowerShell command displays your license status in a clean format. LicenseStatus “1” means activated.

Automating Activation for Multiple Computers

IT professionals managing many computers can automate activation.

Creating a PowerShell Script

Create a file named activate.ps1:

# Set product key
$productKey = "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

# Install key
Start-Process -FilePath "cscript.exe" -ArgumentList "//B //Nologo $env:windir\system32\slmgr.vbs /ipk $productKey" -Wait

# Activate
Start-Process -FilePath "cscript.exe" -ArgumentList "//B //Nologo $env:windir\system32\slmgr.vbs /ato" -Wait

# Check status
slmgr.vbs /xpr

Run this script on each computer to activate Windows automatically.

Using Group Policy for KMS

Organizations can configure KMS activation through Group Policy:

• Computer Configuration > Administrative Templates > Windows Components > Software Protection Platform
• Set “Use KMS for activation” and specify your KMS server

Digital Licenses and Hardware Changes

Windows 10 and 11 often use digital licenses tied to your Microsoft account rather than product keys.

Linking Your License to Microsoft Account

Step 1: Open Settings > Accounts > Your info

Step 2: Sign in with your Microsoft account

Step 3: Go to Settings > Update & Security > Activation

Your digital license links to your account automatically.

Reactivating After Hardware Changes

Major hardware changes (like replacing your motherboard) may deactivate Windows.

Solution:

Run the activation troubleshooter:

slui.exe 0x2a 0xC004F211

Select “I changed hardware on this device recently” and sign in with your Microsoft account. Microsoft’s Learn documentation provides additional guidance on Windows activation troubleshooting.

Security Considerations

Protecting Your Product Key

Never share your product key publicly. After activation, you can remove it from the registry:

slmgr.vbs /cpky

This prevents key extraction tools from reading it.

Avoiding Fake Activation Tools

Only use legitimate Microsoft methods. Third-party “activators” often contain malware. PowerShell with official slmgr.vbs commands is safe and Microsoft-approved.

Verifying Genuine Windows

Check if your Windows is genuine:

slmgr.vbs /dli

Look for “License Status: Licensed” in the output.

Activation in Virtual Machines

Virtual machines need activation just like physical computers.

Hyper-V Automatic Activation

Windows Server hosts can automatically activate Windows VMs using Automatic Virtual Machine Activation (AVMA).

Host requirements:

• Windows Server 2019 or later (Datacenter edition)
• Hyper-V role enabled

Install the AVMA key on the VM:

slmgr.vbs /ipk AVMA-KEY

AVMA keys are specific to each Windows edition. Microsoft provides the complete list of AVMA keys.

Other Virtualization Platforms

VMware, VirtualBox, and other platforms require standard activation with your regular product key. Each VM counts as one activation.

Understanding Activation Limits

Most retail Windows keys activate on one computer at a time. If you reinstall or change computers frequently, you might hit activation limits.

How Many Times Can You Activate?

Microsoft doesn’t publish a specific number, but the system tracks hardware changes. Small changes are fine. Complete hardware replacements may require contacting Microsoft support.

Removing Old Activations

You cannot manually deactivate old installations, but uninstalling the key before reinstalling helps:

slmgr.vbs /upk

Run this on the old computer before moving your key to a new one.

Enterprise Deployment Scenarios

Using MAK Keys

Multiple Activation Keys (MAK) work for organizations without KMS infrastructure.

Step 1: Install MAK key:

slmgr.vbs /ipk MAK-KEY

Step 2: Activate:

slmgr.vbs /ato

Each activation counts against your MAK pool. Check remaining activations through the Volume Licensing Service Center.

Active Directory-Based Activation

Windows 8 and later support activation through Active Directory.

Requirements:

• Active Directory forest with Windows Server 2012 or later
• Generic Volume License Key (GVLK) on client computers

Clients activate automatically when joined to the domain. No manual PowerShell commands needed.

Alternative Activation Methods

While PowerShell is efficient, other methods exist.

GUI Method

Settings > Update & Security > Activation > Change product key

This opens a simple dialog for key entry. It’s slower but more visual.

Command Prompt

All slmgr.vbs commands work in Command Prompt too:

cscript //B //Nologo %windir%\system32\slmgr.vbs /ipk YOUR-KEY

The syntax is identical. PowerShell is preferred for its additional capabilities.

Windows Activation Troubleshooter

Built into Windows 10 and 11, this tool can fix common activation problems without commands.

Access it: Settings > Update & Security > Activation > Troubleshoot

Monitoring Activation Status on Networks

Network administrators need to track activation across many computers.

Using PowerShell Remoting

Query remote computers:

Invoke-Command -ComputerName Computer1, Computer2, Computer3 -ScriptBlock {
    slmgr.vbs /dli
}

This returns activation status for multiple machines.

Creating an Activation Report

Generate a CSV report:

$computers = Get-ADComputer -Filter * | Select-Object -ExpandProperty Name

$results = foreach ($computer in $computers) {
    $status = Invoke-Command -ComputerName $computer -ScriptBlock {
        $license = Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | Where-Object { $_.PartialProductKey }
        [PSCustomObject]@{
            Computer = $env:COMPUTERNAME
            Status = $license.LicenseStatus
            Key = $license.PartialProductKey
        }
    } -ErrorAction SilentlyContinue
    $status
}

$results | Export-Csv -Path "C:\Reports\activation-status.csv" -NoTypeInformation

This scans all domain computers and creates a spreadsheet of activation states.

Summary

Activating Windows through PowerShell is straightforward once you understand the basic commands. The slmgr.vbs script handles everything from installing product keys to checking activation status.

Key takeaways:

• Always run PowerShell as administrator
• Use slmgr.vbs /ipk to install your key
• Use slmgr.vbs /ato to activate
• Verify with slmgr.vbs /xpr
• Keep your product key secure
• Digital licenses offer the most flexibility

PowerShell activation works reliably for home users, IT professionals, and enterprise environments. It’s faster than clicking through settings menus and essential for automation.

Frequently Asked Questions

Can I activate Windows without a product key using PowerShell?

No legitimate method exists to activate Windows without a valid product key or digital license. PowerShell commands require a genuine key to communicate with Microsoft’s activation servers. Any tool claiming to activate without a key violates Microsoft’s terms of service and likely contains malware.

Why does my activation fail with error 0xC004F074?

This error means the Key Management Service (KMS) server is unavailable. It typically occurs in corporate environments when the KMS server is offline or unreachable. Contact your IT department to verify the KMS server status. For home users, this error indicates you’re trying to use a volume license key instead of a retail or OEM key.

How do I switch from one product key to another?

First uninstall the current key with slmgr.vbs /upk, then install your new key with slmgr.vbs /ipk NEW-KEY, and finally activate using slmgr.vbs /ato. This process works when upgrading from Windows Home to Pro or replacing an old key with a new one.

What’s the difference between /ato and /ato <Activation ID>?

The basic slmgr.vbs /ato command activates all Windows editions on your computer. Adding an Activation ID like slmgr.vbs /ato 55c92734-d682-4d71-983e-d6ec3f16059f targets a specific Windows edition. The Activation ID approach is useful when multiple Windows editions are installed simultaneously, which is rare for most users.

Can I transfer my Windows license to a new computer using PowerShell?

Retail licenses can transfer to new computers, but OEM licenses (pre-installed on branded PCs) cannot. To transfer a retail license, run slmgr.vbs /upk on the old computer to uninstall the key. Install Windows on the new computer and activate with your existing key using the standard PowerShell commands. If activation fails, use the phone activation method and explain you’re transferring to new hardware.