Windows desktop: stealth auto-update stops Code sessions and doesn't restart them, so they drop off Remote Control #109193

What happens

On Windows (Microsoft Store/MSIX build), when the PC has been idle the app installs an update and relaunches itself. It stops the running Code sessions before quitting. After the relaunch those sessions appear in the sidebar but aren't running, so Remote Control isn't connected to them. From my phone or laptop the sessions don't appear at all. They only come back once each one is opened on the PC.

Expected

Sessions that had Remote Control on before the update should be running and connected again after the relaunch.

Setup

• Windows desktop app, MSIX/Store build. Updated from 4.23118.1 to 5.1231.2.
• "Connect new sessions to Remote Control" on, and "Keep computer awake while Claude works" on.
• The PC never sleeps or hibernates (checked with powercfg and the event log). It's locked but awake, with a working network the whole time.

Log (main.log)

11:43:53 [stealth-update] Triggering stealth update after idle timeout
11:43:53 [CCD] Stopping 2 active session(s) on quit
11:43:55 beforeQuitForUpdate handler fired, going down for update
11:44:30 [updater] Version changed since last launch: 4.23118.1 → 5.1231.2
11:44:32 [LocalSessionManager] Initialization succeeded … existingSessions=0
(no [remote-control] bridge_state lines until a session is opened at 19:55)
19:55:39 [CCD] Replayed 1 session permission update(s) for <session>
19:55:43 [remote-control] bridge_state: "connected"
19:18:12 [CCD start-timing] … resume=app_relaunch/28507s

Impact

I run long-lived coordinator sessions on this PC and reach them from home through Remote Control. After any idle update they can't be reached until I'm back at the PC.