Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Apps, installers & Microsoft Store · reviewed troubleshooting

Microsoft Store app will not install or update in Windows 11

Check account/device availability, restart state, Windows/Store updates and app-specific deployment evidence before broad package repair.

Applies to: Windows 11 / Microsoft Store appsChange risk: LowReviewed: 2026-09-17
Do this first
  1. Confirm the app is available for your region/account/device and that you are signed in with the intended Microsoft account.
  2. Restart Windows if a Windows update was just installed.
  3. Update Windows and Microsoft Store, then retry the single app.
  4. If a deployment code/ActivityId appears, preserve it before resetting or reinstalling anything.

What this problem usually means

Microsoft Store install failures can be availability/account/device-compatibility problems, pending restart/update state, Store cache/app problems, or an MSIX/AppX deployment failure. Keeping those branches separate avoids destructive package re-registration for an app that is simply unavailable or incompatible.

Diagnostic state

What is known, and what is not proven yet

Keep observation, evidence and conclusion separate before making a higher-impact change.

Observed fact

One Store/MSIX app cannot install or update.

Windows evidence

Store/account/device availability plus exact deployment code and ActivityId when present.

Likely subsystem

Microsoft Store delivery, the specific MSIX/AppX package, or package deployment state.

Evidence still needed

Whether the problem affects one package or many and whether AppX logs name a specific deployment reason.

Safe next action

Apply Store/update fixes first, then use the exact AppX code/log for a package-specific branch.

Handoff boundary

App publisher, Microsoft support or managed-device IT when package identity/signing/policy is the remaining failure.

Ordered repair path

Work from the narrowest fix to the broader one.

1

Use Microsoft Store first-line fixes

Low risk

Why this belongs here: Microsoft recommends updating Windows/Store and using Store troubleshooting before deeper package changes.

  1. Close and reopen Microsoft Store.
  2. Install current Windows updates.
  3. Open Microsoft Store > Library and get available Store/app updates.
  4. Run wsreset.exe if Store cache/launch behavior is also abnormal.
2

Move to package evidence only when the failure is truly deployment-specific

Low risk

Why this belongs here: AppX/MSIX deployment errors can expose an ActivityId and package-specific error that is more useful than generic Store resets.

  1. Copy the exact HRESULT/error code and ActivityId if shown.
  2. Use Get-AppxLog with that ActivityId when appropriate.
  3. Confirm whether the same package is already installed or currently running.
  4. Use the matching error record instead of broad re-registration scripts.
Stop condition

When this guide stops being the right path

Do not run bulk Get-AppxPackage re-registration scripts simply because one Store app fails. System/inbox packages and per-user package state require more context.

If the problem is still not fixed

If the error is 0x80073D02, close the running app/resources first. If the package already exists (0x80073CFB), verify the installed package/version before attempting another deployment.

Evidence

Sources reviewed for this page

Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

GuideMicrosoft Store app not installing in Windows 11: update, account and cache checks

Separate a Store/app problem from regional availability or a broader Windows problem before reinstalling anything.

CommandGet-AppxLog — read one AppX/MSIX deployment ActivityId

Read the package-deployment log associated with the ActivityId returned by a failed Add-AppxPackage or Remove-AppxPackage operation.

Error0x80073CFB — MSIX/AppX package already exists for this user

0x80073CFB indicates an identical package is already registered; verify the installed package/version before attempting another deployment.

Error0x80073D02 — MSIX/AppX package resources are currently in use

0x80073D02 means package deployment cannot proceed because a running process is using resources that must be changed.

GuideDesktop program will not install, update or uninstall in Windows 11

Separate a desktop installer problem from Microsoft Store/MSIX deployment, then use repair, uninstall and installer evidence in the least disruptive order.

CommandGet-AppxPackage — inspect one installed package

Read the installed AppX/MSIX package identity/version for the current user without modifying the package.