Microsoft is slowly but surely preparing the end of slmgr.vbsa tool well known to administrators that allows you to activate Windows, install a product key or even check the status of a license from the command line.
And for good reason, slmgr.vbs is based on VBScript, which Microsoft plans to phase out from Windows. Once removed, the tool will simply no longer be able to function.
Therefore, Microsoft recommends starting to replace uses of slmgr.vbs for the new PowerShell OSLicense module and has just released several examples to ease the transition.
slmgr.vbs will give way to PowerShell
Obviously, all the functions of slmgr.vbs They are not going to disappear with him. Microsoft has planned for this with a new PowerShell module called OSLicense, which allows you to manage Windows activation and licensing without using VBScript.
And just to make the transition a little easier, Microsoft gives several examples to replace the most common commands.
To activate Windows, the command:
slmgr.vbs /atois replaced by:
Invoke-OSLicense -ActivateOnlineTo install a product key, go from:
slmgr.vbs /ipk has :
Invoke-OSLicense -InstallProductKey And to display detailed information about the Windows license, the command:
slmgr.vbs /dlvleave room for:
Get-OSLicenseInfoWell, in short, it’s not much more complicated. Above all, it will be necessary to lose the habits acquired with slmgr.vbs and keep these few new commands.
And there are many more. OSLicense It can be used in particular for KMS, activation via Active Directory or even Windows licenses via subscription. Microsoft has grouped all the commands and their parameters into module documentation if you want to go a little further.
However, don’t be surprised if the commands still don’t work on your PC. OSLicense It is not available in all versions of Windows. In Windows 11, you must at least have the optional KB5120998 August 27, 2026 update or a newer update installed.
For Windows Server, you’ll have to wait a little longer. Microsoft plans to integrate the module in the next major version of the system, although it is already possible to test it with Windows Server vNext Preview Build 29651 or a newer version.
slmgr.vbs will not disappear immediately
Rest assured, Microsoft will not remove slmgr.vbs overnight. Its demise will follow that of VBScript, which occurs in several stages.
At this time, VBScript is still available on Windows as an on-demand feature and remains enabled by default in affected versions. In a second phase, scheduled for around 2027, Microsoft plans to deactivate it by default. Then it will always be possible to activate it manually to continue using the tools that depend on it.
Only in the final step will VBScript be completely removed from future versions of Windows. Once VBScript is permanently removed, slmgr.vbs therefore it will no longer be able to function.
Microsoft still does not give a precise date when slmgr.vbs will stop working permanently. The company simply advises administrators to take advantage of this transition period to identify scripts that still depend on it and test them with OSLicense and gradually migrate them to PowerShell.
For individuals, nothing changes
Obviously, if you have never used slmgr.vbsyou have absolutely nothing to do. This change mainly affects system administrators and companies that still use this tool in their scripts to automate Windows activation on multiple machines.
Classic Windows activation will continue to work as it does today. You can always enter your product key or check the activation status from Windows Settings.
