Visual Studio 2026 Drops Live Share in Version 18.12 Update

Visual Studio 2026 version 18.12 reached general availability on the Stable channel on November 10, 2026, and it permanently removes Live Share. Microsoft's own release notes say the GA build "will no longer offer or bundle Live Share," and any copy of the extension still installed from an older build gets disabled once a machine is running Visual Studio 18.11.3 or later — with no bundled replacement in the box.

What changed in Visual Studio 18.12

Version 18.12 is the latest monthly update on Visual Studio 2026's Stable channel, following the version 18.11.x line that shipped through October and early November. Alongside a batch of Copilot and debugger features, Microsoft used the 18.12 release notes to confirm something it had signaled was coming: Live Share, the pair-programming and screen-sharing extension built into Visual Studio for years, is no longer part of the product.

This isn't a bug, a licensing change, or a connectivity outage — developers searching for why Live Share stopped working or won't connect in Visual Studio are running into an intentional removal, documented in Microsoft's Visual Studio 2026 release notes. Live Share shipped as a built-in way to share an editing session, debug together, and run terminals or servers jointly from inside Visual Studio and VS Code, and it has been a standard part of the Visual Studio collaboration story since its general availability years ago. Its removal from the flagship IDE marks one of the more visible feature cuts in a Visual Studio 2026 release cycle that has otherwise focused on adding Copilot and debugger capabilities rather than taking them away.

Microsoft's exact wording on the removal

The release notes are specific about both the cutoff and what still works underneath. In the 18.12 section, Microsoft states:

"Visual Studio 18.12 GA will no longer offer or bundle Live Share. Previously installed Live Share extensions will be disabled on Visual Studio 18.11.3 and later. API assemblies used by other Visual Studio features remain available."

That last sentence matters for extension authors: Live Share's underlying API assemblies aren't being ripped out of the IDE entirely, because other Visual Studio features depend on them internally. What's gone is the user-facing Live Share experience — starting a collaborative session, sharing a workspace, or joining someone else's session from inside Visual Studio.

Timeline: when Live Share stopped working

The removal happened in two steps rather than overnight:

In practice, anyone who updated Visual Studio through late October would have already noticed Live Share stop responding before the 18.12 GA build made the removal official and permanent.

Why Microsoft pulled Live Share now

Microsoft's release notes and devblog posts don't spell out a single reason for the timing, but the groundwork was laid well before 18.12. Microsoft's own Live Share documentation states plainly that the extension has been in maintenance mode, with no new features planned, and that the Visual Studio 2026 Live Share deprecation and alternatives page now carries a direct notice: "Live Share is deprecated in Visual Studio 2026. Visual Studio 2026 (version 18.12) no longer includes Live Share."

That page also makes a point of separating the two products: "The Visual Studio release announcement doesn't announce a change to the Live Share extension for Visual Studio Code." In other words, this is a Visual Studio (the full IDE) decision, not a decision about the Live Share extension that ships for VS Code.

The maintenance-mode notice isn't the first sign of the extension winding down, either. The separate Visual Studio Live Share Audio extension — a companion extension that added voice chat to collaboration sessions — carries its own marketplace notice stating it "has been deprecated," and Microsoft's documentation frames the Visual Studio IDE removal as the next, more consequential step rather than a standalone decision made in isolation.

What to use instead of Live Share

Microsoft's own planning guidance lists three alternatives for teams that relied on Live Share inside Visual Studio, while cautioning that none of them reproduces every Live Share feature:

• Screen sharing in Microsoft Teams. You can present your Visual Studio window and hand control to a trusted participant, but everyone works from the shared screen rather than independent editor sessions. See Microsoft's guide to presenting content in Teams meetings.
• Asynchronous review with Git and GitHub pull requests. Microsoft points to Git in Visual Studio paired with GitHub pull requests for sharing branches and reviewing changes — useful for code review, but it doesn't provide live co-editing.
• Cloud development environments. GitHub Codespaces can give a team a consistent, repository-based environment accessed through VS Code, a browser, or the GitHub CLI. Microsoft is explicit that Codespaces "doesn't provide shared live editing by itself" and that usage can incur charges.

