System became unbootable after attempting to enable WSL on Windows 11

### Windows Version

Microsoft Windows [version 10.0.26200.8457]

### WSL Version

2.7.3.0

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

- [x] WSL 2
- [ ] WSL 1

### Kernel Version

6.6.114.1-1

### Distro Version

_No response_

### Other Software

I attempted to enable Windows Subsystem for Linux on my machine.

Windows installed WSL and requested a restart. After rebooting, the system failed to boot and entered Automatic Repair.

Automatic Repair was unable to recover the machine and eventually reported an error referencing SrtTrail.txt.

The recovery log only contained cloud remediation entries and no meaningful repair action appeared to be performed.

The system could only be recovered by booting from Windows installation media and running:

dism /image:D:\ /cleanup-image /revertpendingactions

After running this command and rebooting, Windows started normally again.

I waited approximately 24 hours, confirmed the system was healthy (SFC and DISM checks passed), and attempted to enable the WSL-related feature again.

After the next reboot, the same boot failure occurred again and the same recovery procedure was required.

Hardware
ASUS TUF Gaming X570-Plus WiFi
AMD Ryzen 9
32 GB RAM
Samsung 970 EVO 1TB (system drive)
Crucial P3 Plus 2TB
System History

This machine was originally installed with Windows 10 and later upgraded to Windows 11.

The machine had been operating normally before attempting to enable WSL.

Recovery Results

After recovery:

Windows booted normally.
SFC reported no integrity violations.
DISM RestoreHealth completed successfully.
SSD health status was reported as healthy.
Multiple subsequent reboots completed successfully.
Additional Information

After recovery, wsl --version still reported WSL as installed.

However, the following Windows optional features were disabled:

Microsoft-Windows-Subsystem-Linux
VirtualMachinePlatform

which suggests that the activation of these components was rolled back during recovery.

CBS Log Entries

CBS.log contains entries similar to:

CBS_E_INVALID_PACKAGE (0x800f0805)

related to:

Package_for_KB3025096~31bf3856ad364e35~amd64~~6.4.1.0

and

Package_for_KB3025096~31bf3856ad364e35~x86~~6.4.1.0

### Repro Steps

Attempted to enable Windows Subsystem for Linux (WSL).
Windows installed the required components and requested a reboot.
Rebooted the system.
Windows failed to boot and entered Automatic Repair.
Automatic Repair was unable to recover the system.

The system was recovered by booting from Windows installation media and running:

dism /image:D:\ /cleanup-image /revertpendingactions

### Expected Behavior

Enabling Windows Subsystem for Linux should complete successfully after reboot.

If activation cannot be completed, Windows should either rollback the change automatically or provide a recovery path that does not leave the system unable to boot.

Automatic Repair should also be able to recover from this situation without requiring manual DISM commands from Windows Recovery Environment.

### Actual Behavior

After enabling WSL and rebooting, Windows failed to boot and entered Automatic Repair.

Automatic Repair was unable to recover the system and referenced SrtTrail.txt.

The system could only be recovered by booting from Windows installation media and running:

dism /image:D:\ /cleanup-image /revertpendingactions

After this command, Windows booted normally again.

### Diagnostic Logs

_No response_

Start by reviewing CBS.log and SrtTrail.txt around an attempted WSL feature enablement and reboot, using the reported DISM /image:D:\ /cleanup-image /revertpendingactions recovery as context. Confirm the failure and determine whether enabling WSL can complete safely or roll back without leaving Windows unbootable.

Written by the indexing model from the issue text.