Home › DevOps › Fix 0x80073D23: Deployment Blocked Because Special Profile Deployment Is Not Allowed
Beginner 3 min · November 05, 2026

Fix 0x80073D23: Deployment Blocked Because Special Profile Deployment Is Not Allowed

Fix Windows error 0x80073D23, 'The deployment operation was blocked because special profile deployment is not allowed'.

N
Naren Founder & Principal Engineer

20+ years shipping production infrastructure and CI/CD at scale. Drawn from code that ran under real load.

Follow
✓ Production
production tested
November 05, 2026
last updated
2,128
articles · all by Naren
Before you start⏱ 7 min
  • ✓Basic Windows administration
 ● Production Incident 🔎 Debug Guide
⚡Quick Answer
  • Error: The deployment operation was blocked because special profile deployment is not allowed (HRESULT 0x80073D23).
  • Special profiles: temporary, mandatory/super-mandatory, roaming profiles set to delete cached copies, and Guest accounts.
  • Most common case: Windows signed you in with a temporary profile because your profile failed to load.
  • Best fix: sign in with your normal profile (fix the profile load problem first).
  • Admin fix: enable Group Policy Allow deployment operations in special profiles (Computer Configuration > Administrative Templates > Windows Components > App Package Deployment).
✦ Definition~90s read
What is Windows Error 0x80073D23?

0x80073D23 is a Windows app-package error: installing, re-registering, updating or removing a Microsoft Store (packaged) app is blocked because you're signed in with a special profile, one whose changes are discarded at sign-off.

★
Windows is refusing to install apps into a profile that it's going to throw away when you log off, such as a temporary profile created because your normal one didn't load.
Plain-English First

Windows is refusing to install apps into a profile that it's going to throw away when you log off, such as a temporary profile created because your normal one didn't load. It's like refusing to unpack furniture into a hotel room you're checking out of.

You run a PowerShell command such as Add-AppxPackage, or re-register the Microsoft Store apps, and Windows answers: Deployment failed with HRESULT: 0x80073D23, The deployment operation was blocked because special profile deployment is not allowed. Nothing is wrong with the package. Windows has a policy that blocks app deployment in profiles that won't be kept, and you're currently signed in to one of them.

What Counts as a Special Profile

Microsoft defines special profiles as user profiles whose changes are discarded when the user signs off:

  • Roaming profiles where the Delete cached copies of roaming profiles policy applies.
  • Mandatory and super-mandatory profiles created by an administrator.
  • Temporary profiles, created when an error stops your real profile from loading.
  • Profiles for the Guest account and members of the Guests group.

By default, Windows blocks adding, registering, staging, updating or removing packaged Microsoft Store apps in these profiles, and reports 0x80073D23.

🔥Most likely on a home PC
If this is your own PC, you're almost certainly on a temporary profile. Windows usually shows a notification saying you've been signed in with one.
🎯 Key Takeaway
0x80073D23 is caused by the profile type, not the app.

Check Whether You're on a Temporary Profile

A temporary profile lives under C:\Users\TEMP (or similar), and anything you save is lost at sign-off. Check the profile path of the current session.

check_profile.ps1POWERSHELL
1
2
3
4
# Which profile folder is this session using?
$env:USERPROFILE

# A path like C:\Users\TEMP means a temporary profile
⚠ Don't keep working in a temporary profile
Files saved there disappear at sign-off. Copy anything important out before you troubleshoot.
🎯 Key Takeaway
C:\Users\TEMP means the real profile didn't load.

Fix 1: Sign In With Your Normal Profile

