Your application still loads. Your users still log in. Orders still go through. Everything looks normal. But behind the scenes, something important has changed: the company that built the platform your software runs on has stopped protecting it.
That is what happens when a .NET version reaches end of support. And right now, it is happening to a lot of businesses. On 10 November 2026, Microsoft ended support for both .NET 8 and .NET 9 on the same day. Next in line is .NET Framework 4.6.2, which loses support on 12 January 2027, less than two months from now.
If your business relies on a .NET application, this guide explains what end of support really means, the risks of ignoring it, and the practical options you have to keep your software secure, compliant and running smoothly.
What Does “End of Support” Mean for a .NET Version?
End of support vs. end of life
The two terms are often used interchangeably. In simple terms, end of support is the date after which Microsoft stops maintaining a version. End of life describes the same point from your side: the version is no longer a safe, maintained foundation for production software.
What stops after the deadline
Once a .NET version reaches end of support, Microsoft no longer provides:
- Security updates: newly discovered vulnerabilities are not patched.
- Bug fixes and servicing updates: reliability and performance issues stay unresolved.
- Technical support: Microsoft support will not help you troubleshoot problems on that version.
What does not stop, and why that is the danger
Your application keeps running exactly as it did the day before. Nothing breaks on the deadline. That is exactly why end of support is so easy to ignore. The risk does not show up as an outage; it builds up quietly with every new vulnerability that is discovered and never fixed.
How Microsoft’s .NET Support Lifecycle Works
To plan ahead, it helps to understand that Microsoft runs two different .NET families with two different support models.
Modern .NET: LTS and STS releases
Modern .NET (formerly .NET Core) ships a new major version every November. Even-numbered versions are Long Term Support (LTS) releases, supported for three years. Odd-numbered versions are Standard Term Support (STS) releases. In September 2025, Microsoft extended STS support from 18 to 24 months. That change is why .NET 9 ended on the same day as .NET 8, creating a “double deadline” for many development teams.
The key point: LTS means three years, not forever. Even a “long-term” version needs a planned upgrade path.
.NET Framework: tied to Windows
The classic .NET Framework works differently. Version 4.5.2 and later follows the lifecycle of the Windows operating system it is installed on, while specific older versions have been retired on fixed dates. Many long-running business systems still run on .NET Framework, which is why these dates matter so much for legacy applications.
Key .NET Support Dates You Should Know
Here is where the most common versions stand today:
| Version | Status | End of support |
|---|---|---|
| .NET Framework 4.0, 4.5, 4.5.1 | Unsupported | January 2016 |
| .NET Framework 4.5.2, 4.6, 4.6.1 | Unsupported | 26 April 2022 |
| .NET Core 3.1 | Unsupported | December 2022 |
| .NET 6 / .NET 7 | Unsupported | November 2024 / May 2024 |
| .NET 8 (LTS) / .NET 9 (STS) | Unsupported | 10 November 2026 |
| .NET Framework 4.6.2 | Ending soon | 12 January 2027 |
| .NET Framework 3.5 SP1 | Supported | 9 January 2029 |
| .NET Framework 4.7 – 4.8.1 | Supported | No date announced (follows Windows) |
| .NET 10 (LTS) | Current | November 2028 |
Not sure which .NET version your application runs on?
Many businesses don’t know until something goes wrong. Softwiz Infotech offers a free .NET version and support-status check, so you know exactly where you stand.
What Actually Happens When You Keep Running an Unsupported .NET Version
1. Security vulnerabilities go unpatched
New vulnerabilities in the .NET runtime and libraries are found all the time. On a supported version, Microsoft releases a fix on Patch Tuesday. On an unsupported version, the vulnerability is published, attackers learn about it, and your application stays exposed with no official fix coming.
2. Compliance and audit failures
Most security and data-protection standards expect software to be patched and supported. Running an end-of-support platform can create findings in audits for GDPR, PCI DSS, ISO 27001, Cyber Essentials in the UK and data-protection rules in the UAE. For businesses in finance, healthcare or e-commerce, that can put contracts and certifications at risk.
3. Third-party libraries and NuGet packages move on
Library authors and component vendors follow Microsoft’s lead. Over time, new versions of the packages your application depends on stop supporting older frameworks. You end up stuck on outdated, potentially vulnerable dependencies because the newer versions will not install.
4. Tooling, hosting and monitoring stop supporting it
Cloud platforms, monitoring tools and DevOps pipelines also drop old versions. For example, Cisco AppDynamics announced that its .NET agent would stop supporting .NET 8 and .NET 9 from 11 November 2026, in line with Microsoft. One by one, the tools around your application stop working with it.
5. Compatibility problems with newer Windows and servers
As you upgrade servers and operating systems, older frameworks may become harder to install or run. Windows Server 2012 and 2012 R2 have now passed the end of their Extended Security Updates, so many older .NET applications face both an outdated framework and an outdated server at the same time.
6. Rising maintenance costs and a shrinking talent pool
Developers prefer to work on modern technology. The longer an application stays on an old version, the harder and more expensive it becomes to find people who can maintain it, and the more each change costs.
7. Cyber insurance and customer due diligence
Insurers and enterprise customers increasingly ask about unsupported software in security questionnaires. “We’re running an end-of-support platform” is not an answer that wins renewals or new contracts.
Warning Signs Your .NET Application Is at Risk
Your application may need attention if any of these sound familiar:
- It targets .NET Framework 4.6.2 or earlier, or .NET 8 / .NET 9 or earlier.
- It relies heavily on ASP.NET Web Forms, WCF or other legacy technologies.
- It is hosted on Windows Server 2012 / 2012 R2 or older.
- It has not received framework or dependency updates in over a year.
- The original developers have left and documentation is limited.
- Simple changes take weeks because nobody wants to “touch” the code.
Your Options When Your .NET Version Reaches End of Support
The good news: you have more than one path, and not every option requires a full rewrite.
Option 1: Upgrade within .NET Framework
If your application runs on .NET Framework 4.6.2 or earlier, moving to .NET Framework 4.8 or 4.8.1 is usually the fastest, lowest-risk way to get back on a supported version. Code changes are typically minimal, making it ideal when you need to meet the January 2027 deadline.
Option 2: Migrate to modern .NET (.NET 10)
For long-term value, migrating to .NET 10, the current LTS release supported until November 2028, gives you better performance, cross-platform hosting, container and cloud readiness, and access to the modern .NET ecosystem. It takes more effort, especially for Web Forms or WCF applications, but it future-proofs your investment. If you are on .NET 8 or .NET 9, upgrading to .NET 10 is usually a straightforward step.
Option 3: Incremental modernisation
Instead of a “big bang” rewrite, you can modernise one module at a time using the strangler pattern. New features are built on modern .NET while older parts keep running until they are replaced. This spreads cost and risk over time without disrupting the business.
Option 4: Stay put with extra protection (short term only)
Some organisations add compensating controls, such as network isolation, web application firewalls and stricter monitoring, or buy third-party extended support while they plan a migration. This can buy time, but it is a bridge, not a destination.
| Option | Cost | Risk | Timeline | Long-term value |
|---|---|---|---|---|
| Upgrade to .NET Framework 4.8.x | Low | Low | Weeks | Medium |
| Migrate to .NET 10 | Medium–High | Medium | Months | High |
| Incremental modernisation | Spread over time | Low–Medium | Ongoing | High |
| Stay put + controls | Low upfront | High | Immediate | Low |
How to Plan a Safe .NET Upgrade or Migration
- Inventory your applications. List every application, the .NET version it targets and where it is hosted.
- Audit dependencies and compatibility. Check NuGet packages, third-party DLLs and legacy technologies such as WCF and Web Forms.
- Prioritise by business risk. Start with internet-facing and business-critical systems, and those closest to their deadline.
- Choose the right path for each application. Upgrade, migrate or modernise. One size rarely fits all.
- Test thoroughly and deploy in phases. Use automated tests, staging environments and a clear rollback plan.
- Set up ongoing maintenance. Regular patching and a version roadmap mean you are never caught out by the next deadline.
How Softwiz Infotech Helps Businesses with Legacy .NET Applications
Softwiz Infotech specialises in keeping legacy .NET applications secure, stable and future-ready. We work with businesses across the UK, United States, UAE, Australia and Europe to:
- Maintain and support existing .NET Framework applications.
- Audit your .NET versions and dependencies, and deliver a clear upgrade roadmap.
- Upgrade applications to supported .NET Framework versions quickly and safely.
- Migrate and modernise applications to .NET 10 without disrupting your business.
- Provide ongoing security patching and long-term support.
Book a free .NET support-status assessment
Find out which of your applications are at risk, how urgent the deadlines are and the most cost-effective path forward. Contact Softwiz Infotech today.
Frequently Asked Questions
Will my .NET application stop working after end of support?
No. Your application will keep running. However, it will no longer receive security patches, bug fixes or Microsoft support, so the risk increases over time.
Is .NET Framework 4.8 still supported?
Yes. .NET Framework 4.8 and 4.8.1 are supported and follow the lifecycle of the Windows version they are installed on. Microsoft has not announced an end-of-support date for them.
When does .NET Framework 4.6.2 support end?
Support for .NET Framework 4.6.2 ends on 12 January 2027. Upgrading to .NET Framework 4.8 or 4.8.1 is the quickest way to stay supported.
Can I upgrade directly from .NET Framework to .NET 10?
Yes, but it is a migration rather than a simple upgrade. Some technologies, such as Web Forms and parts of WCF, are not available in modern .NET and need to be replaced or reworked. A compatibility assessment will show the effort involved.
How long does a .NET migration take?
It depends on the size and complexity of the application. A framework upgrade can take a few weeks, while a full migration of a large application can take several months. Incremental modernisation lets you spread the work over time.
Is it safe to keep running .NET 8 after November 2026?
.NET 8 no longer receives security updates after 10 November 2026, so it becomes riskier with each new vulnerability. Upgrading to .NET 10 is the recommended path and is usually straightforward from .NET 8.
Conclusion
When a .NET version reaches end of support, nothing breaks overnight, and that is what makes it dangerous. Unpatched vulnerabilities, compliance gaps, failing dependencies and rising costs build up quietly until they become a serious business problem.
With .NET 8 and .NET 9 already out of support and .NET Framework 4.6.2 ending in January 2027, now is the time to act. Whether you need a quick framework upgrade, a full migration to .NET 10 or ongoing support for a legacy system, Softwiz Infotech can help you move forward safely. Get in touch today for your free .NET assessment.



