How to fix Microsoft Store error 0x80073D01?

Error 0x80073D01 means Windows refused to install an app package because a policy blocks it. Microsoft names two causes: an application control policy such as AppLocker, and a temporary, guest or other special profile. Start by signing out and back in to your own profile, then look for the policy.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What error 0x80073D01 means in Microsoft Store and Windows

Store apps, Windows' own inbox apps and many language packs are app packages (APPX or MSIX). Windows installs them through one service, and before it does, it checks the policies that apply to you and to the PC. 0x80073D01 is the answer when a policy says no. Microsoft's developer documentation names it ERROR_DEPLOYMENT_BLOCKED_BY_POLICY: "The package deployment operation is blocked by policy. Contact your system administrator."

What Microsoft Learn lists

Two causes: deployment blocked by Application Control Policies, or blocked by the "Allow deployment operations in special profiles" policy. With no policy set, Microsoft says you may be signed in with a temporary profile.

The full text in PowerShell

Add-AppxPackage : Deployment failed with HRESULT: 0x80073D01, The package deployment operation is blocked by policy. Please contact your system administrator.

The second code that names the culprit

Users on Microsoft Q&A report a second line such as error 0x800704EC: Deployment of package ... was blocked by AppLocker. That line tells you which policy fired.

What it is not

Not a damaged Store cache, not a network error and not a full disk. Those have their own codes.

This is why the usual Store advice often fails here. Clearing the cache, resetting the Store or running the troubleshooter does not touch a policy, so the same code comes back. The old version of this guide led with those steps. We moved them to the end.

Why Windows shows 0x80073D01: the causes, ranked

On a home PC the most common reason is that you are not in your normal profile: Windows loaded a temporary one, or you use a Guest or shared account. Next come AppLocker rules that someone set up, often for a test. Less often an App Package Deployment policy, a tweaking tool or the PC's management by a work or school blocks the install.

0x80073D01 when you install a language pack on Windows 11 or Windows 10

Many searches for this code are about languages, not apps. The reason is the format. Microsoft's Windows 11 documentation says that 47 of the Language Interface Pack languages are "available only as .appx packages" and are added through the Settings app. Such a pack goes through the same package deployment as a Store app, so the same policies block it with the same code.

• Windows 10: Microsoft Support says you need to be an administrator on the PC to add a language pack. A standard account can see the language fail.
• Windows 11: Microsoft says non-administrator accounts can add a display language and its features. If one still fails with 0x80073D01, a policy or a special profile is the cause, as on this page.
• The language works, but a "failed" notice keeps coming: users on Microsoft Q&A report this. The Store keeps retrying a pack that is already there. Clear its queue with Fix 8.
• Microsoft 365 apps: a language for Word or Excel is a separate Office language pack, not a Windows one.

How to fix error 0x80073D01 in Microsoft Store and Windows

Start with Fix 1: it takes five minutes and solves the profile case that Microsoft names. Fix 2 tells you which policy blocks you, so you can skip straight to Fix 3, 4 or 5. Fix 6 is for language packs. Fixes 7 and 8 are the last checks when no policy shows up.

Fix 1. Sign out and sign in to your own profile, not a temporary or Guest one

5 minutesNo riskEveryone first, and above all when your desktop, files or settings look different than usual.

Microsoft says that when no policy is configured and you still see 0x80073D01, you may be signed in with a temporary profile, and tells you to log out and log in again. Windows blocks app installs in temporary, guest, mandatory and some roaming profiles by default.

1. Save your work. Files you created in a temporary profile are deleted when you sign out, so copy them to a USB stick or OneDrive first.
2. Select Start, your account picture, then Sign out.
3. Sign in again with your usual account and password.
4. Press Win + R, type cmd and press Enter. Type echo %USERPROFILE% and press Enter.
5. Read the path. Your own profile is C:\Users\YourName. A path with TEMP in it means Windows loaded a temporary profile again.
6. Open Settings > Accounts > Your info and check that the account is not Guest and shows Administrator or Standard user.
7. Try the install again from Microsoft Store.

• Temporary profile every time: your real profile could not load. Restart once more. If it repeats, sign in with another administrator account and copy your files out, then create a new account (Fix 7).
• Guest or shared accounts: the policy Allow deployment operations in special profiles is off by default, so these accounts cannot install apps. Use your own account instead.

Fix 2. Find the policy that blocks the install

10 minutesNo riskThe code stays in your normal profile, or you do not know whether anyone set policies on this PC.

0x80073D01 always means a policy said no, so reading the policies tells you which fix to use. These commands only read settings and change nothing.

