VBScript will be off by default in Windows around 2027: find .vbs scripts, installer actions and VBA references now

Microsoft’s VBScript deprecation plan makes VBScript a feature on demand that is preinstalled and on by default in Windows 11 version 24H2, turns it off by default around 2027, and later removes it from Windows. Windows Server 2025 also preinstalls VBScript as a feature on demand before its removal in a later release.

A controlled technology lifecycle progressing from assessment to approved production.
DSE visual intelligenceManaged IT operationsGuide · 2 min read
Executive summary

What you need to know

Microsoft’s VBScript deprecation plan makes VBScript a feature on demand that is preinstalled and on by default in Windows 11 version 24H2, turns it off by default around 2027, and later removes it from Windows. Windows Server 2025 also preinstalls VBScript as a feature on demand before its removal in a later release.

Potentially affected

Organizations with logon scripts, scheduled tasks, installers, legacy web pages or Office macros that use VBScript, and the IT staff who maintain them.

DSE recommendation

DSE recommends inventorying VBScript use now, before the 2027 default change, and moving it to PowerShell.

Microsoft’s VBScript deprecation plan makes VBScript a feature on demand that is preinstalled and on by default in Windows 11 version 24H2, turns it off by default around 2027, and later removes it from Windows. Windows Server 2025 also preinstalls VBScript as a feature on demand before its removal in a later release.

Source facts

Microsoft’s Windows IT Pro post VBScript deprecation: Timelines and next steps describes three phases: VBScript features on demand preinstalled and on by default in Windows 11, version 24H2; around 2027, the features no longer enabled by default; and finally removal from future Windows versions, when the VBScript DLLs are removed and projects that rely on it stop functioning. Microsoft’s deprecated features list says VBScript will be a feature on demand before its removal, and the Windows Server list says it is preinstalled as a feature on demand in Windows Server 2025.

The post says VBA solutions that call .vbs files or reference VBScript, such as its regular expression library, keep working in phase 1 but will be affected by later phases, and that VBScript custom actions in installer packages may stop working after deprecation. It recommends migrating automation and installer actions to PowerShell and web pages to JavaScript, and explains how to turn the feature back on under Settings, System, Optional features if VBScript is still needed after phase 2.

Applicability

Use this for Windows 11, Windows Server 2025 and later releases. The same scripts will need attention on older machines when they are replaced, so include them in the inventory.

DSE recommendation

DSE recommends inventorying VBScript use now, before the 2027 default change, and moving it to PowerShell. Search logon scripts, scheduled tasks, Group Policy, installer packages and Office macros for .vbs files and VBScript references, test critical tasks on a machine with the feature turned off, and track remaining exceptions with an owner and a date.

Verification

Search script shares and endpoint telemetry for wscript.exe and cscript.exe launches, and confirm each remaining VBScript use has a migration date.

Official references

Microsoft Windows IT Pro Blog — VBScript deprecation: Timelines and next steps. Microsoft Learn — Deprecated features in the Windows client. Microsoft Learn — Features removed or no longer developed starting with Windows Server. Reviewed October 19, 2026.

Primary reference

Review the official source

Microsoft Windows IT Pro Blog — VBScript deprecation: Timelines and next steps · Verified October 19, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE