To help anyone stumbling across this article -
Ultimately, MS are saying that VBScript is going to be removed from both Windows 11 and Windows Server. If you want to know the impact on your VBScript/Classic ASP applications, this is my summary based on all the responses above:
- If you have web applications that use client-side VBScript then when VBScript is completely removed (date unknown) from Windows 11, this code won't run and your apps will break. From 2025, it will be enabled as a FOD by default, so you're OK. However, from 2027, you'll need to make sure that your users have it installed on their machine as an optional feature in Windows 11 (I haven't seen anything yet on whether this can be enforced centrally e.g. via InTune).
- If you have web applications that use server-side VBScript via Classic ASP, then when VBScript is completely removed (date unknown) from Windows Server, this code won't run and your apps will break. From 2025, it will be enabled as a FOD by default, so you're OK. However, from 2027, you'll need to make sure that it is enabled as a FOD in Windows Server.
Beyond 2027, who knows? However, at some point, it will be removed completed.
If you're one of the (relatively) few people who use JScript on the server via Classic ASP, then theoretically that should still work as MS is only removing vbscript.dll. However, based on the comments above by @dx7dev, removing vbscript.dll currently breaks Classic ASP.
Naveen_Shankar please clarify if I've misunderstood anything.
Microsoft