A Windows desktop shows app management and File Explorer windows alongside a terminal running winget and PowerShell.
Some Windows apps won't uninstall from Settings. Before you reach for PowerShell, it helps to know which kind of app you're dealing with. Windows has three broad categories: classic desktop programs, packaged apps (Appx/MSIX), and protected system components. Each has its own removal route and its own limits. MakeUseOf recently published a walkthrough of removing these apps. Several of its commands and claims don't match Microsoft's documentation, so this guide corrects them.

A Windows desktop shows app management and File Explorer windows alongside a terminal running winget and PowerShell. Start with the boring options​

Microsoft's own documentation says you can uninstall through Start > Settings > Apps, then find the app and select More > Uninstall. That is the first thing to try.

Microsoft Support also covers the case where Settings fails. Some apps can't be uninstalled from Settings right now, and Microsoft says to use Control Panel for those. It also says some apps are built into Windows and can't be uninstalled at all.

Control Panel steps (Windows 10 and 11):

  1. Search for Control Panel on the taskbar and open it.
  2. Select Programs > Programs and Features.
  3. Right-click the program and choose Uninstall or Uninstall/Change.
  4. Follow the on-screen prompts.

This is where trial-version security suites and similar traditional desktop programs usually go quietly.

If the uninstall errors out, Microsoft's troubleshooting page for Windows 11 suggests this order:

  • Restart the PC.
  • Repair or reset the app under Settings > Apps > Installed apps > Advanced options, if the app offers those options.
  • Try uninstalling from Settings again.
  • Follow any troubleshooter Windows recommends.

Not every desktop app supports repair or reset. If you suspect the app is malware, scan with Windows Security and remove the app only after the threats are cleaned. Microsoft's last resorts are contacting the app publisher or using Reset this PC (keep your files).

Microsoft's downloadable Program Install and Uninstall troubleshooter is documented for Windows 10. That version of Windows reached end of support on October 14, 2025. Don't treat the troubleshooter as a Windows 11 cure-all.

Use winget for desktop apps​

winget is the next step when Control Panel doesn't list the app. Microsoft describes the uninstall command as one that uninstalls the specified application. The winget list command shows more than just apps installed with winget, so you can use it to find a program that came from somewhere else.

A safe sequence:

Code:
winget list
winget uninstall --id <App.ID> --exact

Replace the placeholder with the ID shown in the list. The command needs an exact app name, and if there is any ambiguity, winget prompts you to narrow it down. Using --id with --exact avoids removing the wrong thing.

If you hit a Microsoft Store agreement prompt, adding --source winget to the command avoids it. For example:

winget uninstall "App Name" --source winget

Two corrections to the MakeUseOf version:

  • It tells readers to launch winget by typing winget on its own, as an administrator. That isn't part of the documented uninstall syntax, and you don't need it. Open a terminal and run the commands above. Elevate only if a particular uninstaller demands it.
  • It calls winget "the best tool" for third-party apps and says it always uses the app's own installer. I couldn't confirm either claim in Microsoft's documentation.

winget also isn't a bypass for protected components. It can only run the removal path the app has registered. Its reliability varies too. A GitHub issue on the winget project describes a case where winget reported a successful uninstall of an MSIX package that was still present. That's one reported bug, not proof of a widespread problem. It does suggest running winget list again afterward to confirm the app is really gone.

Packaged apps: check before you remove​

Windows apps from the Store and many built-in apps are packages. Remove-AppxPackage removes an app package from a user account, and packages have an .msix or .appx extension. Microsoft's guidance for IT pros is more careful than most blog posts.

Step 1: Identify the package.

Get-AppxPackage -Name <App_name>

If this returns output, the app is registered for your account.

Step 2: Check the NonRemovable attribute. Microsoft says certain packages, such as system apps, can't be removed. Look at the NonRemovable value in the output and don't proceed if it is True.

Step 3: Remove it for your account.

Remove-AppxPackage -Package '<package_name>'

Step 4 (optional): Remove it for every user. Add -AllUsers, which requires administrator permission:

Remove-AppxPackage -Package '<package_name>' -AllUsers

Microsoft warns that removing an Appx package can be irreversible, so make sure you have the right user context and the right package. It also says removing the Microsoft Store app is not supported. MakeUseOf's author reaches a similar conclusion about leaving Store and shell components alone.

Two cautions about the wildcard example​

MakeUseOf's example uses a wildcard to remove Phone Link: Get-AppxPackage *PhoneLink* | Remove-AppxPackage. Microsoft's documentation doesn't show that pattern. If you try it, run the Get-AppxPackage half first and confirm it matches only the package you want. Microsoft's own examples use a specific package name.

Provisioning: new users only​

The MakeUseOf piece suggests removing the provisioned package so Windows doesn't reinstall the app for new accounts. That is a real step, but it is easy to misunderstand. Microsoft's DISM documentation says removing provisioning means app packages won't be registered to new user accounts. It also says the option will only remove provisioning when the package is registered to a user profile. You then need Remove-AppxPackage to remove the app for each user who already has it.

In practice:

  • Removing the app for existing users is done with Remove-AppxPackage, using -AllUsers if appropriate.
  • Stopping it from appearing for new accounts is done by removing the provisioned package. Look up the exact display name first with Get-AppxProvisionedPackage -Online.

The source article's provisioning example targets Xbox Gaming Overlay while its preceding example targets Phone Link, so the two steps don't belong together. Don't paste them as one sequence.

Claims I'd leave out​

Some claims in the original lacked support in the Microsoft documentation I checked:

  • That Edge is protected because Widgets and Copilot depend on it, and that it is removable in the EEA.
  • That manufacturers preload apps for a share of partner revenue.
  • That idle apps consume meaningful RAM.
  • That leftover registry keys and cache conflict with reinstalls.

Some of these may be true, but I wouldn't build a how-to on them. I'd especially avoid the advice to delete registry keys under HKEY_LOCAL_MACHINE\SOFTWARE by hand as routine cleanup. Manual registry deletion is the riskiest step in the whole guide, and the benefit is unproven.

Practical checklist​

  • Try Settings, then Control Panel, then winget, in that order, for desktop programs.
  • Use PowerShell Appx commands only for packaged apps, and check NonRemovable first.
  • Create a restore point before removing anything built in. This is sensible general advice, not something Microsoft's removal pages require.
  • Be wary of OEM utilities that control firmware, drivers or hardware features. Nothing I reviewed shows that removing them is harmless.
  • Verify the result by running winget list or Get-AppxPackage again.

The short version is that the greyed-out Uninstall button usually has a reason. Control Panel and winget handle most stubborn desktop programs. For built-in apps, PowerShell works only when Windows allows the package to be removed, and Windows draws that line on purpose.

 

References

  1. This is how you uninstall apps that Windows Settings won't let you MakeUseOf 2026-10-31T13:16:17+00:00
  2. Uninstall or remove apps and programs in Windows | Microsoft Support support.microsoft.com
  3. `uninstall` Command | Microsoft Learn learn.microsoft.com