win11debloat.dev
2026.08.24

Help · Troubleshooting

Win11Debloat troubleshooting

Paste the message you see, or describe the problem, and the matching fix appears. Each message below is copied from Win11Debloat 2026.08.24's source code, so we can say exactly when it appears and why. We saw several of them in our own test runs. Problems users have reported but nobody has traced to Win11Debloat are labelled as unconfirmed.

Checked against Win11Debloat 2026.08.24Updated 2 min read
On this page 9 sections
  1. What do you see?
  2. First, three quick checks
  3. It will not start
  4. Messages while it runs
  5. App removal
  6. Problems afterwards
  7. Scripts, Intune and other users
  8. Other side effects people report
  9. Reporting a new problem
?

What do you see?

Paste the error text from the PowerShell window or the dialog, or type a few words such as “search not working”.

First, three quick checks

  1. Read the red lines. Win11Debloat keeps going when one step fails and only summarizes at the end. The PowerShell window behind the wizard, or Logs\Win11Debloat.log (☰ → Logs), names the step. The log reader picks them out for you.
  2. Restart. Policies, services and some tweaks only take full effect after a restart, and Explorer may still be running with old settings.
  3. Check you have the current release. The one-liner always gets 2026.08.24. An old downloaded copy may have bugs that are already fixed: the Get-Acl error from PowerShell 7, for example, was fixed in 2026.03.09.

It will not start

“PowerShell execution is restricted by security policies”
Win11Debloat is unable to run on your system, PowerShell execution is restricted by security policies

Why

PowerShell is running in Constrained Language Mode, which is how AppLocker or Windows Defender Application Control lock down work and school PCs. Win11Debloat checks for this and stops.

Fix

There is no safe way around it: the restriction comes from whoever manages the PC. On a work or school device, ask your IT department. On a personal PC, run $ExecutionContext.SessionState.LanguageMode in PowerShell. If it does not say FullLanguage, some security software or policy has locked it down.

Source: Scripts/Get.ps1, Win11Debloat.ps1 in 2026.08.24

“Unable to fetch required files from GitHub”
Unable to fetch required files from GitHub. Please check your internet connection and try again.

Why

The one-liner could not download the release from GitHub. Usually a firewall, proxy, VPN or DNS filter blocks api.github.com or codeload.github.com, or the GitHub API rate limit was hit.

Fix

Open https://github.com/Raphire/Win11Debloat/releases/latest in a browser. If it loads, download Source code (zip), extract it and run Run.bat instead. If several people share your internet connection, wait an hour and try again.

Source: Scripts/Get.ps1 in 2026.08.24

“Win11Debloat requires Windows PowerShell 5.1”
Win11Debloat requires Windows PowerShell 5.1, but it is running under PowerShellApp removal and system restore points rely on modules that are not available in PowerShell 7

Why

You ran Win11Debloat.ps1 directly in PowerShell 7 (pwsh). Its app removal and restore point commands only work in Windows PowerShell 5.1, which comes with Windows.

Fix

Open Windows PowerShell (not PowerShell 7) and run it again. The one-liner already does this for you: from PowerShell 7 it starts the script in Windows PowerShell.

Source: Win11Debloat.ps1 in 2026.08.24 · Project issues: #675

“Win11Debloat must be run as Administrator”
Win11Debloat must be run as Administrator.Restart as Administrator? (y/n)

Why

The script was started without administrator rights.

Fix

Type y and accept the Windows prompt. If no prompt appears, or your account is not an administrator, sign in with an administrator account.

Source: Win11Debloat.ps1 in 2026.08.24

“Running scripts is disabled on this system”
cannot be loaded because running scripts is disabled on this system

Why

PowerShell's execution policy blocks .ps1 files. This only happens when you run Win11Debloat.ps1 directly. The one-liner and Run.bat are not affected.

Fix

Run this first, in the same window. It only applies to that window:

Set-ExecutionPolicy Bypass -Scope Process -Force

Or use the one-liner or Run.bat.

Source: PowerShell itself in 2026.08.24

Run.bat flashes and closes

Why

