Corrupted installation state after partial update failure

VS Code Update Manager

Visual Studio Code employs a background update mechanism that downloads packages to a separate directory before swapping the active installation. While the system is designed to maintain the previous stable version if a download fails, a partial update failure during the swap process can lead to an inconsistent binary state.

When a manual rollback to a previous version is performed following such a failure, the internal cache states may not synchronize automatically with the restored binary version. This creates uncertainty regarding how the application handles cached metadata that was generated by a newer, partially installed version.

• Version assumption: VS Code stable build (User Installer)
• Verification: Inspection of the installation directory for residual pending update folders

Does the update manager provide a mechanism to clear version-specific internal caches during a manual rollback? How does the application ensure cache compatibility when the binary version is downgraded after a failed update attempt?