Visual Studio 2022 end of mainstream support (13 Jan 2027): upgrade plan

Summary. Visual Studio 2022 leaves mainstream support on 13 January 2027, and the last Patch Tuesday inside it is 12 January. The IDE keeps working. Extended support runs to 14 January 2032 with security updates only, on one baseline: version 17.14 on the Current Channel. What ends is non-security fixes, design-change requests and the no-charge support incidents bundled with subscriptions. The harder deadline comes first: .NET 8 and .NET 9 lose support on 10 November 2026, and Microsoft supports targeting net10.0 only in Visual Studio 18.0 (Visual Studio 2026) or later. Visual Studio 2026, at 18.11.3 as of 29 October 2026, has monthly feature updates, an annual in-place release each November and a one-year LTSC for Professional and Enterprise. Active subscribers get it at no extra cost; Microsoft lists first-year standard subscriptions at $1,199.88 for Professional and $5,999.04 for Enterprise. Our verdict: move .NET teams now, keep a patched 17.14 image only for code you cannot retarget, and check Windows 10 developer machines first, because Visual Studio 2026 does not list Windows 10 as supported.

About this article. For IT administrators, engineering leads and build owners who run Visual Studio on developer machines and CI agents. We checked dates, versions, prices and licence terms on 1 November 2026 against Microsoft's lifecycle and servicing pages, release notes, system requirements, the .NET support policy, the C++ team blog and the pricing page as served that day. Prices are US list prices and can change. This is not legal, licensing or financial advice, and no vendor paid for inclusion. Researched with AI assistance and reviewed by our editorial team.

What changes on 13 January 2027, and what does not

Visual Studio 2022 follows Microsoft's Fixed Lifecycle Policy, which Microsoft describes for this product as five years of mainstream support followed by five of extended support. It launched on 8 November 2021. There is no separate LTSC for 17.14. That release, shipped on 13 May 2025, is the final baseline and stays supported on the Current Channel until January 2032, as long as you stay on its latest servicing release. The policy table sets out the two phases:

The incident-support line is easy to miss. Microsoft's policy note limits incident benefits included with licensing programmes, Visual Studio subscriptions among them, to the mainstream phase. The pricing page lists four technical support incidents with Enterprise standard and two with Professional standard. If your subscribers use those incidents to chase Visual Studio 2022 debugger or build bugs, plan on that route closing in January. Visual Studio 2026 on the Stable Channel remains eligible for technical support.

A note on the date. The lifecycle page shows 06:59:59 Pacific time on 13 January 2027 and on 14 January 2032. The servicing page renders the second as 13 January 2032. Both 12 January 2027 and 13 January 2032 are second Tuesdays, so we read them as the last Patch Tuesdays in each phase; Microsoft does not name a final update. Agents, Build Tools, Remote Tools, Team Explorer and the Visual C++ Redistributable shipped with Visual Studio 2022 are supported as part of the same lifecycle.

The dates around it matter more than the date itself

For most teams, 13 January is the least disruptive date in this window. The table lists the dates that change what you can build and ship, from the Visual Studio 2022 lifecycle listing, the servicing page, the .NET support policy, the .NET Framework and Windows Server 2016 listings and the .NET Conf site.

CI agents on Windows Server 2016 lose security updates on the same Patch Tuesday unless you pay for Extended Security Updates, and among servers Visual Studio 2026 Build Tools install only on Windows Server 2019, 2022 and 2025, including Server Core. Our Windows Server 2016 migration playbook covers that side of the move.

Where Visual Studio stands in November 2026

Visual Studio 2026 reached general availability on 11 November 2025. Microsoft's release history shows 18.11.3 shipped on 29 October 2026, after eleven monthly feature updates from 18.1 to 18.11.

Microsoft's November 2025 announcement set the cadence: a new annual version each November alongside .NET, with Visual Studio 2026 updating in place to Visual Studio 2027 the following November. The servicing page gives November 2026 for that baseline without naming a day, lists the 2026-LTSC with an estimated release on 10 November 2026 and end of support on 9 November 2027, and runs the 2027-LTSC to November 2028. Community and Team Explorer users must update to the latest release within 180 days to keep using the product. Microsoft also says the LTSC is not needed just to keep a project in a known state, because .NET 10 and MSVC 14.50 stay available after the annual update.