Run.bat starts PowerShell and asks for administrator rights in a new window. If that fails, for example because you declined the prompt or PowerShell is blocked, the window closes without explanation.

Fix

Read Logs\Win11Debloat-Run.log in the extracted folder, which says what it tried. Or open PowerShell as administrator and run the script directly, as the project's own README suggests: how.

Source: Run.bat in 2026.08.24

“Unable to find required files”
Win11Debloat is unable to find required files, please ensure all script files are present

Why

Some of the release's files are missing, usually because the script was run from inside the ZIP, or an antivirus quarantined part of it.

Fix

Right-click the ZIP, choose Extract All, and run Run.bat from the extracted folder. If files keep disappearing, check your antivirus quarantine.

Source: Win11Debloat.ps1 in 2026.08.24

“The graphical interface could not start”
The graphical interface could not start:Press any key to continue in CLI mode...

Why

The wizard failed to load, for example on a stripped-down Windows install or a remote session without the required .NET components.

Fix

Press a key to use the text menu instead. It has Default mode, app removal and your last used settings. For everything else, use command-line switches.

Source: Win11Debloat.ps1 in 2026.08.24

Messages while it runs

“WinGet is not installed or outdated”seen in our tests
WinGet is not installed or outdated, this may prevent Win11Debloat from removing certain appsPress any key to continue anyway...

Why

Win11Debloat could not find the winget command. It only needs it for three apps: Copilot, Edge and OneDrive. Everything else works without it.

Fix

Press a key to continue, or install WinGet first: open the Microsoft Store, search for App Installer and install or update it. Then open a new PowerShell window and check that winget --version works.

Source: Win11Debloat.ps1 in 2026.08.24

“Restore Point Creation Failed”seen in our tests
Failed to create a system restore point. Do you want to continue without a restore point?Warning: Continuing without restore point

Why

Windows could not create a restore point. Win11Debloat already tries to turn System Protection on for drive C: if it is off, so this usually means System Restore is unavailable (as on Windows Server) or blocked by policy.

Fix

Yes continues without one. The registry backup is still made, so tweaks can still be undone. No cancels the whole run, and nothing is changed. With -Silent it continues without asking.

Source: Scripts/Features/Invoke-SystemRestorePoint.ps1 in 2026.08.24

“Changes Applied with Errors”seen in our tests
Changes Applied with Errorschange(s) failed. See console for details.feature change(s) failed. See output above for details.app removal(s) failed. See output above for details.

Why

At least one step failed, and every other step was still applied. In our tests the failures were the restore point on Windows Server and the WinGet-based Copilot removal on a PC without WinGet.

Fix

Scroll up in the PowerShell window behind the wizard for the red lines, or open Logs\Win11Debloat.log (☰ → Logs). Fix the cause, then run the same settings again: steps that already worked are simply applied again.

Source: Scripts/GUI/Show-ApplyModal.ps1 in 2026.08.24

“This machine is domain-joined”
This machine is domain-joined. Group Policy may override changes made by Win11Debloat.

Why

The PC is managed by an organization. Its Group Policy is reapplied regularly and can undo or block what Win11Debloat changes.

Fix

This is a warning, not an error. On a work PC, check with your IT department before running a debloater at all.

Source: Win11Debloat.ps1 in 2026.08.24

“Unable to restart Windows Explorer”
Unable to restart Windows Explorer process, please manually reboot your PC to apply all changes

Why

Win11Debloat could not restart Explorer, which it normally does so that taskbar and Start changes appear at once.

Fix

Sign out and back in, or restart. If the taskbar has disappeared, press Ctrl + Shift + Esc, choose Run new task, type explorer and press Enter.

Source: Scripts/Features/Invoke-RestartExplorer.ps1 in 2026.08.24

“requires a reboot to take full effect”
requires a reboot to take full effect

Why

Six tweaks only take full effect after a restart: mouse acceleration, Sticky Keys, window snapping, animations, Windows Sandbox and WSL.

Fix

Restart when it suits you. Nothing is wrong.

Source: Scripts/Features/Invoke-RestartExplorer.ps1 in 2026.08.24

“Script execution was cancelled by the user”
Script execution was cancelled by the user. Any remaining changes were not applied.

