Fix it now
0x80073CFF and 0x80073D01 are policy refusals: the package never gets examined because deployment policy said no. Turn on the sideloading route Microsoft documents, or fix the policy that is blocking it, and the same package installs unchanged.
gpresult /h C:\temp\policy.html
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\Appx"
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock"
gpupdate /force
- Turn sideloading on the documented way. Windows 11: Settings, System, For developers, Developer mode. Windows 10: Settings, Update & Security, For developers, Sideload apps.
- Or set it by policy: Computer Configuration, Administrative Templates, Windows Components, App Package Deployment, and enable ‘Allow all trusted apps to install’. The default is Not configured, which means sideloading is off.
- Check the two registry locations above for AllowAllTrustedApps, AllowDevelopmentWithoutDevLicense and BlockNonAdminUserInstall. Microsoft states that MSIX installation fails if AllowAllTrustedApps is disabled.
- If the device is managed, change this in the management platform. A local edit will be overwritten at the next policy refresh.
- For 0x80073D11 you have hit the developer sideload limit: uninstall a sideloaded package, or sign this one and deploy it normally.
0x800F080C is not in this family at all. It is DISM reporting that a Windows feature name was not recognised, and the answer is DISM /Online /Get-Features /Format:Table to find the real name.
If the package installs after a policy refresh, you are done. If the block is an edition boundary rather than a policy, the next section says which capabilities that is still true for.
Why it happens
0x80073CFF is ERROR_INSTALL_POLICY_FAILURE, and Microsoft’s text is a checklist rather than a sentence: to install this app you need a developer licence or a sideloading-enabled system. It is satisfied by an app deployed with F5 from Visual Studio on a machine with a developer licence, by a package signed with a Microsoft signature and deployed as part of Windows or from the Store, or by a package with a trusted signature on a machine with a developer licence, a domain-joined machine with the AllowAllTrustedApps policy enabled, or a machine with a Windows sideloading licence and that policy enabled.
0x80073D01 is ERROR_DEPLOYMENT_BLOCKED_BY_POLICY, and it names two documented causes: Application Control Policies, and the “Allow deployment operations in special profiles” policy. Microsoft adds a third possibility that costs nothing to test – if no policies are configured and you still see it, you may be logged in with a temporary profile, so sign out and back in before investigating further.
The edition question needs care, because it has changed. Microsoft states that as of KB 5024351, Windows 10 versions 2004 and newer and all Windows 11 versions no longer require a specific edition of Windows to enforce AppLocker policies. What is still edition-bound is App-V: Microsoft documents the App-V client as included with the Windows Enterprise edition, from Windows 10 version 1607, and installed automatically from that version.
Sideloading has never been turned on
You have this one if 0x80073CFF on a machine that has only ever installed Store apps, with no management platform involved.
- Windows 11: Settings, System, For developers, and turn on Developer mode. Windows 10: Settings, Update & Security, For developers, and turn on Sideload apps.
- Or enable ‘Allow all trusted apps to install’ under Computer Configuration, Administrative Templates, Windows Components, App Package Deployment.
- The equivalent value is AllowAllTrustedApps, under HKLM\SOFTWARE\Policies\Microsoft\Windows\Appx or HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock.
Application control policy is refusing the deployment
You have this one if 0x80073D01 on a managed device, while the same package installs on an unmanaged one.
- Capture the effective policy first:
gpresult /h C:\temp\policy.htmlfrom an elevated prompt, then read it. - Look in Event Viewer under Applications and Services Logs, Microsoft, Windows for the AppLocker and CodeIntegrity channels, and match the timestamp to the failure.
- Change the rule at the policy object that sets it, then
gpupdate /forceon the client. Editing locally on a managed device achieves nothing lasting.
You are in a special or temporary profile
You have this one if 0x80073D01 with no application control policy configured anywhere.
- Sign out and sign back in, then retry. Microsoft names a temporary profile as a cause of this code.
- If the estate uses roaming profiles, check the ‘Allow deployment operations in special profiles’ policy, which Microsoft also names.
- Confirm the profile loaded correctly rather than falling back to a temporary one – a profile that failed to load produces this alongside a long list of unrelated oddities.
The developer sideload limit has been reached
You have this one if 0x80073D11, on a development or test machine where packages have been registered from loose files repeatedly.
- Uninstall a sideloaded package. Microsoft’s text is exactly that: you have reached the maximum number of developer sideloaded packages allowed on this device.
- List what is registered in development mode with
Get-AppxPackage | Where-Object {$_.IsDevelopmentMode -eq $true}. - For anything beyond development, sign the package and deploy it normally. The limit does not apply to signed deployment.
DISM does not recognise the feature name
You have this one if 0x800F080C while enabling an optional feature, not while deploying a package.
- List the real names:
DISM /Online /Get-Features /Format:Table. - Microsoft’s message is ‘Feature name <x> is unknown. A Windows feature name was not recognized. Use the /Get-Features option to find the name of the feature in the image.’
- Feature names are case-sensitive and differ between client and server images, so copy the name out of the list rather than typing it.
Full reference
Where the sideloading switches live
| Route | Path |
|---|---|
| Windows 11 Settings | Settings, System, For developers, Developer mode |
| Windows 10 Settings | Settings, Update & Security, For developers, Sideload apps |
| Group Policy | Computer Configuration, Administrative Templates, Windows Components, App Package Deployment |
| Policy: trusted apps | Allow all trusted apps to install |
| Policy: development | Allows development of Windows Store apps and installing them from an integrated development environment (IDE) |
| Registry (policy branch) | HKLM\SOFTWARE\Policies\Microsoft\Windows\Appx |
| Registry (unlock branch) | HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock |
The three values Microsoft names in those two locations are BlockNonAdminUserInstall, AllowAllTrustedApps and AllowDevelopmentWithoutDevLicense. The important one for this article is AllowAllTrustedApps: Microsoft states plainly that if it is disabled, MSIX installation fails. Both policies default to Not configured, which means sideloading is off until someone turns it on.
What is still an edition boundary, and what is not
- AppLocker enforcement is no longer edition-bound. Microsoft: as of KB 5024351, Windows 10 versions 2004 and newer and all Windows 11 versions no longer require a specific edition of Windows to enforce AppLocker policies. On versions older than 2004, and on Windows Server 2019, policies deployed through Group Policy were supported on Enterprise and Server editions only, while policies deployed through MDM were supported on all editions.
- App-V is edition-bound. Microsoft documents the App-V client as included with the Windows Enterprise edition starting with Windows 10 version 1607, and automatically installed from that version.
- Sideloading is a policy setting, not an edition feature. Microsoft documents the Settings switch and the two App Package Deployment policies without naming an edition requirement for them.
- The developer sideload limit is a device limit, not an edition one. Signing the package removes it.
Where App-V stands now
This matters because it changes whether App-V is a sensible thing to plan around. Microsoft’s current position is that the App-V client and sequencer are no longer deprecated: they moved to a fixed extended support lifecycle in November 2024, they continue to ship as part of Windows, and they receive bug and security fixes but no new features or design changes. The server components are a separate matter – they are still deprecated and their support ends in April 2026.
On migration, Microsoft’s wording is deliberately unhurried: if the current feature set of App-V works for you, there is no need to migrate away. MSIX is an alternative rather than a mandated replacement. Plan a move if you need capabilities App-V will not gain, or if you depend on the server components whose support is ending; do not plan one because you believe the client is going away.
Enable-Appv and reading its state
| Command | What it does |
|---|---|
Get-AppvStatus |
Reports whether the App-V client is enabled on this device |
Enable-Appv |
Enables the App-V client |
gpresult /h C:\temp\policy.html |
Writes the effective policy to an HTML report you can read |
gpupdate /force |
Reapplies policy immediately rather than waiting for the refresh interval |
DISM /Online /Get-Features /Format:Table |
Lists the feature names this image actually knows about |
Before you conclude it is the edition
- Read the code. 0x80073CFF and 0x80073D01 are policy; 0x800F080C is a feature name; 0x80073D11 is the sideload limit.
- Capture gpresult and read it rather than inferring policy from behaviour.
- Check both registry locations for AllowAllTrustedApps before assuming Group Policy is the only place it can be set.
- Test the same package on an unmanaged machine of the same edition and build. If it installs, the block is policy and the edition is a red herring.
When a licence is the actual fix
There is one capability in this article that a licence genuinely gates, and it is App-V: Microsoft documents the App-V client as included with the Windows Enterprise edition from Windows 10 version 1607. Windows 11 Enterprise E3 is the per-user subscription route to that edition, so if you have packaged applications that only exist as App-V sequences and no route to repackage them, that is the licence that makes them supportable. Buy it with your eyes open, though. The App-V client sits on a fixed extended support lifecycle with no further development, and the App-V server components are still deprecated with support ending in April 2026, so an Enterprise purchase made purely for App-V is buying time rather than a future. Everything else here is free to fix: sideloading is a Settings switch or a policy value, AppLocker enforcement no longer requires a specific edition on current builds, and 0x80073D11 goes away when you sign the package. If the only symptom you have is 0x80073CFF, no licence purchase will change it.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80073CFF |
ERROR_INSTALL_POLICY_FAILURE: a developer licence or a sideloading-enabled system is needed. Microsoft lists the AllowAllTrustedApps policy and a Microsoft-signed or trusted-signed package as the alternatives | Microsoft Learn |
0x80073D01 |
ERROR_DEPLOYMENT_BLOCKED_BY_POLICY: deployment blocked by policy. Documented causes are Application Control Policies, the ‘Allow deployment operations in special profiles’ policy, and being logged in with a temporary profile | Microsoft Learn |
0x800F080C |
A Windows feature name was not recognised: ‘Feature name <x> is unknown. Use the /Get-Features option to find the name of the feature in the image’ | Microsoft Learn |
0x80073D11 |
ERROR_DEV_SIDELOAD_LIMIT_EXCEEDED: the maximum number of developer sideloaded packages allowed on this device has been reached. Uninstall a sideloaded package and try again | Microsoft Learn |
Confirm the fix worked
- The sideloading switch reads as on in Settings, or AllowAllTrustedApps is present and set in one of the two registry locations.
gpresult /h C:\temp\policy.htmlno longer shows an App Package Deployment policy disabling it.- The package installs for a normal user, not only for an administrator.
- For App-V,
Get-AppvStatusreports the client enabled on the edition you expected.
Questions people ask about this
Do I need Enterprise to run AppLocker?
Not on current builds. Microsoft states that as of KB 5024351, Windows 10 versions 2004 and newer and all Windows 11 versions no longer require a specific edition to enforce AppLocker policies. Older versions and Windows Server 2019 needed Enterprise or Server for Group Policy-deployed rules, with MDM-deployed rules supported on all editions.
Is App-V being removed from Windows?
No. As of November 2024 the App-V client and sequencer are no longer deprecated and sit on a fixed extended support lifecycle – they still ship with Windows and get bug and security fixes, but no new features. The server components are a different story: still deprecated, support ending April 2026.
Should I migrate my App-V packages to MSIX?
Microsoft’s own line is that if the current feature set of App-V works for you, there is no need to migrate away. Migrate because you need something App-V will not gain, or because you depend on the server components losing support, not because you think the client is disappearing.
I enabled the policy and it still fails. What did I miss?
Check the second registry location. Microsoft names both HKLM\SOFTWARE\Policies\Microsoft\Windows\Appx and HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock as places AllowAllTrustedApps lives, and a value left disabled in the one you did not check will keep failing the install.
