Microsoft accelerates VBScript deprecation in Windows 11 24H2 and 25H2
Microsoft regularly retires older features across its apps to improve security, performance, and maintainability — a move the company has previously explained is ultimately beneficial for users.
In recent updates, Microsoft announced the deprecation of several components, including the Bing Search APIs and a feature in Microsoft Edge , favoring more modern and secure alternatives. The company also revealed changes to Windows hardware drivers , with plans to phase out Windows Device Metadata and the Windows Metadata and Internet Services (WMIS) . Additionally, one of Excel’s legacy features is being discontinued due to high maintenance costs and low usage.
VBScript has also been on the chopping block for some time. Microsoft first signaled its intent to remove it in May 2023 , and officially deprecated it by October of the same year .
It’s important to note that deprecation doesn’t mean immediate removal. Instead, it marks the start of a transition period , giving organizations time to adapt and migrate away from affected features before they’re fully retired.
In May 2024, Microsoft laid out a three-phase plan for deprecating VBScript , with the first phase currently active. At this stage, VBScript remains available by default as a Feature on Demand (FOD) in Windows 11 version 24H2.
Originally scheduled for removal around 2027, recent updates suggest that Microsoft may disable VBScript sooner than expected , possibly in Windows 11 24H2 or 25H2 .
The company has urged enterprises to act now:
“Before VBScript is disabled by default on these and future OS versions, it’s critical that you identify where and how vbscript.dll is still being used within your enterprise environment.”
To help organizations transition smoothly, Microsoft has shared tools and methods to detect VBScript usage, including:
- Using SysMon to track VBScript DLLs.
- Reviewing Group Policy and PowerShell scripts tied to logon/logoff, startup/shutdown, and scheduled tasks.
- Scanning for
.vbsfiles using a provided PowerShell script. - Detecting embedded VBScript in MSI installers.
Once detected, Microsoft recommends proactively disabling VBScript using the following command:
This can be deployed across enterprise systems via Intune , GPO Startup Scripts , or Configuration Manager . After removal, any attempt to use VBScript will either fail silently or return an error.
You can read more about this update on Microsoft’s official Tech Community blog .
