Background update via MSI/Store (version 2.7.12.0) breaks WSL auto start

Nobody has claimed this yet.

### Windows Version

Microsoft Windows [Version 10.0.19045.7663]

### WSL Version

2.7.12.0

### Are you using WSL 1 or WSL 2?

- [x] WSL 2
- [x] WSL 1

### Kernel Version

Linux version 4.4.0-19041-Microsoft (Microsoft@Microsoft.com) (gcc version 5.4.0 (GCC) ) #7663-Microsoft Sat Aug 08 10:24:00 PST 2026

### Distro Version

Debian

### Other Software

WBS script for the WSL autostart "start_invisible.vbs" called via "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run"

### Repro Steps

1. Have an active WSL session running background processes (managed via VBScript or Startup Registry "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run").
2. Windows Update / Windows Store triggers a silent background update of the WSL subsystem (specifically upgrading to version 2.7.12.0 via "wsl.msi" / AppX bundle).
3. The "RestartManager" attempts to restart "wsl.exe" and "wslhost.exe" to apply files but encounters a security/session lock.
4. The system attempts to run a startup VBScript calling "wsl.exe" right after login or during this event.

- the user is not notified why his WSL tools are currently offline,
- the user is not asked to reboot the PC or restart the service.

### Expected Behavior

The update installer should safely defer the update until system shutdown, or notify the user via a standard Windows Action Center GUI notification that WSL has been updated and a machine restart is required to use Linux applications again.

### Actual Behavior

The update silently bricks the WSL subsystem. All commands (`wsl -l -v`) report the distros as `Stopped` and subsequent execution attempts fail silently or crash. No user-facing warning is shown, making the application stack look broken to end-users (in our case, automated car service workstations) until a manual machine reboot is performed.

### Diagnostic Logs

Event Viewer captured the following entries during the failure:
- **MsiInstaller:** Windows Installer started transaction: `C:\Program Files\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_2.7.12.0_x64__8wekyb3d8bbwe\wsl.msi`. Client Process ID: 8616.
- **RestartManager:** Application 'C:\Program Files\WSL\wsl.exe' (pid 9896) cannot be restarted - Application SID does not match Conductor SID.
- **RestartManager:** Application 'C:\Program Files\WSL\wslhost.exe' (pid 10548) cannot be restarted - Application SID does not match Conductor SID.
- **RestartManager:** Machine restart is required.

[20082026_WSL_UPDATE_LOGS.zip](https://github.com/user-attachments/files/31251309/20082026_WSL_UPDATE_LOGS.zip)

Start by reviewing the wsl.msi/AppX update path and the RestartManager entries for wsl.exe and wslhost.exe in the attached Event Viewer logs. Reproduce the update while a WSL session and HKCU Run VBScript are active. Done means the update safely defers or clearly notifies the user when a machine restart is required, without silently leaving distributions unusable.

Written by the indexing model from the issue text.