Cleaner Professional: 7.8.1414.0
Grok gave me a little report about why my WSL service was being disabled:
Full Data Field
Impact:197379:TUID:M64\{14EDF950-06B9-415F-862C-1D5DEC321AE6}:origStartType:2:origState:4:serviceName:WSLService
| Item | Detail |
|---|---|
| TUID in disable record | {14EDF950-06B9-415F-862C-1D5DEC321AE6} |
| CCleaner UI label | Microsoft GameInput (not WSL) |
| WSL mapping TUID | M64:{ABAA998A-FDCF-48DC-9174-DC711BD2B5D1} → service:WSLService |
Additional findings explain the mismatch:
• wslg.exe and wslsettings.exe are incorrectly registered under the GameInput TUID in DebuggerRegistration.
• Microsoft GameInput was installed June 21, 2026 — the same day WSL was first disabled.
• ProgramToEntriesMapping row 436 links the WSL TUID to service:WSLService.
• CCleanerPOCache.db contains MSI cache entries for “Windows Subsystem for Linux”.