Classic ASP end of life has no date of its own. Microsoft says the use of ASP pages with IIS "is currently supported in all supported versions of IIS," and that ASP support is tied to the lifecycle of the Windows version hosting it. No Microsoft page sets a 2025 end date for Classic ASP.
The date that does deserve attention belongs to VBScript, the scripting language Microsoft itself says is commonly used with ASP. Microsoft has deprecated it and published a three-phase plan to remove it from Windows. This post sets out what Microsoft has said, what it hasn't, and how to find out whether your site keeps running.
- Classic ASP has no end-of-life date. Microsoft says ASP and IIS support are tied to the host Windows lifecycle.
- No Microsoft page sets a 2025 end date for Classic ASP, whatever the search results suggest.
- VBScript is deprecated. Around 2027 it will no longer be on by default, and a later Windows release will remove it.
- Microsoft hasn't said what that means for server-side ASP pages written in VBScript. Test on a server with VBScript removed.
Is Classic ASP still supported?
Yes, on a supported Windows version. Microsoft's support article Active Server Pages (ASP) support in Windows is short. The two sentences that matter:
"The use of ASP pages with Microsoft Internet Information Services (IIS) is currently supported in all supported versions of IIS."
"IIS is included in Windows operating systems. Therefore, both ASP and IIS support lifetimes are tied to the support lifecycle of the host operating system."
Microsoft's IIS lifecycle page agrees: IIS "is a component of the Windows operating system and follows the same lifecycle." So the Microsoft Classic ASP end of life date is your server's date.
| Where the site runs | Support ends |
|---|---|
| Windows Server 2012 R2, Extended Security Update Year 3 | 13 October 2026 (ended) |
| IIS 10 on Windows Server 2016 | 12 January 2027 |
| IIS 10 on Windows Server 2019 | 9 January 2029 |
| Windows Server 2022, which includes IIS | 14 October 2031 |
Checked 27 October 2026 against Microsoft's IIS lifecycle page, its lists of products ending in 2026 and 2029, and the Windows Server 2022 lifecycle page.
For a Classic ASP site still on Windows Server 2012 R2, Extended Security Update Year 3 ended two weeks ago. One on Windows Server 2016 has under three months left. What an unsupported server exposes you to is covered in the risks of running end-of-life software.
Is there a Classic ASP end of life date in 2025?
- People search for "classic asp end of life 2025" as if a date exists, but none of the Microsoft pages above gives Classic ASP an end date in 2025 or any other year. The ASP support article still ties ASP to the host operating system.
Two real changes from around then probably feed the belief, in our view. VBScript became an optional "feature on demand" in Windows 11, version 24H2. And Windows Server 2025 ships VBScript the same way, preinstalled. Neither is an end date for Classic ASP.
Is VBScript deprecated?
Yes. Microsoft's list of deprecated Windows features records the deprecation as announced in October 2023: "In future releases of Windows, VBScript will be available as a feature on demand before its removal from the operating system."
VBScript deprecation: timelines and next steps
Microsoft's Windows IT Pro post VBScript deprecation: Timelines and next steps, published on 22 May 2024, sets out three phases.
| Phase | When | What Microsoft says happens |
|---|---|---|
| Phase 1 | Windows 11, version 24H2 | VBScript features on demand are "pre-installed" and "on by default" |
| Phase 2 | "Around 2027" | VBScript will "no longer be enabled by default"; you'd have to turn it on |
| Phase 3 | No date given | VBScript removed from future Windows versions: "all the dynamic link libraries (.dll files) of VBScript will be removed" |
Checked 27 October 2026 against Microsoft's VBScript deprecation post.
So the only VBScript deprecation date is approximate, and Phase 3 has none. For servers, Microsoft's Windows Server removed and deprecated features list says "VBScript is available as an FOD and preinstalled in Windows Server 2025, before its removal from the operating system in a later release." The same page says "Components aren't removed from generally available supported versions that are within their product lifecycle." Taken together: a supported Windows Server release keeps VBScript, and the removal comes in a later release.
What VBScript deprecation means for Classic ASP pages
The honest answer: Microsoft's pages don't say. The VBScript post mentions ASP once, describing VBScript as "commonly used in conjunction with Microsoft technologies like Active Server Pages (ASP) and Windows Script Host (WSH)." Its migration advice covers automation scripts, installer custom actions and VBScript in browser pages. It says nothing specific about server-side ASP pages, and the ASP support article doesn't mention VBScript at all.
What the post does say is general: in Phase 3, "projects that rely on VBScript will stop functioning." Until Microsoft says otherwise for ASP, plan as if that includes your site, and test instead of guessing:
- Build a test server on the Windows version you'd move to, and deploy the Classic ASP site.
- Remove the VBScript feature on demand from that server, then run the site's main journeys.
- Record every page that fails, and anything else that breaks, such as scheduled .vbs jobs.
- Add VBScript back and run the same journeys, so you know the failures came from VBScript.
Developer machines on Windows 11 may meet Phase 2 before your servers do.
Your options for a Classic ASP site
| Option | What changes | When it fits | Main risk |
|---|---|---|---|
| Move to a supported Windows Server | The server; the code stays | Stable site, few changes | Phase 3 removal later, date unknown |
| Rewrite on ASP.NET Core | New application on modern .NET | The site still changes, or must outlive VBScript | Rules buried in include files and inline script get missed |
| Replace with a package | The process moves to a product | A standard process a product already handles | Integrations and reports built on the old database |
Moving Classic ASP to ASP.NET Web Forms isn't a sensible target now. Web Forms can't move to modern .NET either, as we explain in Web Forms end of life.
Classic ASP sites are often paired with other aging pieces, such as a VB6 COM component called from the pages. Microsoft's support for the VB6 runtime has its own rules, covered in VB6 end of support. These combinations turn up on almost any list of legacy system examples.
Know what's in the site before you choose
Before you pick a path, find out what the site contains and what it depends on. The 30-day assessment is fixed in scope, at a price agreed before we start. Over 30 days we read the ASP pages, include files, COM components and database code, map how the site fits together with its databases, scheduled jobs and the systems around it, find the hidden architectural debt, and flag the security and compliance gaps, such as servers past their support date or SQL built straight from request values.
The report says in plain language what is broken and what it would take to fix it, including which pages depend on VBScript and which could move first. Your own team can act on it, or we can do the rewrite as a separate project with its own scope and price. Either way, the report stands on its own.
Book a scoping call to talk through your Classic ASP site.