So a single Visual Studio 2026 annual release is supported for about two years, while Visual Studio 2022 17.14 gets security fixes until 2032. For a frozen legacy codebase the old IDE has the longer runway on paper. The catch is everything around it: runtimes, SDKs, operating systems and compilers move on, and 17.14 will not follow them.

.NET: what Visual Studio 2022 can and cannot target

Microsoft's versioning page says targeting net10.0 is officially supported only in Visual Studio 18.0 and later. You can install the .NET 10 SDK next to Visual Studio 2022 17.14 without being blocked, but targeting a newer runtime from an older Visual Studio is unsupported and raises a build warning. Its SDK table reads:

The SDK that Visual Studio 2022 17.14 bundles and the .NET 9 runtime it targets both reach end of life on 10 November 2026, nine days after this check. An SDK will not load in a Visual Studio older than its minimum, so only the 10.0.1xx band runs in 17.14. From 10 November, a team doing modern .NET work on Visual Studio 2022 is either building for an unsupported runtime or targeting net10.0 in an unsupported configuration. In practice:

1. Move .NET 8 and .NET 9 apps to .NET 10 in Visual Studio 2026. .NET 10 is an LTS release, supported to 14 November 2028. Its SDK still builds older targets, so you can switch the IDE first and retarget project by project.

1. Build with the dotnet CLI in CI. Microsoft recommends dotnet build over msbuild for consistent tooling.

1. Do not plan around .NET Upgrade Assistant. Microsoft has deprecated it in favour of the GitHub Copilot modernization chat agent, included in Visual Studio 2026 and Visual Studio 2022 17.14.16 or later.

.NET Framework is a separate story. Visual Studio 2026 still targets .NET Framework 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 and 4.8.1, plus 3.5 SP1. But 4.6.2 itself reaches end of support on 13 January 2027, so retarget those projects to 4.8 or 4.8.1 while you are touching them. Our .NET partner guide for the 10 November cliff goes deeper on runtime migration.

C++: toolsets, ABI compatibility and the new MSVC lifecycle

C++ teams have more room than .NET teams, because the compiler is now decoupled from the IDE.

Old toolsets keep their old lifecycle. Microsoft says MSVC build tools 14.44 and earlier follow the lifecycle of the Visual Studio version they first shipped in, even when a later version installs them. The v143 build tools (v14.44) therefore track Visual Studio 2022, which means security support until 2032 even inside Visual Studio 2026.

New toolsets follow a new clock. From MSVC 14.50, which shipped with Visual Studio 2026 version 18.0 on 11 November 2025, the C++ team ships a release every six months (May and November) with nine months of support. Every two years the November release becomes an LTS with three years of support, and MSVC 14.50 is the first. LTS servicing is limited to security fixes after the first year.

The default compiler has already moved. Version 18.6 in May 2026 brought MSVC 14.51, which installs by default with the C++ desktop and gaming workloads and gets nine months of servicing. By our arithmetic that runs out around February 2027. For the longer runway, select a version-labelled component such as 14.50 instead of the latest one.

ABI compatibility still holds, with three rules. Binaries built with the v140, v141, v142, v143 and v145 toolsets can be combined, provided that:

• The linker is at least as new as the newest toolset used for any input.

• The Visual C++ Redistributable on the target machine is at least as new as the newest toolset used.

• Nothing built with /GL or /LTCG crosses versions. Those objects must use exactly the same build tools for compile and final link, down to the minor version.

Installers must tolerate a newer redistributable. There is one v14 redistributable per machine, and a newer one overwrites an older one. If your setup program tries to install the 2022 redistributable on a machine that already has the 2026 version, it gets error 0x80070666 by design. Microsoft's advice is to make installers recover from that silently.

Use the Setup Assistant for mixed estates. Visual Studio 2026 adds a Setup Assistant, opened with Retarget solution in Solution Explorer, that installs missing MSVC components and Windows SDKs, including tools from older Visual Studio versions.

