Visual Studio 2022 End of Support: Which Versions Ended in 2026?

Visual Studio 2022 has not reached the end of support as a complete product. However, every dedicated Visual Studio 2022 Long-Term Servicing Channel (LTSC) release is now out of support.

The latest deadline affected Visual Studio 2022 version 17.12 LTSC , which reached the end of support on July 14, 2026 . Version 17.10 LTSC had already reached its support deadline on January 13, 2026.

That does not mean every Visual Studio 2022 user must immediately move to a new major release. Visual Studio 2022 version 17.14 on the Current Channel remains supported until January 13, 2032 , as long as users continue installing Microsoft’s latest servicing updates.

This guide breaks down the Visual Studio 2022 end-of-support dates, explains which versions and editions are affected, and helps you decide whether to update to version 17.14 or move to Visual Studio 2026.

Visual Studio 2022 End of Support: Quick Answer

Here is the current position as of July 2026:

• Visual Studio 2022 is still supported as a product.
• Version 17.12 LTSC reached the end of support on July 14, 2026.
• Version 17.10 LTSC reached the end of support on January 13, 2026.
• All earlier Visual Studio 2022 LTSC versions are also out of support.
• Version 17.14 Current Channel remains supported.
• Version 17.14 is supported until January 13, 2032.
• Users must keep version 17.14 updated with the latest servicing releases.
• Microsoft did not release a separate version 17.14 LTSC channel.

The July 14, 2026 deadline applied specifically to version 17.12 LTSC , not to every installation carrying the Visual Studio 2022 name.

Is Visual Studio 2022 Still Supported?

Yes. Visual Studio 2022 remains covered by Microsoft’s Fixed Lifecycle Policy.

The overall product lifecycle is:

During Mainstream Support, Microsoft may provide security updates, quality fixes, feature improvements, and platform updates. Extended Support is more limited and mainly focuses on security updates.

The lifecycle applies to Visual Studio 2022 Community, Professional, and Enterprise. It also covers certain related components, including Build Tools, Remote Tools, Performance Tools, and the Visual C++ Redistributable.

Microsoft’s official Visual Studio 2022 lifecycle page provides the complete product policy and support dates.

Visual Studio 2022 End-of-Support Dates by Version

Visual Studio 2022 has been serviced through two different models: the Current Channel and a series of LTSC releases.

The table below shows the support status of each major servicing baseline.

As of July 2026, version 17.14 Current Channel is the only supported Visual Studio 2022 servicing baseline .

What Happened to Visual Studio 2022 Version 17.12 LTSC?

Visual Studio 2022 version 17.12 LTSC was released on November 12, 2024. Its servicing period ended on July 14, 2026.

The software will not suddenly stop opening after that date. Developers may still be able to launch the IDE, edit code, compile projects, and use installed extensions.

The main change is that Microsoft no longer provides normal ongoing servicing for the 17.12 LTSC baseline. Continuing to use it may therefore introduce security, compatibility, and technical support concerns over time.

Organizations still running version 17.12 have two main options:

1. Update to Visual Studio 2022 version 17.14 Current Channel.
2. Move to Visual Studio 2026 after checking project, extension, and workload compatibility.

For most teams, moving from version 17.12 to 17.14 will be the less disruptive option because both belong to the Visual Studio 2022 generation.

Did Visual Studio 2022 Version 17.10 Also End Support?

Yes. Visual Studio 2022 version 17.10 LTSC reached the end of support on January 13, 2026.

Organizations still using version 17.10 should update as soon as reasonably possible. The same applies to versions 17.8, 17.6, 17.4, 17.2, and 17.0, which reached their support deadlines earlier.

This is why the installed version number matters. A computer may display “Visual Studio 2022” while still running an unsupported servicing baseline underneath.

Simply checking the product name is not enough. You also need to confirm the minor version and update channel.

Is Visual Studio 2022 Version 17.14 an LTSC Release?

No. Microsoft did not create a separate LTSC channel for Visual Studio 2022 version 17.14.

Instead, Microsoft made version 17.14 on the Current Channel the final supported Visual Studio 2022 release. It will remain supported for the rest of the product lifecycle, which ends on January 13, 2032.

In practice, version 17.14 acts as the final long-term baseline for Visual Studio 2022. Microsoft still classifies it as a Current Channel release; however, rather than an LTSC release.

Users must also continue installing the latest 17.14 servicing updates. Staying on an older 17.14.x build indefinitely could leave the installation without recent security, reliability, and compatibility fixes.

You can review the latest requirements in Microsoft’s Visual Studio 2022 servicing documentation .

What About Non-LTSC Visual Studio 2022 Versions?

Non-LTSC installations use the Current Channel.

Under this model, support depends on running Microsoft’s latest supported minor version and keeping it updated with the newest servicing releases.

Now that version 17.14 is the final Visual Studio 2022 Current Channel version, users running older releases such as 17.13, 17.1,1 or 17.9 should update to 17.14.

Older Current Channel releases do not receive the same fixed support period that Microsoft provided for LTSC baselines. Current Channel users are expected to move forward as new supported versions become available.

The practical rule is simple:

To remain on Visual Studio 2022, install the latest available servicing release of version 17.14.

Visual Studio 2022 Professional End of Support

