You uninstall an unwanted app from Windows 11.

It disappears.

Problem solved.

Then you restart the computer, install a Windows update, create another user account or set up a replacement PC—and the application is back.

It can feel as though Windows is simply ignoring you.

Usually, something more specific is happening.

Windows applications can be installed or restored through several different mechanisms. Removing an app from your own account does not necessarily remove its provisioning package, stop Microsoft Intune deploying it, prevent an OEM utility installing it or remove an app reference associated with Windows Backup.

So before trying increasingly aggressive PowerShell commands, ask a much better question:

What is actually reinstalling the app?

Once you know that, stopping it becomes much easier.

Why Do Deleted Windows 11 Apps Come Back?

An application can reach a Windows 11 PC through several routes:

• normal desktop installation
• Microsoft Store
• Windows provisioning
• Microsoft Intune or another management platform
• Windows Backup restoration
• manufacturer utilities
• Windows servicing or feature changes
• another application that requires it

And sometimes the application hasn't actually returned at all.

Windows may simply be showing a recommendation, shortcut or placeholder.

These scenarios need different fixes.

If Intune is reinstalling an application, removing a provisioned package won't solve the problem.

If Windows Backup restored an app reference during a new PC setup, editing Intune won't help.

Identify the source before choosing the fix.

First: Is the App Actually Installed?

Before opening PowerShell, confirm that you're dealing with a real installation.

Open:

Settings > Apps > Installed apps

Search for the application.

Also right-click its Start menu entry.

If Uninstall appears, Windows recognises it as an installed application or package that can be removed through that route.

But Start can also display things such as:

• recommendations
• shortcuts
• web links
• recently added applications
• suggested content
• placeholders

If selecting an icon causes Windows to begin downloading the application, what you saw may not have been a complete local installation in the first place.

That distinction can save a lot of unnecessary troubleshooting.

Work Out When It Comes Back

The timing provides an important clue.

It returns immediately or after rebooting:
Look for management software, OEM utilities or another application installing it.

It appears when another user signs in:
Provisioning is a strong possibility.

It appears on a replacement or newly configured personal PC:
Check Windows Backup.

It returns after the company PC checks into Intune:
Check application assignments.

It appears after a major Windows update:
Investigate Windows servicing, provisioning and whether it is a new or replacement Windows component.

Don't repeatedly uninstall the application without noticing when Windows puts it back.

That behaviour is evidence.

Method 1: Uninstall It Normally

Always start with Windows' supported uninstall mechanism.

Go to:

Settings > Apps > Installed apps

Find the application.

Select the three-dot menu and choose:

Uninstall

Many applications can also be removed by right-clicking them in Start and selecting Uninstall.

For an ordinary desktop application, that may be all you need.

Restart Windows and check again.

If it stays gone, stop.

Don't use PowerShell merely because PowerShell exists.

Method 2: Check Windows Backup on Personal PCs

Windows Backup can remember applications associated with a personal Microsoft account and help restore them when moving to another Windows device.

Go to:

Settings > Accounts > Windows backup

Look for:

Remember my apps

If you don't want Windows remembering your installed applications for restoration, turn it off.

There is an important business distinction here.

Microsoft says Remember my apps isn't available for work or school accounts, and Windows doesn't remember apps for those accounts.

So if a company-owned, Entra-joined PC keeps reinstalling a managed application, don't automatically blame Windows Backup.

Look at your management platform.

For personal Microsoft accounts, Windows Backup can retain a list of installed applications to help restore the user's environment on another PC.

This makes Windows Backup most relevant when apps seem to return after:

• moving to another PC
• rebuilding Windows
• restoring a personal Windows environment
• signing into a newly configured PC with the same personal Microsoft account

Turning off Remember my apps does not uninstall applications that are already present.

Method 3: Remove a Store/Appx Package From Your User Account

Some Windows applications are packaged using Appx/MSIX rather than traditional desktop installers.

If Settings won't remove the application, PowerShell can help.

Open Windows Terminal or PowerShell as Administrator.

First, identify the package:

Get-AppxPackage | Select-Object Name, PackageFullName

To narrow the search:

Get-AppxPackage *AppName*

Replace AppName with a distinctive part of the application's name.

Once you have positively identified the correct package, it can be removed from the current user with:

Get-AppxPackage *AppName* | Remove-AppxPackage

But understand what you've just done.

You removed the package from that user.

You haven't necessarily stopped Windows making it available to future users.

That's where provisioning comes in.

Installed Package vs Provisioned Package

This distinction explains a huge number of supposedly “reinstalled” Windows apps.

Think of Windows as having two layers.

Existing-user installation

The app is registered for a user who already exists.

Remove-AppxPackage deals with this layer.

Future-user provisioning

Windows contains a provisioned package that can be installed when a new user profile is created.

Remove-AppxProvisionedPackage deals with this layer.