Licensing: what you pay, and what you do not

The upgrade itself costs nothing for subscribers. Microsoft's pricing FAQ says the newest version stays available while your subscription is active, and that current and older versions are both included. The table uses the US list prices on the pricing page; volume licensing differs.

Watch three traps. First, Community: in an enterprise organisation, which Microsoft defines as more than 250 PCs or more than $1 million in annual revenue, it is not licensed beyond open-source, academic research and classroom use. Other organisations may use it for up to five users. Second, Microsoft says standalone Professional buyers purchase each new annual version, and the Store listing behind the $499 button now reads Visual Studio Professional 2026. A Professional 2022 licence does not carry you to Visual Studio 2026. Third, renewal pricing applies only if you renew within 30 days of the expiry date.

Stay, split or move: pick your path

The last row is the one workload we found that cannot simply move: Microsoft's release notes say that tooling is unavailable in Visual Studio 2026 and stays functional in Visual Studio 2022 until the deployment model retires on 31 March 2027.

Worked example: a 25-developer .NET and C++ team

Take a team of 25: 20 developers on Professional and 5 on Enterprise, all with active standard subscriptions, using Microsoft's US list prices.

Renewing standard subscriptions:

• Professional: 20 × $799.08 = $15,981.60

• Enterprise: 5 × $2,569.08 = $12,845.40

• Total: $28,827.00 a year, and the move to Visual Studio 2026 adds $0 in licence cost.

If the subscriptions lapse and you buy again:

• Professional: 20 × $1,199.88 = $23,997.60

• Enterprise: 5 × $5,999.04 = $29,995.20

• Total: $53,992.80, which is $25,165.80 more than renewing.

Switching everyone to monthly subscriptions:

• Professional: 20 × $45 × 12 = $10,800

• Enterprise: 5 × $250 × 12 = $15,000

• Total: $25,800 a year, or $3,027 less than renewal.

The monthly route looks cheaper until you price what it drops. Standard subscriptions carry Azure credit of $50 a month for Professional and $150 for Enterprise: 20 × $50 × 12 = $12,000 plus 5 × $150 × 12 = $9,000, so $21,000 a year forgone, along with Azure dev/test pricing and the perpetual licence. For a team running test environments in Azure, renewal wins. For short-term contractors, monthly makes sense.

The upgrade checklist, from 1 November to 12 January

That window is 72 days, roughly ten working weeks with the December break in the middle. The .NET date falls in week 2, so if you cannot retarget everything by 10 November, start with internet-facing apps.

Start the inventory with these commands. vswhere is included with Visual Studio 2017 and later. Its default search covers only Community, Professional and Enterprise, so add -products * to catch Build Tools on agents.

            & "${env:ProgramFiles(x86)}\Microsoft Visual Studio\Installer\vswhere.exe" -all -products '*' -format json
dotnet --list-sdks
          

1. Inventory every installation (week 1). List editions, versions and channels on developer machines and build agents.

1. Find the dead baselines (week 1). Any Visual Studio 2022 install below 17.14 is already outside support. Move those machines to the latest 17.14 servicing release, which was 17.14.44 on 29 October 2026, even if they will move to Visual Studio 2026 later.

1. Classify solutions (week 2). For each repository, record target frameworks, global.json pins, C++ PlatformToolset values and extensions. Flag .NET 8, .NET 9 and .NET Framework 4.6.2.

1. Check operating systems and licences (week 2). Visual Studio 2026 does not list Windows 10 as supported and rules out Windows Enterprise LTSC editions, S mode and pooled multi-user VDI hosts. It recommends 16 GB of RAM and an SSD for typical professional solutions. Reconcile assigned subscriptions and check Community use against the 250-PC and $1 million thresholds.

1. Pilot side by side (weeks 3 to 4). Install Visual Studio 2026 next to Visual Studio 2022 on a few machines, open real solutions and use the Setup Assistant to add v143 where needed.