Microsoft's guidance also urges teams to weigh access, security, platform requirements, and cost before settling on a substitute — there isn't an official like-for-like swap for Live Share's real-time, multi-cursor pairing inside Visual Studio itself.

Is Live Share in VS Code also affected?

No — and this is the detail worth bookmarking if autocomplete sent you here looking for a "Live Share alternative" or "Live Share download." The Live Share extension that runs inside Visual Studio Code is a separate product listing from the Visual Studio (IDE) integration, and Microsoft's documentation does not announce any change to it. The extension remains listed on the Visual Studio Marketplace, where it shows roughly 24.4 million installs and is still free to install, and continues to be installable for VS Code users; existing capabilities keep working, support requests go through Microsoft's standard channels, but — per the maintenance-mode notice — no new features are planned for it either. If your team's workflow is VS Code rather than full Visual Studio, this particular change shouldn't touch you, though the extension's own long-term roadmap looks frozen.

That split mirrors a broader pattern worth keeping straight: Visual Studio and Visual Studio Code are different products with separate release cadences and, increasingly, separate feature sets, something our explainer on setting up VS Code's extensions and AI features walks through in more detail.

The new LTSC 18.11 channel, for holdouts

The same day it shipped 18.12, Microsoft also opened a new Visual Studio 2026 LTSC 18.11 channel — a long-term servicing option, not a separate product. According to the announcement, it "includes the full feature set, capabilities, and fixes as Visual Studio 2026 18.0 through 18.10," ships with long-term-support toolsets for .NET 10 and MSVC 14.50/14.52, and is supported for two years, through November 14, 2028 — longer than the one year Microsoft had previously announced for LTSC support, a change Microsoft says came directly from customer feedback that a single year "did not leave enough time to validate and deploy a release."

Existing Visual Studio 2026 Enterprise, Professional, and Build Tools license keys work on both the Stable and LTSC 18.11 channels. LTSC installs receive security and other critical fixes only, not regular feature updates, so staying supported means keeping up with LTSC servicing releases. One caveat worth testing before you rely on it: Microsoft's release notes say Live Share extensions get disabled specifically from version 18.11.3 onward, while the LTSC channel is documented as carrying the 18.0–18.10 feature set — Microsoft hasn't spelled out, in the sources reviewed for this article, whether LTSC's own security servicing will carry forward that same Live Share disablement. Teams that specifically need Live Share to keep functioning should verify current behavior on their exact LTSC build rather than assume either outcome.

Other features shipping in 18.12

Live Share's removal is the headline for search traffic, but it's one line in a release that also adds several Copilot- and debugging-focused features, per the official release notes:

It's the latest in a steady monthly cadence of changes to the IDE; the October update, for instance, focused on C++23 IntelliSense improvements rather than collaboration tooling. The AGENTS.md addition in particular continues a wider industry push toward a shared, tool-agnostic instructions file for AI coding agents, a trend also visible in recent Visual Studio Code Copilot updates we covered in our rundown of VS Code 1.146's inbox mode and Copilot changes.

What's next

For most Visual Studio 2026 users on the Stable channel, there's no action required beyond knowing Live Share is gone — updating to 18.12 simply removes an already-disabled extension rather than breaking something that was working. Teams that depend on real-time pairing inside Visual Studio need to pick a substitute now, using Microsoft's own shortlist as a starting point, and teams specifically trying to preserve current Live Share behavior should test the new LTSC 18.11 channel directly rather than assume it's unaffected. Microsoft has not said whether Live Share could return in a different form, and a commenter's question about a future "Visual Studio 2027" annual release got only a noncommittal reply from Microsoft's own team: "We do not have anything to share about annual releases at this time, we will circle back with an update when we do." For now, watch the official release notes for both the Stable and LTSC channels for any further word.

Written byFelix Moreau

Felix Moreau writes Pandromeda's software coverage and how-to guides. He covers Windows, macOS and Linux updates, the apps people rely on, emulators and developer tools, and turns official documentation into clear, numbered steps that work on the current version.

More from Felix MoreauAll Software & Guides coverage