{"id":257725,"date":"2026-11-10T10:06:36","date_gmt":"2026-11-10T18:06:36","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=257725"},"modified":"2026-11-10T10:06:36","modified_gmt":"2026-11-10T18:06:36","slug":"announcing-visual-studio-2026-ltsc-1811","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/announcing-visual-studio-2026-ltsc-1811\/","title":{"rendered":"Announcing Visual Studio 2026 LTSC 18.11"},"content":{"rendered":"

Today, we are announcing Visual Studio 2026 Long-Term Servicing Channel (LTSC) 18.11 alongside Visual Studio 2026 18.12<\/a> on the Stable channel. LTSC 18.11 will receive two years of support, through November 14, 2028, rather than the one year of LTSC support we previously announced. If you are using Visual Studio 2022 for its LTSC benefits this is a great time to consider migrating to the new Visual Studio 2026 LTSC 18.11 to get the latest Visual Studio has to offer. <\/span>\u00a0<\/span><\/p>\n

Visual Studio 2026 LTSC 18.11 is not a new product – it is a new support and servicing channel for Visual Studio 2026 so it includes the full feature set, capabilities, and fixes as Visual Studio 2026 18.0 through 18.10. If you have stayed on Visual Studio 2022 while waiting for a Visual Studio 2026 LTSC release with LTS toolsets, you should begin planning validation and deployment of LTSC 18.11.<\/span><\/p>\n

View the Visual Studio 2026 LTSC 18.11 Release Notes<\/a><\/div><\/p>\n

We are not changing how the Stable channel works. Stable will continue receiving monthly feature and quality updates. If you are on Stable and want to keep receiving those updates, you do not need to change anything. LTSC is an option if your organization needs to stay on a fixed release.<\/span><\/p>\n

Why are we making this change?<\/span><\/b><\/h2>\n

In November 2025, we <\/span>announced a new release and support model<\/span><\/a> with Visual Studio 2026, including one year on Stable followed by one year of LTSC support. Customers told us that one year of LTSC support did not leave enough time to validate and deploy a release. The longer support period gives those organizations more time to deploy and use LTSC 18.11.<\/span>\u00a0<\/span><\/p>\n

An LTSC release with LTS toolsets<\/span><\/b><\/h2>\n

Visual Studio 2026 LTSC 18.11 will include Long-Term Support (LTS) toolsets for .NET and C++ development: .NET 10 LTS and MSVC 14.50 and 14.52. The MSVC and .NET toolsets in Visual Studio 2026 LTSC 18.11 will be supported per their respective support lifecycles, which are at least as long as the support lifecycle for Visual Studio 2026 LTSC 18.11.<\/span>\u00a0<\/span><\/p>\n

Stable is for feature updates and servicing, we recommend this as the default<\/span><\/b><\/h2>\n

Stable remains the recommended channel if you want the latest Visual Studio features, including new GitHub Copilot capabilities. To remain supported on Stable, keep your installation current with its monthly updates. Stable is where most customers will be and we strongly recommend this channel so you can receive and take advantage of the latest features Visual Studio has to offer.\u00a0<\/span>\u00a0<\/span><\/p>\n

LTSC will get servicing only<\/span><\/b><\/h2>\n

LTSC 18.11 will receive security and other critical fixes, we do not plan to ship regular feature updates for LTSC like we will for the Stable cannel. If you choose LTSC to limit feature changes in your development environment, you still need to keep your installation current with LTSC servicing updates to remain supported.<\/span>\u00a0<\/span><\/p>\n

Existing Visual Studio 2026 keys continue to work<\/span><\/b><\/h2>\n

Visual Studio 2026 LTSC 18.11 is not a new product, the product remains Visual Studio 2026. Today\u2019s announcement is a new channel for the existing product. Therefore, existing Visual Studio 2026 product keys will continue to work on both Stable and LTSC 18.11 for Enterprise, Professional, and the Build Tools SKUs. You do not need a new key or another purchase of Visual Studio 2026 to use either channel.<\/span>\u00a0<\/span><\/p>\n

Getting started<\/span><\/b><\/h2>\n

If your organization has stayed on Visual Studio 2022 while waiting for a Visual Studio 2026 LTSC release with LTS toolsets, you should begin planning validation and deployment of LTSC 18.11.<\/span>\u00a0<\/span><\/p>\n

Before deployment, review <\/span>Visual Studio Product Lifecycle and Servicing<\/span><\/a> for support requirements and installation and deployment guidance. See the <\/span>Visual Studio 2026 LTSC 18.11 release notes<\/span><\/a> for release details.<\/span>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Today, we are announcing Visual Studio 2026 Long-Term Servicing Channel (LTSC) 18.11 alongside Visual Studio 2026 18.12 on the Stable channel. LTSC 18.11 will receive two years of support, through November 14, 2028, rather than the one year of LTSC support we previously announced. If you are using Visual Studio 2022 for its LTSC benefits […]<\/p>\n","protected":false},"author":712,"featured_media":255385,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[],"class_list":["post-257725","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio"],"acf":[],"blog_post_summary":"

Today, we are announcing Visual Studio 2026 Long-Term Servicing Channel (LTSC) 18.11 alongside Visual Studio 2026 18.12 on the Stable channel. LTSC 18.11 will receive two years of support, through November 14, 2028, rather than the one year of LTSC support we previously announced. If you are using Visual Studio 2022 for its LTSC benefits […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/257725","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/712"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=257725"}],"version-history":[{"count":1,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/257725\/revisions"}],"predecessor-version":[{"id":257768,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/257725\/revisions\/257768"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/255385"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=257725"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=257725"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=257725"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}