Forum Widgets
Latest Discussions
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:ExtensionCategory="windows.fileTypeAssociation"> <uap3:FileTypeAssociationName="ttf"> <uap:SupportedFileTypes> <uap:FileType>.ttf</uap:FileType> </uap:SupportedFileTypes> <uap2:SupportedVerbs> <uap3:VerbId="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.
MSIX Desktop Shortcuts working on Windows 11, but not on Windows 10
Hello, I'm using the latest version of MSIX packaging tool 1.2024.405.0 and I have Windows AppRuntime 1.4.x installed on both OS versions. While using Windows 11 23H2 I can launch the application by using the desktop shortcut and the start menu icon as well, but while using Windows 10 22H2 is working only if I use the start menu icon. I know that I can use PSF fixup to make it work, but why? Shouldn't this work natively? What am I missing? Thank you, BogdanMSIX Packages with WebView2 Dependency now fail to install
I detected this happening starting over Thanksgiving weekend. Packages that have the WebView2 external dependency, including packages that worked just before the holiday, fail to install currently. The following was posted to the WebView2 folks, who suggested it be posted here, however the poster seemed to have issues and I am adding a link to their original post here:MSIX WebView2 ExternalDependency failing to install/update. - Microsoft Q&A It is a pretty good writeup up the issue. My own notes: This may be related to an issue that has also cropped where winget is currently requiring the --allow... parameters rather than allowing you to accept once. So possibly this causes the implementation of the detected install to fail. This has been tested against systems with the latest version of the WinView2 package already installed, and the packages that reference still fail to install. There has also been a suggestion on linkedIn that it might be related to a known WindowsAppSDK issue "There is a known issue with the WinAppSDK 1.6.2 package. https://portalfuse.io/blog/portalfuse-weekly-security-update-november-26-2024 " Finally I'll note that web searches find a similar sounding issue occurred two years ago at the end of November.Understanding App Isolation Behavior in MSIX: Issue with System State Restoration After Crash
We have an application built with .NET Forms, while the security components (DLLs) are developed in C++. Recently, we packaged our application using MSIX (App Isolation) and signed it with a self-signed certificate. The Application launches and functions as expected. However, when we introduce an intentional crash (e.g., a null pointer exception), the system does not restore the changes made by the application, such as hiding the taskbar. Our understanding was that App Isolation would help revert any system modifications after a crash, but it seems this isn't the case. Is this expected behavior for App Isolation in MSIX, or are we missing something in our configuration? Any insights on ensuring system state restoration would be appreciated.
Combine workingdirectory and startScript results in error message.
I am trying to combine both working directory and startup script in the config.json file. Everything seems to be configured correctly. i install the MSIX package but when i try to start it i get this error message. If i exclude either workingDirectory or startScript everything is OK. Config.json { "applications": [ { "id": "NOTEPAD", "executable": "VFS\\ProgramFilesX64\\Notepad++\\notepad++.exe", "workingDirectory": "VFS\\ProgramFilesX64\\Notepad++", "scriptExecutionMode": "-ExecutionPolicy Bypass", "startScript": { "waitForScriptToFinish": true, "runOnce": true, "showWindow": false, "scriptPath": "Copy.ps1" } } ] } Package files AppxManifest.xml <Applications> <Application Id="NOTEPAD" Executable="PsfLauncher64.exe" EntryPoint="Windows.FullTrustApplication">
Eclipse IDE MSIX
Hello Anyone with experience creating a user context MSIX for Eclipse IDE to be deployed true App Attach for Azure Virtual Desktop. I have built a MSIX for Eclipse and ended up bringing the Installer process to the app attachment and not the application. All files are under the user context, and that is not working in a multitenant vm. Any ideas or tips. Thank youMSIX dynamic start menu configuration
With AppV it was possible to configure profiles at the streaming server and assign shortcuts/start menu entries from the AppV package to AD groups. Is it possible to so something similar with MSIX? So a MSIX package has four start menu entries abcd. Member of AAD group X get shortcuts ab Member of AAD group Y get shortcuts cd Anyone has an idea if this can be done by some scripting?