1. Open Settings > Accounts > Access work or school. If an organisation is listed, the PC is managed. Send the code to its IT support; they can see the policy.
2. Right-click Start and select Terminal (Admin) (Windows 10: Windows PowerShell (Admin)). Select Yes.
3. Run the first command below. Values in the output are App Package Deployment policies. Note each value name for Fix 4.
4. Run the second command. Values here are Microsoft Store policies, such as a policy that disables Store apps.
5. Run the third command. If it lists RuleCollection Type="Exe" with EnforcementMode="Enabled" but no Appx collection, AppLocker blocks every packaged app (Fix 3).
6. For the exact reason, open the event log as shown in If 0x80073D01 is still there below.

Windows Terminal or PowerShell as administrator: read the policies (nothing is changed)

reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\Appx"
reg query "HKLM\SOFTWARE\Policies\Microsoft\WindowsStore"
Get-AppLockerPolicy -Effective -Xml

"ERROR: The system was unable to find the specified registry key or value" after a reg query is good news: no policy of that kind is set. If all three commands come back empty, skip to Fix 5.

Fix 3. Add the default Packaged app rules in AppLocker

10 minutesRead the warningYour own PC, PowerShell says "blocked by AppLocker", or Fix 2 shows enforced Executable rules without Packaged app rules.

Microsoft's AppLocker documentation says that AppLocker blocks all packaged apps when rules exist in the Executable collection, until you allow packaged apps on purpose. The default Packaged app rule allows signed packaged apps for everyone, which lifts the block and keeps your other rules.

1. Press Win + R, type secpol.msc and press Enter (or open gpedit.msc and go to Computer Configuration > Windows Settings > Security Settings). Both need Pro, Enterprise or Education.
2. Open Application Control Policies > AppLocker.
3. Select Packaged app Rules. If the right pane says "There are no items to show in this view", this is the cause.
4. Right-click Packaged app Rules and select Create Default Rules.
5. Check that a rule now allows Everyone to run All signed packaged apps.
6. Open Terminal (Admin) and run gpupdate /force, then restart the PC.
7. Install the app again.

• Allow only one app: instead of the default rule, select Create New Rule, choose Use an installed packaged app as a reference and select the app. This keeps a tight policy.
• Why not delete the rules: the old version of this guide said to delete everything under Packaged app Rules. That does not help while Executable rules are enforced, because an empty Packaged app list still blocks every packaged app.
• Windows Home: since update KB5024351, Microsoft says AppLocker can be enforced on every edition of Windows 10 2004 and newer and Windows 11. Home has no editor to change it; use Set-AppLockerPolicy with the backup file, or ask the person who set it.

Fix 4. Set the App Package Deployment policies back to Not configured

10 minutesRead the warningFix 2 found values under the Appx policy key on a PC that you own and manage yourself.

These policies are read every time Windows installs a package. A value left by an old setup, a former employer or a tweaking tool keeps blocking installs until it is removed. Setting it to Not configured gives back the Windows default.

1. Pro, Enterprise or Education: open the Local Group Policy Editor: Open the Local Group Policy Editor
2. Go to Computer Configuration > Administrative Templates > Windows Components > App Package Deployment.
3. Double-click Prevent non-admin users from installing packaged Windows apps and select Not Configured, then OK.
4. Do the same for Disable installing Windows apps on non-system volumes if it is Enabled.
5. Under Windows Components > Store, set Disable all apps from Microsoft Store to Not Configured if it is enabled.
6. Home edition, or when the editor shows nothing: remove only the value names Fix 2 found, with the command below, one line per value.
7. Run gpupdate /force, restart the PC and try the install again.

Terminal (Admin): remove one policy value that Fix 2 found (example for BlockNonAdminUserInstall)

reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\Appx" /v BlockNonAdminUserInstall /f

Shared PCs, classrooms and kiosks are the one case where you may want the opposite. To let temporary or mandatory profiles install apps, an administrator sets Allow deployment operations in special profiles to Enabled. Microsoft documents it in the same folder.

Fix 5. Save new apps to the system drive

5 minutesLow riskNew apps are set to save on a second drive, an SD card or a USB disk, or such a drive was removed.

The policy Disable installing Windows apps on non-system volumes blocks installs to any drive other than the system drive. A Microsoft moderator's first advice for this code on Microsoft Q&A was to set the storage location back to the system drive.

1. Open Settings > System > Storage.
2. Windows 11: select Advanced storage settings > Where new content is saved. Windows 10: select Change where new content is saved.
3. Under New apps will save to, choose the drive Windows is on, usually C:, and select Apply.
4. Restart Microsoft Store and install the app again.