The cleanest fix is to stop using the special profile. For a temporary profile, restart first: a one-off load failure often clears. If it keeps happening, the user profile needs repairing (typically by an administrator checking the profile's entry under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList, or creating a new user profile and moving files across). For Guest, use a standard account.

💡Back up first
Before editing ProfileList or rebuilding a profile, back up the user's files and create a restore point.
🎯 Key Takeaway
Fixing the profile is better than allowing installs into a disposable one.

Fix 2: Allow Deployment in Special Profiles (Group Policy)

When special profiles are intentional, such as lab or kiosk machines with mandatory profiles, an administrator can allow packaged-app deployment. The policy is available on Pro, Enterprise and Education editions.

In the Group Policy Editor (gpedit.msc): Computer Configuration > Administrative Templates > Windows Components > App Package Deployment > Allow deployment operations in special profiles > Enabled. Then run gpupdate /force.

The policy writes this registry value, which you can also set directly from an elevated prompt:

allow_special_profiles.ps1POWERSHELL
1
2
3
4
5
6
# Run as Administrator
New-Item -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\Appx' -Force | Out-Null
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\Appx' `
  -Name 'AllowDeploymentInSpecialProfiles' -Value 1 -Type DWord

gpupdate /force
⚠ Company devices
On a managed device, don't change this yourself: the setting may be enforced by your IT department or MDM, and they may block it deliberately.
🎯 Key Takeaway
Policy: Allow deployment operations in special profiles. Registry: AllowDeploymentInSpecialProfiles = 1.
● Production incidentPOST-MORTEMseverity: high

The Kiosk Image That Couldn't Update Its Apps

Symptom
Add-AppxPackage failed with 0x80073D23 on lab PCs but worked on the engineer's own laptop.
Assumption
The team assumed the package or its signing certificate was the problem.
Root cause
The lab accounts used mandatory profiles, which Windows treats as special profiles. By default, packaged-app deployment is blocked in special profiles.
Fix
For the lab image, the team enabled the Allow deployment operations in special profiles policy through Group Policy and moved app provisioning to the machine image, so users didn't need per-session installs.
Key lesson
  • Test deployment scripts with the same profile type users have.
  • 0x80073D23 is about the profile, not the package.
  • Provision apps in the image for shared or mandatory-profile machines.
Production debug guideConfirm the profile type, then pick the right fix4 entries
Symptom · 01
Windows showed 'You've been signed in with a temporary profile'
→
Fix
Fix the profile load problem and sign in normally; don't install apps into the temporary profile.
Symptom · 02
Shared, lab or kiosk PCs
→
Fix
They likely use mandatory profiles; use the Group Policy setting or provision apps in the image.
Symptom · 03
Guest account
→
Fix
Sign in with a standard user account instead.
Symptom · 04
Policy enabled but still failing
→
Fix
Run gpupdate /force and confirm the registry value AllowDeploymentInSpecialProfiles = 1.
⚙ Quick Reference
2 commands from this guide
FileCommand / CodePurpose
check_profile.ps1$env:USERPROFILECheck Whether You're on a Temporary Profile
allow_special_profiles.ps1New-Item -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\Appx' -Force | Out-Nul...Fix 2

Key takeaways

1
0x80073D23 is caused by signing in with a special profile.
2
Temporary profiles are the usual cause on personal PCs.
3
Fix the profile first; it's the cleanest solution.
4
For intentional special profiles, enable Allow deployment operations in special profiles.

Common mistakes to avoid

3 patterns
×

Reinstalling or re-signing the app package

Symptom
The same 0x80073D23 error every time.
Fix
The package is fine; fix or change the profile, or enable the policy.
×

Working on in a temporary profile

Symptom
Files and settings vanish after sign-out.
Fix
Repair the profile and sign in normally.
×

Enabling the policy on a home edition

Symptom
gpedit.msc isn't available.
Fix
Home editions don't include the Group Policy editor; fix the profile instead.
INTERVIEW PREP · PRACTICE MODE

Interview Questions on This Topic

Q01SENIOR
A packaged-app install works on a developer laptop but fails with 0x8007...
Q01 of 01SENIOR

A packaged-app install works on a developer laptop but fails with 0x80073D23 on shared lab PCs. Why?

ANSWER
The lab PCs use mandatory (or other special) profiles, and Windows blocks packaged-app deployment in special profiles by default. Enable Allow deployment operations in special profiles for those machines or provision the app in the image.
FAQ · 2 QUESTIONS

Frequently Asked Questions

01
What is a special profile in Windows?
02
How do I fix 0x80073D23?
N
Naren Founder & Principal Engineer

20+ years shipping production infrastructure and CI/CD at scale. Drawn from code that ran under real load.

Follow
✓ Verified
production tested
November 05, 2026
last updated
2,128
articles · all by Naren
🔥

That's Platform. Mark it forged?

3 min read · try the examples if you haven't

←
Previous
Platform Engineering with Backstage IDPs
2 / 2 · Platform
Next
Claude Code Agent Workflow for Engineers
→