Repository navigation
Description
Windows Version
10.0.26300.9457
WSL Version
3.0.5.0
Are you using WSL 1, WSL 2, or WSLC?
- WSL 2
- WSL 1
- WSLC
Kernel Version
6.18.58.1-1
Distro Version
Ubuntu 24.04.5 LTS
Other Software
Windows Subsystem for Linux 3.0.5.0 (x64)
wsl --version
WSL-Version: 3.0.5.0
Kernelversion: 6.18.58.1-1
WSLg-Version: 1.0.79
MSRDC-Version: 1.2.7391
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.26100.1-240331-1435.ge-release
Windows-Version: 10.0.26300.9457- Docker Engine and containerd running inside WSL2
- systemd-managed services
- Long-running Linux processes
Repro Steps
On November 2026, Windows Update automatically installed Windows Subsystem for Linux 3.0.5.0 (x64) while my WSL2 environment was actively running.
The update terminated my running Linux distributions without any warning, confirmation prompt, or user consent. This interrupted running services and caused loss of in-progress work.
The incident was confirmed by correlating Windows Event Viewer, Windows Update history, and the persistent Linux system journal.
Environment and conditions:
- Keep WSL2 distributions running continuously with active processes such as systemd services, and Docker containers.
- Enable automatic Windows Updates, including security and application updates.
- Configure Windows to prevent automatic system restarts. Updates requiring a reboot should remain pending until a user-initiated restart.
- Leave the WSL2 environment running while Windows Update automatically installs a new WSL package.
- Observe that the WSL2 update terminates all active Linux distributions also Docker Desktop even though Windows itself remains running.
Observed timeline (November 11, 2026, CET / UTC+01:00):
| Time | Event |
|---|---|
| 1 | Windows Update begins installing Windows Subsystem for Linux 3.0.5.0 (x64). |
| 2 | Service Control Manager, Event ID 7040: WSL Service startup type changes from Automatic to Disabled. |
| 3 | WSL forcibly powers off the running Docker Desktop Linux instance after the graceful shutdown exceeds the 10-second timeout. |
| 4 | WSL forcibly powers off the running Ubuntu instance after the graceful shutdown exceeds the 10-second timeout. |
| 5 | Service Control Manager, Event ID 7045: WSL Service is installed again. |
| 6 | Windows Update reports successful installation of WSL 3.0.5.0. |
| 7 | A new WSL2 Linux kernel boot begins. |
Windows Update details:
| Property | Value |
|---|---|
| Update | Windows Subsystem for Linux 3.0.5.0 (x64) |
| Update orchestrator | MoUpdateOrchestrator |
| Installation result | Successful |
| Update ID | 2de349cd-24eb-4744-acfe-83ee05ec01e2 |
The Windows Update history confirms this was an automatically initiated update. I did not manually request a WSL upgrade, restart the distributions, or authorize a maintenance interruption.
The Windows host itself did not reboot during this incident.
This is an observed incident associated with a particular automatic update. I have not deliberately repeated the destructive update procedure.
Expected Behavior
Automatic WSL updates must never terminate actively running Linux distributions without explicit user consent.
- Detect whether any WSL2 distributions, processes, or containers are still running before installing an update that requires terminating WSL2.
- If WSL2 is active, automatically download and stage the update but defer its installation until a user-approved maintenance window or an appropriate user-initiated restart.
- Never forcibly terminate active distributions merely to complete an unattended background update.
- Provide an explicit opt-in mechanism if an immediate update requires interrupting active workloads.
- Honor existing Windows Update policies intended to prevent unattended operational interruptions.
- Allow Windows security updates to continue normally without requiring users to disable automatic updates globally.
- Preserve running services and data integrity when an update cannot be applied without downtime.
A WSL2 update that requires stopping active Linux workloads should be treated as a disruptive system maintenance operation, even when the Windows host itself does not need to reboot.
Previous proposals to request user consent or defer upgrades while WSL is active have been closed without resolving this observed scenario.
Please provide a supported, reliable mechanism that allows WSL updates to be downloaded and staged automatically but prevents installation from interrupting active distributions until an explicit user-approved maintenance window.
Can the WSL installer and Windows Update integration be changed to detect running workloads and defer disruptive updates instead of forcibly shutting them down?
WSL2 is frequently used as a persistent development environment, container runtime, and server platform. Active distributions may contain long-running build processes, databases, Docker containers, network services, or other stateful workloads.
Actual Behavior
Windows Update silently terminated actively running WSL2 distributions while installing WSL 3.0.5.0.
The update process:
- Disabled the existing WSL Service.
- Initiated shutdown of active Linux distributions.
- Waited only 10 seconds for the shutdown operation to complete.
- Issued forced power-off operations when the distributions did not terminate within that timeout.
- Reinstalled the WSL Service and completed the update successfully.
- Did not request the user's permission or provide an opportunity to postpone the interruption.
The affected distributions were running workloads at the time of the update.
This caused an unexpected outage of my WSL and loss of in-progress work.
The impact is particularly serious for Docker workloads, databases, persistent services, and long-running computations. Even if the Linux filesystems recover successfully, forcibly terminating running processes can destroy unsaved application state and interrupt active transactions.
The configured Windows policy preventing automatic host restarts did not protect these workloads because the WSL update interrupted the Linux environment without restarting Windows.
This makes WSL2 unsuitable for workloads requiring predictable uptime unless unattended updates can be reliably deferred while WSL is active.
I want to keep WSL and Windows fully updated, including security fixes. However, installation of an update that requires stopping the Linux environment must be scheduled or explicitly authorized.
Diagnostic Logs
Update Windows Subsystem for Linux 3.0.5.0 (x64)
Installationprogram MoUpdateOrchestrator
Update-ID 2de349cd-24eb-4744-acfe-83ee05ec01e2Linux system journal
Persistent journal entries from the previous WSL2 boot:
WSL (2 - init-systemd()) ERROR:
InitTerminateInstanceInternal:2901:
systemctl poweroff did not terminate the instance
in 10000 ms, calling reboot(RB_POWER_OFF)
WSL (2 - init-systemd(Ubuntu)) ERROR:
InitTerminateInstanceInternal:2901:
systemctl poweroff did not terminate the instance
in 10000 ms, calling reboot(RB_POWER_OFF)
These entries establish that WSL explicitly attempted to terminate both distributions and escalated to forced power-off after the shutdown timeout.
Windows Event Viewer
System log, Service Control Manager:
Event ID: 7040
The start type of the WSL Service was changed
from Automatic to Disabled.
Event ID: 7045
Service installed: WSL Service
Executable: C:\Program Files\WSL\wslservice.exe
Startup type: Automatic
Account: LocalSystem
Windows Update Client:
Event ID: 43
Installation started:
Windows Subsystem for Linux 3.0.5.0 (x64)
Event ID: 19
Installation successful:
Windows Subsystem for Linux 3.0.5.0 (x64)
The installed wslservice.exe product version was independently verified as 3.0.5.0.
Linux boot history
The previous Linux boot ended during the automatic WSL upgrade, and a new kernel boot began approximately 72 seconds later.
Related reports and prior proposed fixes
- Ask for user consent if wsl is active during store updates. #40786
- Defer MSI upgrades while WSL is active #41447
- WSL2 shut down without warning while I was using it, because Windows Store began to update it #8169
- Forced store updates crashes WSL processes #12204
- Background update via MSI/Store (version 2.7.12.0) breaks WSL auto start #41394
- WSL 2.7.1.0 pre-release update forces system restart via msiexec without user consent, then fails with unhelpful ERROR_FILE_NOT_FOUND when HypervisorPlatform is not enabled #14536
Activity
github-actions commentedon Nov 11, 2026
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use
.\collect-wsl-logs.ps1 -LogProfile networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce completed please upload the output files to this GitHub issue.
See Collect WSL logs (recommended method).
If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.
[-][WSL2] Automatic Windows Update to 3.0.5.0 forcibly shuts down active distributions without user consent, causing data loss[/-][+]Automatic Windows Update to 3.0.5.0 forcibly shuts down active distributions without user consent, causing data loss[/+]github-actions commentedon Nov 11, 2026
Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done.
If this is a networking issue, please use
.\collect-wsl-logs.ps1 -LogProfile networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce completed please upload the output files to this GitHub issue.
See Collect WSL logs (recommended method).
If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.