Fix 6. Add the language from an administrator account

10 to 20 minutesLow riskA display language, language features or a Local Experience Pack fails with 0x80073D01.

Many Windows languages arrive as app packages, so they meet the same policy check as Store apps. Microsoft says Windows 10 needs an administrator to add a language pack. An administrator account in its own normal profile avoids both the rights problem and the special profile block.

1. Sign in with an account that is an Administrator (check in Settings > Accounts > Your info).
2. Windows 11: open Settings > Time & language > Language & region. Windows 10: Settings > Time & Language > Language.
3. If the language is already listed with an error, select it, then Remove, and restart the PC.
4. Select Add a language, type the language name, select it and Next.
5. Under Install language features, keep the features you need and select Install.
6. Wait until the language shows no download icon, then sign out and sign in again.

• Still blocked: the language is subject to the same AppLocker and Appx policies. Go back to Fix 2, 3 and 4.
• Language works but warnings repeat: clear the Store queue with Fix 8. The Store retries a pack that is already installed.
• After you add a language on an image: Microsoft advises reinstalling the latest cumulative update. For a home PC, run Windows Update once after adding the language.

Fix 7. Test the install in a new local account

10 minutesLow riskNo policy shows up in Fix 2, you are in your normal profile, and the code stays.

Microsoft's moderators suggest a new account for this code on Microsoft Q&A. Package registration is per user, so a new profile tells you whether the block is in your profile or on the whole PC.

1. Create a new local account and make it an administrator for the test. Step by step: Create a new user account to test a problem
2. Sign out of your account and sign in to the new one. The first sign-in takes a few minutes.
3. Open Microsoft Store in the new account and install the same app or language that failed.
4. Note whether the code appears, then sign back in to your own account.

• The app installs in the new account: the block is in your old profile. Move your files to the new account and use it, or keep testing with Fix 8.
• The app fails in the new account too: the block is on the PC. Read the event log as in the next section, and look again at the policies in Fix 2.

Fix 8. Reset Microsoft Store and clear its download queue

5 minutesLow riskNo policy was found, or a language or app that already works keeps showing failed downloads.

A reset cannot lift a policy, so it rarely fixes this code alone. It clears a Store queue that keeps retrying an install that was blocked once, and it signs the Store in again after Fixes 1 to 6.

1. Clear the Store cache. Press Windows + R, type wsreset.exe and select OK. A blank Command Prompt window opens; after a short while it closes and Microsoft Store opens by itself.
2. Open System components. If the problem stays, select Start > Settings > System > System components. Next to Microsoft Store, select the three dots and Advanced options. If Microsoft Store is not listed there, look for it in Settings > Apps > Installed apps.
3. Repair first. Scroll to Reset and select Repair. Repair keeps the app's data. Open the Store and check whether it works.
4. Reset if Repair did not help. Select Reset and confirm. This deletes the Store app's data on this PC; your purchases stay in your Microsoft account. Open the Store and sign in again.

These steps were written for Windows 11 26H2 (build 26300). The full page with the other versions and what each result means: Reset the Microsoft Store

If 0x80073D01 is still there: find the reason and what to send to support

Windows writes the policy that blocked the install into an event log. Microsoft's troubleshooting page for app deployment points to these logs and to the Get-AppxLog command.

1. Try the install once more and note the time.
2. Press Win + R, type eventvwr.msc and press Enter.
3. Open Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational and find the error at that time.
4. Then open Applications and Services Logs > Microsoft > Windows > AppLocker and look at Packaged app-Deployment. Events 8025 and 8027 mean AppLocker blocked the package.
5. For a quick view in PowerShell, run Get-AppxLog | Out-GridView right after the failure.

• What to send to IT or Microsoft support: the app or language name, the full error text from the log, your Windows version and build from Settings > System > About, and the output of Fix 2.
• Event 8027: "No packaged apps can be executed while Exe rules are being enforced and no Packaged app rules have been configured." That is Fix 3.
• Developers: Visual Studio shows error DEP0700 with [0x80073D01] when a policy blocks the debug deployment. The same AppLocker and Appx policies apply, and Allows development of packaged Microsoft Store apps must also be allowed.
• Hardware: Microsoft's description of this code is a policy decision. No hardware fault causes it, and a full disk or a missing drive have their own codes.

Codes that look like 0x80073D01 and what each one means

Microsoft Store and PowerShell show many codes that start with 0x80073D. They come from the same table of app deployment errors on Microsoft Learn, but each stops at a different check, so each has a different fix.

Some searchers type 0x80073D31; we found no Microsoft description for it, so we do not give one. For a conflict with an installed version of a game, see our guide to error 0x80073CF3.