1. Move CI (weeks 4 to 6). Build agent images with Visual Studio 2026 Build Tools on Windows Server 2019 or later, or in Windows containers. On GitHub, windows-latest and windows-2025 already use the Visual Studio 2026 image. GitHub said windows-11-arm would follow by 30 September, but its README still listed that label separately on 1 November, so check what your jobs get. Our note on the GitHub Actions windows-11-arm switch covers what changes.

1. Set the channel policy (week 6). Decide which teams follow the Stable Channel and which sit on the 2026-LTSC once it opens, and deliver Microsoft's monthly administrator updates through your patch tooling.

1. Retarget and test (weeks 6 to 9). Move .NET apps to net10.0 and .NET Framework apps to 4.8 or 4.8.1. Rebuild C++ binaries that use /GL or /LTCG, and make installers tolerate a newer redistributable.

1. Keep a patched legacy image (week 10). Keep one Visual Studio 2022 17.14 network layout for code you cannot move. Refresh it with each servicing release, because only the latest is supported, name an owner, and set a review date well before 2032.

If developers use AI agents inside the IDE, review that configuration too. Our piece on Visual Studio 2026 agent skills and the trust gap lists the folders agents read from.

India, EU and US notes

India. Microsoft publishes subscription prices in US dollars, and its FAQ says pricing is the same when converted across currencies. Standard subscriptions are not sold through CSP, where partners offer only monthly subscriptions; the routes listed for standard are Open Value, Enterprise Agreement and the Microsoft Store. The Store listing served to us in India on 1 November showed Visual Studio Professional 2026 at ₹42,593.39 including GST, so take a local quote rather than converting $499.

EU and US. Microsoft's C++ team names the EU Cyber Resilience Act and the US cybersecurity executive order, alongside NIST and CISA standards, when it argues that outdated compilers are no longer acceptable. That is a vendor's framing, not a legal reading, so check your own obligations and record which toolset built each release. We would expect an unsupported .NET runtime to be a harder audit finding than an IDE in extended support.

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our application development services team can run this upgrade as a scoped project, from the inventory of installs and build agents to .NET 10 retargeting, C++ toolset checks and rebuilt CI images. Talk to us at /contact-us/.

Last updated: 1 November 2026.

References

1. Visual Studio 2022 lifecycle — Microsoft Learn

1. Visual Studio 2022 Product Lifecycle and Servicing — Microsoft Learn

1. Fixed Lifecycle Policy — Microsoft Learn

1. .NET and .NET Core Support Policy, updated 25 October 2026 — Microsoft .NET

1. .NET SDK, MSBuild, and Visual Studio versioning — Microsoft Learn

1. Visual Studio Release History — Microsoft Learn

1. Visual Studio Channels and Release Rhythm — Microsoft Learn

1. Visual Studio subscriptions pricing — Microsoft

1. Visual Studio 2026 Product Family System Requirements — Microsoft Learn

1. Visual Studio Product Lifecycle and Servicing — Microsoft Learn

1. Microsoft .NET Framework lifecycle — Microsoft Learn

1. Windows Server 2016 lifecycle — Microsoft Learn

1. .NET Conf 2026 — .NET Conf

1. Visual Studio: Built for the Speed of Modern Development, 24 November 2025 — Visual Studio Blog

1. What is .NET Upgrade Assistant? — Microsoft Learn

1. Visual Studio Platform Targeting and Compatibility — Microsoft Learn

1. New release cadence and support lifecycle for Microsoft C++ Build Tools, 24 November 2025 — C++ Team Blog

1. Visual Studio release notes — Microsoft Learn

1. C++ binary compatibility between Visual Studio versions — Microsoft Learn

1. Use native multi-targeting in Visual Studio to build old projects — Microsoft Learn

1. Visual Studio Community — Microsoft

1. Visual Studio Professional 2026 — Microsoft Store

1. Tools for detecting and managing Visual Studio instances — Microsoft Learn

1. vswhere command-line help strings — Microsoft on GitHub

1. Visual Studio 2022 Release History — Microsoft Learn

1. GitHub Actions runner images README — actions/runner-images on GitHub

1. The windows-11-arm image label will use Windows 11 Arm64 with Visual Studio 2026 image in September 2026 — actions/runner-images on GitHub