Scriptocalypse: Microsoft announced the deprecation of the VBScript environment a few years ago, asking companies and power users to switch to modern scripting systems. Now, the company is warning organizations that depend on VBScript that Windows activation might even become impossible after the language is gone.
Microsoft is asking organizations that rely on the Slmgr.vbs tool to switch to PowerShell, as the old script will soon stop working along with the rest of the VBScript language. Companies that use the script to manage Windows activation should act soon, as Microsoft is likely to accelerate VBScript deprecation in future Windows upgrades.
As explained in Microsoft's own documentation, Slmgr.vbs is a Visual Basic Script included in Windows to manage OS activation from the command line. The script can install and change product keys, activate Windows, check the current activation or licensing status, and much more. The tool is specifically designed to provide enterprise organizations with a flexible way to manage multiple OS activations, which has nothing to do with KMS servers or other "unofficial" methods designed to achieve the same results without paying Microsoft a dime.
As the company first announced in 2023, VBScript will soon disappear from Windows after being part of the operating system's convoluted lineage for almost 30 years. Modeled after the Visual Basic programming language, VBScript was designed as a powerful automation technology for programmers and users looking to exert greater control over the Windows operating environment.
According to Microsoft's latest timeline for VBScript deprecation, the technology is now available as a Feature on Demand (FOD) on Windows and is enabled by default. At a later stage, VBScript's FOD will no longer be enabled by default, and users will need to manually install the feature if they need it.
Finally, a future Windows release will completely remove VBScript. At that point, Slmgr.vbs and other automation solutions will stop working altogether.
Microsoft said that Slmgr.vbs can be easily replaced with PowerShell, where the OSLicense module provides the automation features currently available through VBScript. OSLicense requires Windows PowerShell 5.1 and can be used to manage activation information, invoke new licensing instances, and more.
One potential issue with adopting the OSLicense module is the version of Windows used by organizations. The PowerShell component is available in client versions of Windows 11 after installing the August 2026 Preview update (KB5120998) or later. Meanwhile, Windows Server will provide support for the new module with the next major release of the enterprise-focused operating system.
Either way, Redmond said organizations should start checking their scripts, command-line tools, and group policies right now. Companies using Slmgr.vbs and other VBScript-based "dependencies" are advised to thoroughly check their IT automation procedures so they can ease the pain that comes with changing decades-old conventions.
Microsoft warns that killing VBScript could break Windows activation for businesses