Why

The run was stopped part-way: you clicked cancel, answered No to the restore point question, or closed the window.

Fix

Steps before the cancel were applied, later ones were not. Run it again with the same settings to finish, or undo what was applied.

Source: Win11Debloat.ps1 in 2026.08.24

App removal

“WinGet is either not installed or is outdated; … could not be removed”seen in our tests
WinGet is either not installed or is outdated;could not be removed

Why

One of the three WinGet-based apps (Copilot XP9CXNGPPJ97XX, Edge, OneDrive) could not be removed because winget is missing. We saw exactly this for Copilot on our Windows 11 test machine.

Fix

Install or update App Installer from the Microsoft Store, then run Win11Debloat again with just that app, or uninstall it from Settings → Apps → Installed apps.

Source: Scripts/AppRemoval in 2026.08.24

“Removal of app … is not supported and will be skipped”
is not supported and will be skipped

Why

A name in -Apps is not in Win11Debloat's list of 141 apps, usually a typo or a display name instead of a package name.

Fix

Use package names such as Microsoft.BingNews. Look them up in the app list or with the app checker.

Source: Scripts/FileIO/Get-ValidatedAppList.ps1 in 2026.08.24

“Unable to uninstall Microsoft Edge via WinGet. Would you like to forcefully uninstall it?”
Unable to uninstall Microsoft Edge via WinGet. Would you like to forcefully uninstall it? NOT RECOMMENDED!

Why

The normal Edge removal through WinGet failed, which is common: Microsoft blocks uninstalling Edge in most regions.

Fix

Answer No unless you are sure. The forced removal runs Edge's own uninstaller and leaves WebView2 and the updater behind. Windows Sandbox and apps that open web pages through Edge can stop working.

Source: Scripts/AppRemoval in 2026.08.24

“Are you sure that you wish to uninstall the Microsoft Store?”
Are you sure that you wish to uninstall the Microsoft Store? This app cannot easily be reinstalled.

Why

You ticked the Microsoft Store. The wizard asks a second time, because without the Store you cannot reinstall the other apps from it.

Fix

Answer No and untick it, unless you have a reason. Note that the command line and -Silent do not ask this question.

Source: Scripts/Helpers/Confirm-UnsafeAppRemoval.ps1 in 2026.08.24

“Unable to uninstall Microsoft.OneDrive via WinGet”confirmed bug
Unable to uninstall Microsoft.OneDrive via WinGetUnable to uninstall

Why

A confirmed bug. On fresh installs OneDrive is installed for your user only, and newer WinGet versions no longer remove such apps from an administrator session, which is how Win11Debloat runs.

Fix

Uninstall OneDrive yourself: Settings → Apps → Installed apps → Microsoft OneDrive → Uninstall, or run winget uninstall Microsoft.OneDrive in a normal, non-administrator PowerShell and accept the prompt. Your files are not deleted.

A fix is already merged in the project's unreleased code (#802) and should arrive with the next release.

Source: Scripts/AppRemoval in 2026.08.24 · Project issues: #789, #802

“Unable to load list of installed apps via WinGet”confirmed bug
Unable to load list of installed apps via WinGet.

Why