Visual Studio Professional 2022 has not reached the end of support as an edition.

Its overall lifecycle continues until January 13, 2032. However, the support status of an individual installation depends on its version and update channel.

Developers who plan to continue with the 2022 generation can explore Microsoft Visual Studio Professional 2022 and keep the installation updated to the latest version 17.14 servicing release.

Existing users do not normally need a new product key simply to install a servicing update within Visual Studio 2022. A new licence may be necessary when adding users or expanding an organization’s licensed deployment, depending on the applicable licensing terms.

Does End of Support Mean Visual Studio Will Stop Working?

Usually not.

An unsupported Visual Studio installation may continue to open, compile projects, and run existing extensions. End of support affects Microsoft’s servicing commitment rather than switching off the software.

An unsupported version may stop receiving:

• Security updates
• Reliability fixes
• Compatibility improvements
• Quality updates
• Microsoft technical support
• Fixes for affected IDE components

This can become a serious concern when developers work with proprietary code, production credentials, customer information, or regulated systems.

It is also important to remember that Visual Studio is only one part of a development environment. .NET SDKs, Windows SDKs, compilers, libraries, extensions, and third-party tools may all follow separate lifecycle policies.

Updating the IDE does not automatically mean that every installed component is supported. Teams should review the whole development stack rather than treating Visual Studio as an isolated application.

How to Check Your Visual Studio 2022 Version

To find your installed version:

1. Open Visual Studio 2022.
2. Select Help from the top menu.
3. Choose About Microsoft Visual Studio .
4. Find the full version number.
5. Note whether you are using Community, Professional, or Enterprise.

An installation beginning with 17.12 belongs to the expired version 17.12 baseline. A supported Visual Studio 2022 installation should show 17.14 , followed by its servicing build number.

How to check your update channel

You should also confirm which update channel the installation uses:

1. Open the Visual Studio Installer.
2. Find the relevant Visual Studio 2022 installation.
3. Select More .
4. Choose Update settings .
5. Review the selected update channel.

Different Visual Studio installations on the same computer can use different update channels. Check each instance separately rather than assuming they all share one configuration.

How to Update Visual Studio 2022 to Version 17.14

The easiest way to update is through the Visual Studio Installer:

1. Save your work and close Visual Studio.
2. Open the Visual Studio Installer.
3. Find your Visual Studio 2022 installation.
4. Select More , followed by Update settings .
5. Switch to the Current Channel where necessary.
6. Select Update .
7. Restart the computer if prompted.
8. Reopen Visual Studio.
9. Confirm that version 17.14 is installed.
10. Test your most important projects, workloads, and extensions.

Microsoft also supports updates through IDE notifications, administrator updates, command-line deployments, and network installation layouts. Its official Visual Studio update guide explains these methods in more detail.

Before rolling out the update across an organization, test the components that matter most to your development workflow:

• Visual Studio extensions
• .NET SDKs
• Windows SDKs
• C++ toolsets
• MSBuild configurations
• Database projects
• Azure workloads
• Internal templates
• Build automation
• CI/CD pipelines

A small pilot group can help identify compatibility problems before the update reaches every developer and build system.

Should You Stay on Visual Studio 2022 or Upgrade to Visual Studio 2026?

There is no need to rush into a major upgrade simply because version 17.12 LTSC reached the end of support.

Visual Studio 2022 version 17.14 remains supported until January 13, 2032. For many organizations, updating to 17.14 will be the most practical next step.

Visual Studio 2026 may still be worth considering if your team is already planning a wider refresh.

Stay with Visual Studio 2022 version 17.14 when:

• You want the smallest change from version 17.12.
• Your current projects are already validated for Visual Studio 2022.
• Important extensions and internal tools work reliably with version 17.14.
• You are not ready for a major IDE migration.
• You want a supported environment that can remain in place until 2032.

Teams considering an upgrade may also find our Visual Studio 2026 vs Visual Studio 2022 comparison useful.

Consider Visual Studio 2026 when:

• You want access to the latest Visual Studio platform and features.
• Your projects and extensions support the newer version.
• You are already planning a wider development environment refresh.
• Your team needs newer Enterprise testing and diagnostic capabilities.
• You want to modernize older development workflows.

For a closer look at the newer release, read our Visual Studio 2026 Enterprise overview .

Organizations ready to move to the newer Enterprise edition can also explore Microsoft Visual Studio 2026 Enterprise .

Recommended Action by Installed Version

Final Thoughts

The phrase “Visual Studio 2022 End of Support” can sound more dramatic than the situation really is.

Visual Studio 2022 itself did not reach the end of support on July 14, 2026. That date applied specifically to version 17.12 LTSC . Version 17.10 and every earlier Visual Studio 2022 LTSC release had already passed their own support deadlines.

For teams that want the least disruptive route forward, the simplest option is to update to the latest servicing release of version 17.14 Current Channel . It remains supported until January 13, 2032.

Organizations planning a broader modernization project can instead evaluate Visual Studio 2026 after checking their projects, extensions, SDKs, and development workflows for compatibility.

Before deciding, review the actual version and update channel used across developer workstations, virtual environments, and build systems. The product name may still say Visual Studio 2022, but the version number and servicing channel reveal whether the installation is truly supported.