Microsoft Is Replacing slmgr.vbs With PowerShell OSLicense for Windows Activation

For years, slmgr.vbs has been one of the most familiar command-line tools for Windows administrators. It can activate Windows, install product keys, check licensing information, and manage several types of Windows activation from a Command Prompt or script.

That is about to change.

Microsoft is gradually moving away from VBScript, the scripting technology that slmgr.vbs depends on. As VBScript is eventually removed from Windows, slmgr.vbs will no longer be able to run.

Instead of leaving administrators without an alternative, Microsoft has introduced a new PowerShell module called OSLicense. The module provides modern PowerShell commands for managing Windows activation and licensing, including several replacements for the most commonly used slmgr.vbs commands.

Microsoft is now encouraging administrators to start migrating their existing scripts and workflows before VBScript is eventually retired.

Microsoft Is Phasing Out slmgr.vbs

The important thing to understand is that Microsoft isn’t directly killing slmgr.vbs overnight.

The problem is its dependency on VBScript.

slmgr.vbs is essentially a VBScript-based licensing management tool. Once Windows no longer includes the VBScript engine, the script will no longer have the environment it needs to execute.

Microsoft is therefore introducing OSLicense as the long-term replacement.

The new PowerShell module is designed to handle many of the same Windows activation and licensing tasks while providing administrators with a more modern command-line interface.

For organizations that rely heavily on automated Windows deployment and activation, this transition is worth preparing for now.

OSLicense Replaces the Most Common slmgr.vbs Commands

The good news is that switching from slmgr.vbs to OSLicense shouldn’t require administrators to completely rethink how they manage Windows licenses.

Microsoft has already published equivalent commands for many of the most frequently used slmgr.vbs operations.

Activate Windows Online

The traditional command for activating Windows online is:

slmgr.vbs /ato

With OSLicense, Microsoft provides:

Invoke-OSLicense -ActivateOnline

The new command performs the online activation operation through PowerShell rather than relying on the VBScript-based licensing tool.

Install a Windows Product Key

Administrators currently use the following command to install a product key:

slmgr.vbs /ipk <product-key>

The PowerShell equivalent is:

Invoke-OSLicense -InstallProductKey <product-key>

This should make it relatively straightforward to update existing deployment scripts that install Windows product keys automatically.

Display Detailed License Information

To display detailed information about the current Windows license, slmgr.vbs uses:

slmgr.vbs /dlv

With OSLicense, Microsoft provides:

Get-OSLicenseInfo

This PowerShell command is designed to provide information about the operating system’s licensing and activation state without depending on slmgr.vbs.

OSLicense Does More Than Basic Windows Activation

Although replacing a few familiar slmgr.vbs commands is probably the most obvious use case, Microsoft’s new OSLicense module isn’t limited to basic activation.

The module is also intended to support more advanced Windows licensing scenarios, including:

• KMS activation
• Active Directory-based activation
• Windows subscription activation
• Product key management
• Online activation
• Windows license information
• Enterprise licensing workflows

That means OSLicense isn’t simply a temporary workaround for administrators who still use slmgr.vbs.

Microsoft appears to be positioning it as the modern PowerShell interface for Windows licensing and activation.

For companies managing hundreds or thousands of Windows PCs, that distinction is important because licensing commands are often embedded in deployment systems, PowerShell scripts, provisioning processes, and automated maintenance tools.

When Will OSLicense Be Available?

If you try one of the new commands on your Windows PC and nothing happens, don’t necessarily assume you’ve entered the command incorrectly.

OSLicense isn’t available on every Windows version yet.

For Windows 11, Microsoft says the module requires at least the optional KB5120998 update released on August 27, 2026, or a newer update.

If your Windows 11 installation doesn’t have that update or a later one, the OSLicense commands may not be available.

What About Windows Server?

Windows Server is following a slightly different timeline.

Microsoft plans to include OSLicense in the next major version of Windows Server.

Administrators who want to test the new licensing module before the final release can already use it with Windows Server vNext Preview build 29651 or later.

This gives enterprise administrators an opportunity to test their existing activation scripts and identify compatibility problems before the technology becomes a requirement.

VBScript Isn’t Going Away Immediately

Despite Microsoft’s plans, there is no need to panic if you still depend on slmgr.vbs.

slmgr.vbs will continue to work for some time.

That’s because Microsoft’s removal of VBScript is happening gradually rather than through a single Windows update.

The transition is expected to happen in several stages.

Stage 1: VBScript Remains Available

For now, VBScript remains available in Windows as an optional feature and is still enabled by default on the affected versions.

That means existing VBScript-based tools, including slmgr.vbs, can continue to operate.

Stage 2: VBScript Will Be Disabled by Default

Microsoft plans to move to the next phase around 2027.

At that point, VBScript is expected to be disabled by default.

Administrators will still be able to manually enable the feature when necessary, allowing older scripts and applications that depend on VBScript to continue functioning.

However, this will be an important warning sign for organizations that still rely heavily on legacy VBScript automation.

Stage 3: VBScript Will Be Removed

The final stage is the complete removal of VBScript from future versions of Windows.

Once that happens, software and scripts that require the VBScript engine will no longer work.

That includes slmgr.vbs.

Microsoft has not provided a specific final date for when slmgr.vbs will stop working permanently. Instead, the company is encouraging administrators to use the transition period to identify scripts and automation workflows that still depend on the legacy tool.

System Administrators Should Start Migrating Now

For home users, this change is unlikely to make any noticeable difference.

For IT departments and system administrators, however, it is worth taking seriously.

Many organizations don’t manually run slmgr.vbs. Instead, the command may be hidden inside:

• Windows deployment scripts
• PowerShell or batch files
• Configuration management tools
• Imaging workflows
• Automated activation processes
• KMS deployment scripts
• Enterprise provisioning systems
• Windows maintenance scripts

Those scripts can continue working today while silently becoming dependent on technology Microsoft intends to remove.

The safest approach is to audit existing scripts for slmgr.vbs references, determine which commands are being used, and begin testing their OSLicense equivalents.

This also gives IT teams plenty of time to update automated deployment systems rather than discovering the problem after a future Windows release disables or removes VBScript.

What Does This Mean for Regular Windows Users?

For most people, practically nothing changes.

If you’ve never opened Command Prompt to run slmgr.vbs, you don’t need to do anything.

Windows activation itself isn’t being discontinued.

You will still be able to activate Windows using a valid digital license or product key. You can also continue checking your activation status through the normal Windows Settings interface.

The change is primarily about how administrators and automated tools interact with Windows licensing from the command line.

Microsoft is replacing an aging VBScript-based management tool with a PowerShell-based solution that fits better with modern Windows administration.

slmgr.vbs vs. OSLicense: What’s Changing?

The commands may look different, but the transition should be relatively straightforward for administrators who are already comfortable with PowerShell.

The Bottom Line

slmgr.vbs isn’t disappearing tomorrow, but its long-term future is effectively sealed.

Microsoft’s broader plan to retire VBScript means the decades-old Windows licensing script will eventually become unusable. The company is therefore giving administrators a replacement in the form of the OSLicense PowerShell module.

For simple tasks such as activating Windows, installing a product key, or checking license information, the new commands are easy enough to learn. More importantly, OSLicense is designed to handle enterprise scenarios such as KMS, Active Directory activation, and Windows subscription licensing.

The best time for businesses to make the switch is before they are forced to.

If you manage Windows machines professionally, start checking your deployment and automation scripts for slmgr.vbs now. Migrating to OSLicense while VBScript is still available gives you plenty of time to test everything and avoid unexpected activation problems when Microsoft eventually removes the legacy scripting technology from Windows.