Microsoft has made VBScript an optional Windows feature. On Windows 11 it plans to switch it off by default next and remove it later; for servers, its Windows Server documentation says Windows Server 2028, now in preview, removes VBScript. Nothing breaks yet on released versions of Windows, but everything that loads vbscript.dll is now living on borrowed time, and classic ASP is the biggest of those. Here is what Microsoft has actually said, how to test, and where to move.
| Phase | What happens |
|---|---|
| 1, since Windows 11 24H2 and Windows Server 2025 | VBScript is a feature on demand, still installed and enabled by default. |
| 2, on Windows 11: Microsoft said around 2027; later wording: 2026 or 2027 | The feature is disabled by default. It can still be turned back on manually. Microsoft's Windows Server documentation doesn't list this step for servers. |
| 3, Windows Server 2028 (now in preview) for servers; no date yet for Windows 11 | VBScript is retired and removed from future Windows releases. Microsoft's Windows Server documentation lists it as removed in Windows Server 2028. |
Microsoft's advice is to move to PowerShell or JavaScript.
vbscript.dll. Microsoft's detection post names IIS running VBScript for classic ASP among the uses administrators should find before the default changes..asp pages and the ASP role service installed.cscript.exe or wscript.exe, and .vbs files in Group Policy scripts and on file shares.CreateObject("VBScript.RegExp").This test needs Windows 11 24H2 or later, or Windows Server 2025, where VBScript is a removable feature on demand; older Windows versions have no VBScript feature to remove. On such a test machine, remove the feature and see what breaks:
Get-WindowsCapability -Online | Where-Object Name -like 'VBSCRIPT*'
Remove-WindowsCapability -Online -Name <the name shown above>
Run your sites, scheduled jobs, installers and macros against that machine. Whatever fails is your migration list.
| What you have | Where it goes |
|---|---|
| Classic ASP site | ASP.NET Core on .NET 10. Put a reverse proxy (for example YARP) in front, move pages section by section and route each one to the new app as it's done. |
.vbs admin and batch scripts | PowerShell |
| VBScript custom actions in installers | Compiled custom actions (for example C# with WiX) or PowerShell run by the installer |
VBA using VBScript.RegExp | Check whether your Office version has a native replacement; otherwise move the logic out of the macro |