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'.
20+ years shipping production infrastructure and CI/CD at scale. Drawn from code that ran under real load.
- ✓Basic Windows administration
- 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).
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.
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.
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.
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:
The Kiosk Image That Couldn't Update Its Apps
- 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.
| File | Command / Code | Purpose |
|---|---|---|
| check_profile.ps1 | $env:USERPROFILE | Check Whether You're on a Temporary Profile |
| allow_special_profiles.ps1 | New-Item -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\Appx' -Force | Out-Nul... | Fix 2 |
Key takeaways
Common mistakes to avoid
3 patternsReinstalling or re-signing the app package
Working on in a temporary profile
Enabling the policy on a home edition
Interview Questions on This Topic
A packaged-app install works on a developer laptop but fails with 0x80073D23 on shared lab PCs. Why?
Frequently Asked Questions
20+ years shipping production infrastructure and CI/CD at scale. Drawn from code that ran under real load.
That's Platform. Mark it forged?
3 min read · try the examples if you haven't