Forum Discussion
FTA Shell verb limitations because reserved for system use
In packaging a traditional application, it sets up file type association verbs for a number of file types, including png and ttf.
The manifest validates and package creates just fine. When you attempt to install the package, the desktop appinstaller fails during installation with the message:
App installation failed with error message: AppXManifest.xml(line,col😞 error 0x80080204: Cannot register the XXX package because the '.ttf' file type association is reserved for system use. (0x80080204).
Here is the portion of the AppXManifest file:
<uap3:Extension Category="windows.fileTypeAssociation">
<uap3:FileTypeAssociation Name="ttf">
<uap:SupportedFileTypes>
<uap:FileType>.ttf</uap:FileType>
</uap:SupportedFileTypes>
<uap2:SupportedVerbs>
<uap3:Verb Id="open" uap7:Default="false" Parameters=""%1"">open</uap3:Verb>
</uap2:SupportedVerbs>
</uap3:FileTypeAssociation>
</uap3:Extension>
The ttf fta is defined in the base OS under the HKLM\Software\Classes\SystemFileAssociations key, but so are a lot of others, including png.
Can you please define the list of restricted ftas? This is necessary for third-party tooling to ensure good packages are being generated.
Bumping the request for the list of restricted FTA types as I just ran into a second one. Why is the disallowed list a "secret"?
add-appxpackage : Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.
AppxManifest.xml(3048,16): error 0x80080204: Cannot register the Autodesk-TrueView_2024.0.0.0_x64__k7hsda8r3p9s2
package because the '.scr' file type association is reserved for system use.
NOTE: For additional information, look for [ActivityId] 2b1e5052-4669-0001-00e4-2b2b6946db01 in the Event Log or use
the command line Get-AppPackageLog -ActivityID 2b1e5052-4669-0001-00e4-2b2b6946db01Known items on the list so far: .ttf .scr
