VS Code Update Mode: Binary Recovery vs User Data Integrity

Update Mechanism and Data Persistence

Visual Studio Code employs a background update process that separates the application binaries from user-specific configuration and extensions. When an automatic update fails, the system typically reverts to the previous stable binary version to maintain application availability.

Recovery Constraints

While the internal update mechanism handles binary rollbacks, the User Data and Extensions directories remain persistent across these cycles. This design ensures that workspace settings are not lost during a failed installation, but it introduces uncertainty if a version-specific configuration change occurs before the binary update fails.

Depending on the installation method—whether via a standalone installer, %LocalAppData% on Windows, or a system package manager—the recovery path for a corrupted installation varies.

• How does VS Code distinguish between a binary-level failure and corruption within the shared User Data folder during a failed upgrade?
• What is the expected behavior for extensions that have already migrated their internal schemas to a newer version when the application reverts to a previous binary?