How to keep 0x80073D01 from coming back

• Do not install apps from a temporary profile. If Windows signs you in with one, restart before you do anything else, and fix the profile.
• Test AppLocker in Audit only mode. Microsoft's events 8021 and 8024 show what would be blocked without blocking it. Always add Packaged app rules when you enforce Executable rules.
• Read what a tweaking tool changes. Privacy and "debloat" tools may write policy values. Keep a note of them, and set them back if the Store breaks.
• Keep new apps on the system drive unless you need the space, and keep that drive connected.
• Know whether the PC is managed. If Access work or school lists an organisation, app rules come from it, and changes on the PC do not last.

Keep a restore point before you change policies, so you can undo a mistake in a few minutes: Undo recent changes with System Restore

Frequently asked questions

What does error code 0x80073D01 mean?

It means a policy on the PC blocked the install of an app package. Microsoft names the error ERROR_DEPLOYMENT_BLOCKED_BY_POLICY, and its text is "The package deployment operation is blocked by policy. Please contact your system administrator." Microsoft lists two causes: an application control policy such as AppLocker, and the policy that blocks installs in special profiles, such as temporary and guest profiles. It is not a damaged download. Sign out and sign in again first, then check the policies as in Fix 2.

How do I fix 0x80073D01 on Windows 11?

Sign out and sign in to your own profile, and check that the path from echo %USERPROFILE% is not a TEMP folder (Fix 1). Then read the policies with the three commands in Fix 2. If AppLocker enforces Executable rules without Packaged app rules, create the default Packaged app rules (Fix 3). If values sit under the Appx policy key on your own PC, set them back to Not configured (Fix 4). The steps are the same on Windows 11 25H2 and 26H2.

Is 0x80073D01 different on Windows 10?

No. The code, its meaning and the fixes are the same on Windows 10 22H2. Some menu paths differ: Windows 10 shows Change where new content is saved directly on the Storage page, and Settings > Time & Language > Language for languages. Microsoft also says Windows 10 needs an administrator to add a language pack. Keep in mind that Windows 10 left Microsoft support on 14 October 2025, so it gets no further fixes.

Why do I get 0x80073D01 when installing a language pack?

Because many Windows languages are app packages. Microsoft's documentation says 47 Language Interface Pack languages on Windows 11 come only as .appx packages added through Settings. They go through the same deployment check as Store apps, so a temporary profile, an AppLocker rule or an Appx policy blocks them with the same code. On Windows 10 a standard account cannot add a language pack at all. Add the language from an administrator account in its normal profile, as in Fix 6.

Is 0x80073D01 caused by AppLocker?

Often, but not always. AppLocker is one of the two causes Microsoft names. You can tell from PowerShell: users report a second line such as error 0x800704EC saying the package was blocked by AppLocker. Event 8027 in the AppLocker log says the same. If you are in a temporary or guest profile, the special profile policy is the cause instead. Fix 2 shows which one applies to you in a few minutes.

Should I delete all AppLocker Packaged app rules to fix it?

No. The earlier version of this guide said so, and it does not work while Executable rules are enforced. Microsoft's documentation says AppLocker blocks all packaged apps in that case, until you allow them on purpose. An empty Packaged app Rules list is exactly what causes the block. Instead, right-click Packaged app Rules and select Create Default Rules, or create one rule for the app you need. Save the policy first with Get-AppLockerPolicy, as shown in Fix 3.

Can I fix 0x80073D01 on a work or school computer?

Usually not by yourself. If Settings > Accounts > Access work or school lists an organisation, its policies come from Intune, another management tool or the domain, and they are applied again at the next sync. The block is a decision of your IT team, which is why the message says to contact your system administrator. Send them the app name, the code and the event log entry from the last section. They can allow the app or the package family.

Does resetting Microsoft Store or wsreset fix 0x80073D01?

Rarely on its own. wsreset clears the Store cache and a reset clears the app's data, but neither changes a Windows policy, so the same code returns. They help in one case: when the policy is gone but the Store keeps retrying a blocked download, or a language that already works keeps showing failed notices. That is why the reset is the last method here, Fix 8, after the profile and policy checks.

What is the difference between 0x80073D01 and 0x80073D28?

Both stop an install, but for different reasons. The code 0x80073D01 means a policy blocks the deployment, whoever you are. The code 0x80073D28 means the package needs administrator rights, so a standard user cannot install it, and Microsoft's advice is to contact an administrator. If you see 0x80073D28, sign in with an administrator account. If you see 0x80073D01, an administrator account alone may not help, because the policy applies to it too.