BestPaid guides · Windows · classic ASP

VBScript is being phased out of Windows. What it means for classic ASP sites, .vbs scripts and installers

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.

Sources: Microsoft's VBScript deprecation timelines (May 2024), Microsoft's detection strategies post (May 2025), Microsoft's Features removed or no longer developed in Windows Server (updated November 2026), a Microsoft Q&A answer on classic ASP and The Register's report on the later wording. Checked on November 21, 2026. This page is our own summary; follow Microsoft's documentation for every detail.

The three phases

PhaseWhat happens
1, since Windows 11 24H2 and Windows Server 2025VBScript is a feature on demand, still installed and enabled by default.
2, on Windows 11: Microsoft said around 2027; later wording: 2026 or 2027The 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 11VBScript 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.

Classic ASP

Find everything that still uses VBScript

Test without VBScript today

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.

Where to move

What you haveWhere it goes
Classic ASP siteASP.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 scriptsPowerShell
VBScript custom actions in installersCompiled custom actions (for example C# with WiX) or PowerShell run by the installer
VBA using VBScript.RegExpCheck whether your Office version has a native replacement; otherwise move the logic out of the macro
A classic ASP site nobody wants to touch? We move classic ASP sites to ASP.NET Core on .NET 10 page by page, with the old site running until the last page moves, and rewrite VBScript automation in PowerShell. Fixed price, starting with a $490 audit: every page, script and dependency mapped, with a quote.
See the .NET upgrade offer
Is the site on Windows Server 2016? Its extended support ends on January 12, 2027: what to do with IIS sites, .NET apps, services and scheduled tasks.