Microsoft explicitly confirms that removing a provisioned package prevents it being installed for new user accounts, but does not remove it from existing user accounts.

That's why removing something from your desktop doesn't necessarily mean you've removed it from the Windows image.

Method 4: Remove the Provisioned Package

To see the provisioned applications on the current Windows installation, run:

Get-AppxProvisionedPackage -Online |
Select-Object DisplayName, PackageName

Find the application carefully.

Record both its:

DisplayName

and:

PackageName

Then, when you're certain you have the correct package, the structure for removing it is:

Remove-AppxProvisionedPackage -Online -PackageName "PACKAGE_NAME"

Replace PACKAGE_NAME with the complete package name returned by Windows.

Microsoft documents that this removes the package from the Windows image so it isn't automatically installed when new user accounts are created.

Why the Existing User May Still Have It

This is expected.

Microsoft's documentation is clear that removing a provisioned package doesn't automatically remove that application from existing user accounts.

You may therefore need to deal with:

Existing users: Remove-AppxPackage

and separately:

Future users: Remove-AppxProvisionedPackage

Don't confuse the two.

Does Windows Update Always Put Removed Apps Back?

No.

This is worth clarifying because there is a lot of outdated advice online claiming Windows Update simply reinstalls every built-in application you remove.

Microsoft documents specific behaviour for applications deprovisioned from an online Windows installation.

When a provisioned application is removed in this supported way, Windows creates information telling servicing not to reinstall or update that deprovisioned application during subsequent Windows updates.

So if an application continually returns, don't automatically conclude:

“Windows Update ignored me.”

Investigate whether it is actually being restored by:

• Intune
• another management platform
• an OEM utility
• Windows Backup
• another installer
• user provisioning
• a newly introduced Windows component

Finding the deployment source is much more useful than repeatedly fighting Windows Update.

Business PCs: Check Intune Before Running Removal Scripts

For a managed company computer, I would move this investigation near the top of the list.

An employee says:

“I keep uninstalling this program and Windows keeps putting it back.”

IT checks Microsoft Intune.

The application is assigned:

Required

There's your answer.

Microsoft says Intune automatically attempts to reinstall required applications when they're no longer detected. It can automatically reinstall, update or remove required applications within approximately 24 hours.

That is not Windows malfunctioning.

Intune is doing exactly what the administrator configured it to do.

If an application should no longer be installed, correct its assignment centrally rather than fighting the policy on individual PCs.

Check Intune Detection Rules Too

There's a subtler Intune problem.

Sometimes the application really is installed, but the detection rule is wrong.

Intune decides whether many Win32 applications are present using configured detection rules.

If the rule tells Intune:

“Application missing”

when it is actually installed, Intune can offer the required application for installation again.

Microsoft documents that required Win32 apps that aren't detected can be offered again within approximately 24 hours.

So if a business application keeps reinstalling or repairing itself unexpectedly, check:

• assignment
• install intent
• detection rules
• installation context
• version detection
• dependencies
• supersedence

The problem may be your deployment configuration rather than Windows itself.

Don't Manually Fix 100 PCs

Suppose you have 100 business laptops and want an unwanted packaged application removed.

Logging into every PC and running:

Remove-AppxPackage

is not good device management.

Define the desired application baseline centrally.

Depending on your Windows edition and management environment, use appropriate controls through:

• Microsoft Intune
• Group Policy
• MDM
• Configuration Manager
• your RMM platform
• supported application-removal policies

This gives you consistency.

New computers receive the same configuration.

Existing machines can be corrected.

Changes can be documented.

And IT isn't repeating the same manual procedure every time a laptop is replaced.

Check Other Management Systems

Intune isn't the only system capable of putting an application back.

Also investigate:

• Group Policy
• Microsoft Store app assignments
• Configuration Manager
• RMM software
• login scripts
• provisioning packages
• software deployment platforms
• device-build scripts

Ask:

Is something deliberately enforcing the presence of this application?

If the answer is yes, change the desired state there.

Don't continually fight the management platform from the endpoint.

Check Manufacturer Software

Dell, HP, Lenovo, ASUS, Acer and other PC manufacturers may supply utilities responsible for:

• driver updates
• firmware
• support applications
• hardware configuration
• recovery
• recommended software

Depending on the manufacturer's configuration, these utilities can sometimes contribute to software appearing or returning.

Look under:

Settings > Apps > Installed apps

for manufacturer utilities.

But don't blindly uninstall everything carrying the manufacturer's name.

Some tools may provide useful or necessary functions such as:

• BIOS/firmware updates
• battery controls
• docking support
• driver management
• hardware diagnostics

Again:

Identify the source before removing it.

Sometimes It's Just a Start Recommendation

If an unwanted application appears in Start but not under Installed apps, check Windows' recommendation settings.

Go to:

Settings > Personalisation > Start

Review options relating to:

• recently added apps
• recommendations
• tips
• shortcuts
• suggested content

Also review:

Settings > System > Notifications > Additional settings

and disable unwanted suggestions or Windows setup prompts where appropriate.

This can reduce clutter.

But remember:

Hiding a recommendation is not the same as uninstalling an application.

Don't Disable Microsoft Store Updates

If an unwanted Store application keeps appearing, it can be tempting to disable Store updates completely.

Don't use a sledgehammer to solve a deployment problem.

Microsoft Store applications need security and reliability updates too. Microsoft also notes that Store apps deployed through Intune are automatically kept updated and that disabling automatic Store updating can interfere with that process.

Instead, establish why the unwanted application exists.

Is it:

• required by Intune?
• provisioned?
• a dependency?
• restored?
• part of Windows?
• installed by another application?

Fix the cause.

Don't Remove Everything Beginning With “Microsoft”

PowerShell gives administrators enormous control over packaged applications.

It also makes it remarkably easy to break things quickly.

Do not assume that something is unnecessary because:

• you've never opened it
• you don't recognise its name
• it contains “Microsoft”
• somebody's debloat script removes it

Windows packages can include:

• frameworks
• runtimes
• identity components
• WebView components
• App Installer
• shell components
• application dependencies

Removing a dependency can cause seemingly unrelated applications to stop working.

Before removing a provisioned package, record the exact:

DisplayName

and:

PackageName

Then establish what the package actually does.

For a business deployment, test removal on a representative non-critical device before applying it across the organisation.

Avoid Generic Windows “Debloat” Scripts

A script called:

Ultimate Windows 11 Debloater 2026

may look convenient.

It may also remove 40 packages you never intended to touch.

Generic debloat scripts can:

• remove dependencies
• break Microsoft Store applications
• damage Windows features
• interfere with management tools
• remove components employees actually need
• create inconsistent configurations
• make future troubleshooting harder

For a personal test PC, you may choose to experiment.

For 100 production business laptops, use a documented and tested application baseline.

Repeatability beats aggressive debloating.

Prove That Your Fix Worked

This is an important step that is often forgotten.

You remove the app.

It disappears.

You declare victory.

But the original problem was:

“It keeps coming back.”

So test the condition that caused it to return.

It returned after rebooting

Restart the PC and check again.

It appeared for new users

Create an appropriate test user and verify the package isn't provisioned.

Intune kept reinstalling it

Review the assignment, then allow or trigger an appropriate management sync and check the resulting status.

It appeared after Windows servicing

Validate the configuration on an appropriate test machine through your normal update process.

It returned during new-device setup

Validate your deployment/build process on a test device.

Don't reset a production computer merely to prove a point.

The objective is to verify that you've fixed the source, not merely removed the visible application again.

Quick Diagnostic Table

The table is deliberately a starting point rather than an absolute diagnosis.

Use the behaviour to narrow down the source.

A Better Troubleshooting Order

When a Windows 11 app refuses to stay deleted:

1. Confirm whether it is actually installed.
2. Uninstall it normally.
3. Note exactly when it returns.
4. On a personal PC, review Windows Backup where relevant.
5. On a business PC, check Intune or other management systems early.
6. Determine whether it is an Appx/MSIX package.
7. Remove the current-user package if appropriate.
8. Check whether the package is provisioned for future users.
9. Remove provisioning only after positively identifying the package.
10. Check OEM software and other deployment tools.
11. Avoid disabling Store updates as a workaround.
12. Avoid generic debloat scripts.
13. Test the scenario that previously caused the app to return.
14. For business estates, deploy the desired configuration centrally.

The objective is not:

“Find the strongest PowerShell command.”

It is:

“Find the system responsible for installing the application and correct that configuration.”

Why This Matters for Businesses

One unwanted app on one laptop is an annoyance.

An inconsistent application estate across 100 computers is an IT-management problem.

Businesses should know:

• which applications are approved
• which applications are required
• which applications are optional
• which applications should be removed
• how applications are deployed
• who can install software
• how applications are updated
• how new devices receive the standard configuration

If employees are manually removing unwanted software from every new PC, your device-build process needs improvement.

A properly managed environment should make the desired state repeatable.

How Hamilton Group Can Help

Hamilton Group helps businesses manage Windows devices consistently rather than fixing the same configuration problem repeatedly on individual PCs.

We can help with:

• Windows 11 configuration
• Microsoft Intune
• Microsoft 365
• application deployment
• Microsoft Store apps
• Windows provisioning
• device baselines
• PC deployment
• patch management
• endpoint security
• Windows troubleshooting
• managed IT support

If one application keeps returning on one PC, we can find out why.

If unwanted applications are appearing across an entire organisation, the better solution is to correct the deployment, provisioning or device-management configuration centrally.

Visit or call 0330 043 0069 to discuss Windows 11 and business device management.