Microsoft could deactivate VBScript with Windows 11 25H2 prematurely

Microsoft apparently accelerates the abolition of VBScript in Windows 11. Instead of planned as originally planned for 2027, the outdated scripting language could already be deactivated in versions 24h2 and 25h2 by default.

Surprising turn?

For this purpose, Microsoft has published a comprehensive guide that is intended to support companies in identifying the use of VBScript – and now indicates the deactivation that was previously planned. This outdated scripting language is currently available as “Feature on Demand” (FOD) and is still activated in Windows 11 version 24H2 by default. Microsoft is already pushing for examination in companies:

In the current leak phase of VBScript, it is available as a feature on demand (FOD) and in Windows 11, version 24h2, activated by default. Before VBScript is deactivated by default in these and future operating system versions, it is important that you find out where and how VBScript.dll is still used in your corporate environment. Microsoft Support

Early end of support

The abolition of VBScript was first announced in May 2023 and officially declared outdated in October of the same year. It was originally planned to deactivate the function until 2027.

VBScript: Relic from the 90s

Microsoft has now announced that the Deactivation could possibly be done much earlier – Already with Windows 11 version 24H2 or at the latest with version 25h2, in response to growing security concerns in connection with the use of this scripting language. VBScript (Visual Basic Scripting Edition) was introduced by Microsoft in 1996 and was used primarily in the Windows system administration.

The scripting language enabled the automation of tasks and was often used for registration scripts, system maintenance and simple web development. However, the rise of modern alternatives such as PowerShell in 2006 heralded the slow decline of VBScript. PowerShell offers extended functions, improved security and closer integration into the Windows ecosystem.

Strategies for recognizing VBScript

Microsoft recommends four scalable methods for recognizing VBScript in corporate environments:

• System Monitor (Sysmon) – To monitor VBScript use
• Review of VBScript dependencies
• System-wide search for .VBS files
• Analysis of custom MSI packages

After identifying dependencies, companies should proactively deactivate VBScript with the DISM command to block the use.

Recommended alternatives for companies

Companies that are still dependent on VBScript are recommended to switch to PowerShell or other modern scripting languages. PowerShell not only brings with it improved security functions, but also supports extensively modern Windows functions and cloud services. The abolition of VBScript is part of a comprehensive strategy by Microsoft to remedy outdated technologies.