Tool · Runs in your browser
Log reader
Win11Debloat writes everything it prints to a log file, and ends a run that had trouble with only “See output above for details.” Paste the log here and see which steps ran, what failed, and why, matched against our troubleshooting catalog. It works with release 2026.08.24 and the releases around it.
Where to find the log: in the wizard, ☰ → Logs. Or open Logs\Win11Debloat.log next to the script, or %TEMP%\Win11Debloat\Logs\Win11Debloat.log if you used the one-liner. You can also paste the text from the Win11Debloat window. From the release after 2026.08.24, logs move to %LOCALAPPDATA%\Win11Debloat\Logs.
What stays private
The log is read in your browser and never sent anywhere. It does contain your PC's name and your user name, so think before you paste it into a public issue or forum: replace them with something neutral first.
Reading a log yourself
- Each run starts with a header of asterisks and Windows PowerShell transcript start. Win11Debloat adds every run to the same file, so the newest run is at the bottom.
- Lines starting with
>are the steps: the registry backup, the restore point, app removal and each tweak. - Problems show up as lines starting with
Error:,WARNING:orUnable to, and a run with failures ends with N app removal(s) failed or N feature change(s) failed. - Harmless lines: Scheduled Task … not found or is already disabled mean that telemetry task was already off. Unable to find Store app database … creating it now is expected the first time.
- WinGet timeouts only show up with
-Verbose. Without it you see Unable to uninstall … via WinGet.
For deployments, the log matters more than the exit code: see automation.
Keep going
Something wrong or out of date? Email hello@win11debloat.dev and we will fix it.