Simplify VS Code setup caption and fix extension troubleshooting - #189
Merged
guanzhousongmicrosoft merged 1 commit intoSep 24, 2026
Conversation
The caption promised an install prompt that never shows on managed devices, and the guide's recovery steps didn't cover old extension versions, --force, or the reload needed after updating.
guanzhousongmicrosoft
approved these changes
Sep 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
"Set up in VS Code" fails silently or with a confusing error for several groups of users, and the caption promised a prompt that doesn't always come:
No extension gallery service configuredand never starts setup. It fails with VS Code already running too, so the guide's "open the link again once VS Code has loaded" advice was wrong./localfails with "Failed to process URI: A DocumentDB deep-link was opened without a connection string".code --install-extensionover an old version prints "already installed" and doesn't update without--force.Reproduced each with VS Code 1.139 and extension 0.10.0/0.10.2, using VS Code's logs and an isolated user-data dir.
The website can't detect the extension or its version, and a link can't chain install-then-setup, so the homepage keeps one button. The caption now only covers what the button can't: "Don't have VS Code? Download it first." Recovery for the cases above goes in the guide's install and troubleshooting sections, per the earlier review ask to keep troubleshooting off the homepage.