Ticking Only show installed apps asks WinGet for your installed apps. The wizard waits 20 seconds for an answer (the text menu's app picker, 10). On some PCs winget list takes longer, for example the first time, when WinGet still needs you to accept its source agreements.

Fix

Run winget list --accept-source-agreements once in PowerShell, wait for it to finish, then try again. Or untick the option and find your apps in the full list.

Source: Scripts/GUI in 2026.08.24 · Project issues: #535

Problems afterwards

“Some settings are managed by your organization”seen in our tests
Some settings are managed by your organizationYour organization prevents sending diagnostic data to Microsoft

Why

27 tweaks set Group Policy values, and Windows shows this message for any policy. Default mode includes 8 of them, including telemetry, Copilot and Recall. No organization is involved.

Fix

It is harmless. To remove it, undo the policy tweaks: how to undo. Which tweaks cause it.

Source: Regfiles (Policies keys) in 2026.08.24

“You'll need a new app to open this ms-gamingoverlay link”
ms-gamingoverlay

Why

Xbox Game Bar was removed, but Windows still tries to open it when you press Win + G or a controller's Xbox button.

Fix

Apply the -DisableGameBarIntegration tweak, which turns off the integration, or reinstall Xbox Game Bar from the Microsoft Store.

Source: Config/Features.json (DisableGameBarIntegration) in 2026.08.24 · Project issues: #367

Windows troubleshooters do not open

Why

Some built-in troubleshooters need the Get Help app. The project rates it “not recommended” to remove.

Fix

Reinstall Get Help from the Microsoft Store: winget install --id 9PKDZBMV1H3T --source msstore.

Source: Apps.json (Microsoft.GetHelp) in 2026.08.24

Settings changes keep coming back

Why

A management tool, an OEM utility or a major Windows update set them again. On a domain-joined or Intune-managed PC, Group Policy is reapplied on a schedule.

Fix

Run Win11Debloat again with -RunSavedSettings to reapply your last choices. On a managed PC, the organization's policy wins.

Microsoft account, Xbox or Windows Hello sign-in problemsunconfirmed

Why

Reported twice, and neither time traced to Win11Debloat. The maintainer could not find an option that could cause it, and both reports were closed as not reproducible. In one, the user had also removed Edge and WebView2. In the other, Windows' component store was damaged.

Fix

If you removed any of the red “not recommended” apps, reinstall them first, especially Xbox Identity Provider for game sign-in. If Windows Hello or the PIN misbehave, repair Windows: DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow, in an administrator prompt. A DISM repair fixed it for one user.

Project issues: #537, #401

Scripts, Intune and other users

“Win11Debloat is running as the SYSTEM account”
Win11Debloat is running as the SYSTEM account. Use the '-User' or '-Sysprep' parameter to target a specific user.

Why

Intune, SCCM, RMM tools and scheduled tasks often run scripts as SYSTEM, which has no user profile to change.

Fix

Add -User username to change a specific account, or -Sysprep to change the default profile for new accounts.

Source: Scripts/Features/Invoke-Changes.ps1 in 2026.08.24 · Project issues: #310, #851

“Please ensure the user exists on this system”
Something went wrong when trying to find the user directory path for userUnable to find user directory path for user

Why

The name given to -User or -AppRemovalTarget has no profile folder under C:\Users. The account may not exist, or it has never signed in.

Fix

Use the account's folder name as it appears in C:\Users, and sign in with that account once before running Win11Debloat.

Source: Scripts/Helpers/Get-UserDirectory.ps1 in 2026.08.24

“Sysprep mode is not supported on Windows 10”
Win11Debloat Sysprep mode is not supported on Windows 10

Why

-Sysprep only works on Windows 11.

Fix

On Windows 10, run Win11Debloat for each account with -User instead.

Source: Win11Debloat.ps1 in 2026.08.24

“Unable to find LastUsedSettings.json file”
Unable to find LastUsedSettings.json file, no changes were made

Why

-RunSavedSettings needs a previous run on this PC. With the one-liner the file lives in your temp folder, which may have been cleaned up.

Fix

Export your settings from the wizard (☰ → Export config) and use -Config path\to\file.json instead. A config file does not depend on the temp folder.

Source: Win11Debloat.ps1 in 2026.08.24

Other side effects people report

The project's issue tracker also has reports of fullscreen flicker, Realtek audio, webcam and copy-paste problems after running Win11Debloat. Many are labelled unconfirmed or could not be reproduced. If you suspect one, the fastest test is to undo the tweaks you applied (the wizard shows them all with Detect applied tweaks) and see whether the problem goes away. Then reapply them a few at a time. How to undo.

Reporting a new problem

If none of this matches, report it to the project, not to us: ☰ → Report a bug in Win11Debloat, or the issue tracker. Include your Windows version (Win + R, winver), the release you used, which mode or tweaks you chose, and the log file. Search the existing issues first: many problems have a thread already.

If something on this page is wrong or out of date, email the address at the bottom of the page and we will fix it.

Keep going

Something wrong or out of date? Email hello@win11debloat.dev and we will fix it.