Visual Studio 2022 leaves mainstream support on 12 January 2027. That is the date everyone quotes, and it is the wrong one to plan around.
The constraint that actually bites arrives sooner. Visual Studio 2022 cannot target .NET 10 inside the IDE, current .NET 10 SDK feature bands refuse to load in it at all, and the SDK band it does ship with falls out of support in November 2026. If you are on any servicing baseline other than 17.14, you are already unsupported today.
Maintaining .NET 8 or 9? Keep Visual Studio 2022. Starting .NET 10 work? You need 2026.
Both are genuine perpetual Microsoft licences with instant delivery and UK support — no annual fee on either.
VS 2022 Professional — … VS 2026 Professional — …What actually happens on 12 January 2027
Visual Studio 2022 follows Microsoft’s Fixed Lifecycle Policy: ten years of support, split into five years of mainstream support and five years of extended support. It shipped on 8 November 2021, so the mainstream half closes on 12 January 2027 and the extended half runs to 13 January 2032.
It is worth being precise about this, because a lot of coverage is not. Visual Studio 2022 is not reaching end of life in January 2027. It reaches end of life in January 2032. What happens in January 2027 is that it stops receiving bug fixes, performance work and compatibility updates, and drops back to security patches only for its final five years.
That distinction matters commercially. An IDE receiving security patches until 2032 is a perfectly defensible tool for maintaining an existing codebase. What it is not is a tool you can rely on to keep pace with the .NET platform — and that is where the real deadline lives.
First question: are you supported right now?
Most teams assume that running “Visual Studio 2022” means running something supported until 2027. That is not how Visual Studio servicing works. Microsoft supports specific servicing baselines, not the product name, and every Visual Studio 2022 baseline except one has already expired.
| Servicing baseline | Available from | Support ended | Status today |
|---|---|---|---|
| 17.14 (Current Channel) | 13 May 2025 | 13 January 2032 | Supported |
| 17.12 (LTSC) | 12 November 2024 | 14 July 2026 | Expired |
| 17.10 (LTSC) | 21 May 2024 | 13 January 2026 | Expired |
| 17.8 (LTSC) | 14 November 2023 | 8 July 2025 | Expired |
| 17.6 and earlier (LTSC) | 2022–2023 | 14 January 2025 or earlier | Expired |
Microsoft never created an LTSC channel for 17.14. Instead it made 17.14 on the Current Channel the final servicing baseline for the entire 2022 generation. The practical effect is that the long-term servicing route out of Visual Studio 2022 closed on 14 July 2026, when 17.12 expired. There is no LTSC baseline left to sit on.
Open Visual Studio and go to Help > About Microsoft Visual Studio. If the version does not begin 17.14, you are running an unsupported build today — regardless of the January 2027 date. Updating to 17.14 is free for any existing Visual Studio 2022 licence and takes one pass of the Visual Studio Installer.
If your organisation is subject to Cyber Essentials, ISO 27001 or a similar framework, this is the detail that shows up in an audit. “We are on Visual Studio 2022, supported until 2027” does not survive contact with an auditor who checks the minor version and finds 17.10.
The .NET ceiling — the constraint nobody mentions
Here is the part that changes the decision, and it has nothing to do with the lifecycle dates.
Every .NET SDK has a minimum Visual Studio version, and each SDK also caps the highest framework you can target from inside the IDE — a cap that can be lower than what the same SDK allows from the dotnet command line. For Visual Studio 2022, those two numbers have already parted company.
| .NET SDK | Ships with | Minimum VS | Max target in IDE | Max target via CLI |
|---|---|---|---|---|
| 9.0.300 | VS 17.14 | 17.12 | net9.0 | net9.0 |
| 10.0.100 | VS 18.0 | 17.14 | net9.0 | net10.0 |
| 10.0.200 | VS 18.4 | 18.0 | net10.0 | net10.0 |
| 10.0.300 | VS 18.6 | 18.0 | net10.0 | net10.0 |
| 10.0.400 | VS 18.9 | 18.0 | net10.0 | net10.0 |
Read the middle row carefully. The first .NET 10 SDK, 10.0.100, will install alongside Visual Studio 2022 17.14 and will build a net10.0 project — but only from the command line. Inside the IDE, the highest framework you can target is net9.0. You can compile .NET 10 code on that machine; you cannot open, debug, or manage a .NET 10 project in Visual Studio 2022 the way you would expect to.
Then look at the rows below it. From SDK 10.0.200 onward — shipped March 2026, so this is already the past — the minimum Visual Studio version is 18.0. Visual Studio 2022 is not merely limited by those SDKs. It cannot load them. Any team on the current .NET 10 SDK feature band, which as of August 2026 is 10.0.400, is outside what Visual Studio 2022 can open at all.
Visual Studio 2022 is a fully supported IDE for .NET 8 and .NET 9 development, and will stay patched until 2032. For .NET 10 it is not a slow option or a limited option — it is not an option. The platform moved past it in March 2026, ten months before the lifecycle date suggests anything changes.
Why November 2026 is the date to diary
Visual Studio 2022 17.14 ships with .NET SDK 9.0.300. That SDK feature band’s support ends in November 2026. So does .NET 9 itself, which as a Standard Term Support release reaches end of support that month.
Stack the three dates and the sequence is clearer than the headline suggests:
- March 2026 — already passed. .NET SDK 10.0.200 raises the minimum to Visual Studio 18.0. Current .NET 10 SDK bands stop loading in Visual Studio 2022 entirely.
- November 2026 — three months away. .NET 9 and SDK band 9.0.3xx reach end of support. The framework Visual Studio 2022 is built around stops receiving patches, even though the IDE itself is still supported.
- 12 January 2027. Visual Studio 2022 leaves mainstream support. Bug fixes and compatibility work stop; security patches continue.
- 13 January 2032. Extended support ends. Visual Studio 2022 receives nothing further.
If your codebase targets .NET 9, the meaningful deadline is November 2026, not January 2027 — and it is a framework deadline, not an IDE one. Migrating to .NET 10 is the work that matters; the Visual Studio upgrade is a prerequisite for doing it, not the project itself.
Who can stay on Visual Studio 2022 — and who cannot
The blanket “upgrade now” advice you will find elsewhere is wrong for a meaningful share of developers. Visual Studio 2022 has security patches until 2032. That is a long runway, and for some work it is entirely sufficient.
Stay where you are if…
- You maintain .NET 8 or .NET 9 applications with no plan to move framework
- You work on .NET Framework 4.x line-of-business apps that are not moving
- You maintain legacy C++ projects with a fixed toolset
- You need a second machine or a build agent licensed cheaply for existing work
- Your CI pipeline is pinned to a toolchain you do not intend to disturb
Update to 17.14 first — that is non-negotiable either way.
VS 2022 Professional — …You need to move if…
- You are starting any new .NET 10 project
- You need to target
net10.0from within the IDE - You are on .NET 10 SDK band 10.0.200 or later — it will not load in VS 2022
- You need C# 14 language features
- You want current Copilot and agent tooling rather than the 2022 extension model
- You are planning a migration off .NET 9 before November 2026
One planning note for anyone in the second column. Visual Studio 2026 is the first release to follow Microsoft’s Modern Lifecycle Policy rather than the Fixed Lifecycle Policy — annual releases, roughly two years of support each, rather than a ten-year window. That is a different maintenance rhythm to the one Visual Studio 2022 taught you, and it is worth understanding before you commit. Our Visual Studio 2026 licensing guide for .NET developers covers how that cadence works in practice, and the 2022 vs 2026 comparison goes feature by feature.
Five-year cost: perpetual licence vs subscription
Microsoft’s own route to Visual Studio Professional is an annual subscription at roughly £420 per year. A perpetual licence is a single payment with no renewal, which changes the shape of the cost considerably over a normal hardware refresh cycle.
Cumulative spend over five years. Subscription figure based on approximately £420 per year for Visual Studio Professional. Perpetual licences are one-time purchases with no renewal.
The comparison is not purely financial, though. A subscription includes Azure credits, Microsoft 365 developer benefits and rolling access to new releases, which suits teams that want to stay on the annual cadence. A perpetual licence suits developers who want a fixed cost for a known toolset and are content to make a deliberate decision each time they upgrade. If your instinct is that you would rather buy the tool once and revisit the question in five years, the perpetual route is the honest fit.
A sensible plan for the next five months
- Check your version this week.
Help > Abouton every developer machine and build agent. Anything below 17.14 is unsupported now, and updating is free. - Audit your target frameworks. Search your solutions for
<TargetFramework>. Anything onnet9.0has a November 2026 framework deadline that is independent of your IDE. - Check your SDK band. Run
dotnet --list-sdks. If you see 10.0.200 or higher and expect to open those projects in Visual Studio, you need 2026. - Decide per project, not per team. Legacy maintenance and new .NET 10 work have different answers. Running both IDEs side by side is supported and often the cheapest correct outcome.
- Budget before January. If you are buying licences, a perpetual purchase in this financial year avoids a recurring line item and removes the deadline from next year’s planning entirely.
January 2027 is not the only Microsoft deadline in your calendar. Our Visual Studio end of life reference covers where every version stands, and October 2026’s deadline month collects the Office, Windows and Publisher dates landing before this one.
Frequently asked questions
Visual Studio 2022 leaves mainstream support on 12 January 2027 and reaches full end of life on 13 January 2032. Between those dates it receives security patches only, with no bug fixes, feature updates or platform compatibility work.
No. This is a common misreading of the lifecycle. January 2027 is the end of mainstream support, not end of life. Visual Studio 2022 continues to receive security patches for a further five years, until 13 January 2032.
Only version 17.14 on the Current Channel. Microsoft did not create an LTSC channel for 17.14, making it the final servicing baseline for the 2022 generation. Every LTSC baseline has now expired — 17.12 was the last, ending 14 July 2026. Check yours under Help > About Microsoft Visual Studio; updating to 17.14 is free with an existing licence.
Not from within the IDE. Visual Studio 2022 17.14 can use .NET SDK 10.0.100, but the highest framework you can target inside Visual Studio is net9.0; building for net10.0 with that SDK works only from the dotnet command line. From SDK 10.0.200 onward, released March 2026, the minimum Visual Studio version is 18.0, so current .NET 10 SDK bands will not load in Visual Studio 2022 at all. Targeting .NET 10 properly requires Visual Studio 2026.
It depends on your framework, not the calendar. If you are maintaining .NET 8, .NET 9 or .NET Framework applications with no plan to move, Visual Studio 2022 remains a supported and sensible tool with patches until 2032. If you are starting .NET 10 work, need C# 14, or are on a current .NET 10 SDK band, Visual Studio 2026 is required rather than merely preferable.
Yes. Visual Studio versions install side by side and are designed to coexist, each with its own instance and toolset. This is often the most practical arrangement — 2026 for new .NET 10 work, 2022 retained for legacy solutions that are not worth migrating. Each installation needs its own licence.
It will continue to work and will keep receiving security patches until 2032. What stops is everything else: bug fixes, performance work, and validation against new Windows releases, .NET versions and Azure SDK changes. Extension vendors also drop support for older Visual Studio versions over time, so tooling breakage tends to arrive gradually rather than on a specific date.
Over any period longer than about a year, yes, considerably. A Visual Studio Professional subscription runs at roughly £420 per year with no end, while a perpetual licence is a single payment that never renews. The subscription includes Azure credits and other developer benefits, so the comparison is not purely on price — but for a developer who wants a fixed cost for a known toolset, the perpetual route is materially cheaper.
Yes, and this catches teams out. .NET 9 is a Standard Term Support release reaching end of support in November 2026, as does SDK feature band 9.0.3xx which ships with Visual Studio 2022 17.14. That is roughly two months before Visual Studio 2022 leaves mainstream support, so for most teams the framework deadline arrives first.
Gary Walsh is the Head of Tech Support at Software Supplies, with more than 20 years in the IT industry. Fully Microsoft-certified and experienced across the full business software stack — from Windows and Office to cloud infrastructure and device management — Gary delivers practical, no-nonsense advice that helps users and businesses get the most from their technology.
