Forum Widgets
Latest Discussions
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, Bogdan
MSIX package and shortcut icons
I see some strange behavior and can't explain why it is not working. I am playing around with the MSIX package and shortcut icons. I created them using the Visual Asset generator (https://apps.microsoft.com/detail/9mz6qrqtdkf2?hl=en-US&gl=US) and copied them to the Assets folder. When configuring the shortcuts with the files, the shortcuts and package logo stays blank. When I open the manifest and point the entries hardcoded to the files the icons appear. Like this config below. <Application Id="PSFLAUNCHERTwo" Executable="PsfLauncher2.exe" EntryPoint="Windows.FullTrustApplication"> <uap3:VisualElements AppListEntry="default" BackgroundColor="transparent" Description="Fair Prod" DisplayName="Fair Prod" Square150x150Logo="Assets\Edge-Square150x150Logo.scale-400.png" Square44x44Logo="Assets\Edge-Square44x44Logo.scale-400.png" VisualGroup="FCA"></uap3:VisualElements> </Application> But when removing the ".scale-400" part of the files, the icons would not appear. Anyone knows what I am doing wrong here?
MSIX Packaging Tool Crash: Error code: 0x80131500
I am experiencing an MPT crash on several of our 23h2 Win 11 sequencer’s. MPT version 1.2024.405.0 Issue Presentation: 1. When Options gear cog is clicked MPT crashes with “unknown Error” log below 2. MPT GUI disappears during a standard package commencement workflow. A work around: 1. Resetting the MPT: Navigate to "installed apps" and rest the MPT once reset re-configure the MPT tool like first time it was installed. The error code has been reported in MSIX forum on several posts from 2020 onwards resulting from different inputs. A definitive fix has not been alluded to. MPT Log: [10/12/2024 12:03:28] [Error] Error Occurred: Newtonsoft.Json.JsonSerializationException: Error getting value from 'CertificatePassword' on 'MsixPackagingTool.Common.Utils.SigningInput'. --->[10/12/2024 12:03:25] [Info] Microsoft (R) MsixPackagingTool Tool [10/12/2024 12:03:25] [Info] Copyright (C) 2024 Microsoft. All rights reserved. [10/12/2024 12:03:25] [Info] ************************************************************ [10/12/2024 12:03:25] [Info] MSIX Packaging Tool Launch [10/12/2024 12:03:25] [Info] ************************************************************ [10/12/2024 12:03:25] [Info] Log file is located under: %UserProfile%\AppData\Local\Packages\Microsoft.MSIXPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\Logs_6\Log.txt [10/12/2024 12:03:25] [Info] Tool Version: 1.2024.405.0 [10/12/2024 12:03:25] [Info] Feedback logs are located under: %UserProfile%\AppData\Local\Packages\Microsoft.MSIXPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\FeedbackLogs\Logs_6 [10/12/2024 12:03:25] [Debug] Attempting to read settings file: %UserProfile%\AppData\Local\Packages\Microsoft.MSIXPackagingTool_8wekyb3d8bbwe\LocalState\settings.xml [10/12/2024 12:03:25] [Debug] Updating the settings file from version 1.2024.405.0 to a newer version. [10/12/2024 12:03:25] [Debug] Enabling Telemetry [10/12/2024 12:03:26] [Debug] Tool install location: C:\Program Files\WindowsApps\Microsoft.MSIXPackagingTool_1.2024.405.0_x64__8wekyb3d8bbwe [10/12/2024 12:03:27] [Debug] Open MSIX Settings [10/12/2024 12:03:27] [Debug] ************************************************************ [10/12/2024 12:03:27] [Debug] Settings [10/12/2024 12:03:27] [Debug] ************************************************************ [10/12/2024 12:03:28] [Error] Error Occurred: Newtonsoft.Json.JsonSerializationException: Error getting value from 'CertificatePassword' on 'MsixPackagingTool.Common.Utils.SigningInput'. ---> System.Security.Cryptography.CryptographicException: Key not valid for use in specified state. at MsixGenerator.Utils.DataProtectionHelper.Decrypt(String protectedData) at GetCertificatePassword(Object ) at Newtonsoft.Json.Serialization.DynamicValueProvider.GetValue(Object target) --- End of inner exception stack trace --- at Newtonsoft.Json.Serialization.DynamicValueProvider.GetValue(Object target) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.CalculatePropertyValues(JsonWriter writer, Object value, JsonContainerContract contract, JsonProperty member, JsonProperty property, JsonContract& memberContract, Object& memberValue) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty) at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.Serialize(JsonWriter jsonWriter, Object value, Type objectType) at Newtonsoft.Json.JsonSerializer.SerializeInternal(JsonWriter jsonWriter, Object value, Type objectType) at Newtonsoft.Json.JsonConvert.SerializeObjectInternal(Object value, Type type, JsonSerializer jsonSerializer) at MsixPackagingTool.Common.SettingsFile.SettingsInput.CopyPropertiesFromOther(SettingsInput settingsInput) at MsixPackagingTool.ViewModel.SettingsWorkflow.MasterSettingsEditorViewModel..ctor(ViewStateOrchestrator orchestrator, ViewStateOrchestrator parentViewStateOrchestrator, SettingsInput masterSettingsInput) at MsixPackagingTool.Model.Common.ViewStateOrchestrator.CreateMainWindowPage() [10/12/2024 12:03:37] [Debug] ************************************************************ [10/12/2024 12:03:37] [Debug] Closing MSIX Packaging Tool [10/12/2024 12:03:37] [Debug] ************************************************************
File Redirection crashes on Windows 11 24H2
I have noticed that some applications deployed with MSIX packages and having file redirection fixups can be correctly launched on Windows 11 22H2 or 23H2, but crash on Windows 11 24H2. If Config.json contains a snippet: "fixups": [ { "dll": "FileRedirectionFixup.dll", "config": { "redirectedPaths": { and a MSIX package integrates the latest PSF release (version 1.0.240212.1), applications crashes during initialization, and the Event Viewer contains these errors: Faulting module name: FileRedirectionFixup64.dll, version: 0.0.0.0, time stamp: 0x63f88f2e Exception code: 0xc0000005 Fault offset: 0x0000000000009809 Faulting process id: 0x2688 File redirection seems to work well with previous Windows builds. What is the cause of this error? Why is it observed only on Windows 24H2? Are FileRedirectionFixup64.dll assemblies released with PSF 1.0.240212.1 or earlier PSF versions compatible with Windows 11 24H2? Can PSF vendors and MSIX experts shed light on this problem?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 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.
