Forum Widgets
Latest Discussions
MSIX HKLM not read
I have created an MSIX application and the application does capture some registry data in: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Odyssey\Starter Now when starting this application I see this in procmon: When I create the required registry data 'outside' the MSIX package in the local HKLM registry, the application works fine. What is going on here? Is this default behavior or do i miss here something? I think this is already some while ago mentioned in the following thread, but did not see any update so far:msix HKLM key not read | Microsoft Community Hub Anyone who can clear this behavior for me and how to fix this?
msix HKLM key not read
I have an issue with my repackaged MSIX. A HKLM key under WOW6432node with my servername is not read. when i open the CMD within the bubble and i start the program, the key is read. But when starting it with the Shorcut it doesn't. Tried several PSF fixes but still not working, anyone an idea? thanksMSIX Package working on 23H3 but not 24H3: System.Numerics.Vectors conflict
NOTE: There may be multiple issues that match the generic "MSIX packages that work on Windows 11 23H3 fail upon launch on 24H2". This is a specific issue and anyone with different symptoms should start a new issue rather than jump onto this one. I have an MSIX package that consists of three applications, all built using .Net Framework 4.8.1. The package works great on Windows 10, and Windows 11 22H2 and 23H2. On Windows 11 24H2 the package fails as one of the three applications crashes without UI appearing. In one case, I tested the app installed on 23H2 successfully and after installing the OS upgrade to 24h2 the application now fails. The symptoms are that the crash occurs early, apparently before the mainwindow initializes, a WerFault occurs, and there is an interesting event in the Windows Logs/Application file. My analysis of the situation is that there is a new conflict in System.Numerics.Vectors versions that did not cause an issue on the earlier OS builds I tested. All three applications in the package use checkboxes in the mainpage.xaml. It appears to me from the dump file that this wants to use System.Numerics.Vectors 4.1.4.0. A difference in the problem app from the other two in the package (which also use checkboxes) is that the app uses the NuGet package PowerShellStandardLibrary 5.1.1. This library claims no dependencies have noticed it needs a newer version of System.Numerics.Vectors anyway. The package has the NuGet package System.Numerics.Vectors 4.6.0 installed in two of the three applications in the package, including the broken app and one app without the issue (which is not using the PowerShell library). The interesting event recorded is from .Net Runtime, EventId=1026. Log Name: Application Source: .NET Runtime Date: 12/22/2024 3:42:23 PM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: VS2023.TMU.int Description: Application: MSIXDeploy.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileLoadException at WinRT.Projections..cctor() Exception Info: System.TypeInitializationException at WinRT.Projections.RegisterAbiDelegate(System.Type[], System.Type) at WinRT.AbiDelegatesInitializer.InitalizeAbiDelegates() at <Module>..cctor() Exception Info: System.TypeInitializationException at MSIXDeploy.MainWindow.ApplyFilterToList(Boolean) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.Controls.Primitives.ToggleButton.OnIsCheckedChanged(System.Windows.DependencyObject, System.Windows.DependencyPropertyChangedEventArgs) at System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs) at System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs) at System.Windows.DependencyObject.NotifyPropertyChange(System.Windows.DependencyPropertyChangedEventArgs) at System.Windows.DependencyObject.UpdateEffectiveValue(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata, System.Windows.EffectiveValueEntry, System.Windows.EffectiveValueEntry ByRef, Boolean, Boolean, System.Windows.OperationType) at System.Windows.DependencyObject.SetValueCommon(System.Windows.DependencyProperty, System.Object, System.Windows.PropertyMetadata, Boolean, Boolean, System.Windows.OperationType, Boolean) at System.Windows.Baml2006.WpfMemberInvoker.SetValue(System.Object, System.Object) at MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetValue(System.Object, System.Xaml.XamlMember, System.Object) Exception Info: System.Windows.Markup.XamlParseException at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri) at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri) at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri) at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean) at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext) at System.Windows.Application.DoStartup() at System.Windows.Application.<.ctor>b__1_0(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at MSIXDeploy.App.Main() Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2024-12-22T20:42:23.1118353Z" /> <EventRecordID>757</EventRecordID> <Correlation /> <Execution ProcessID="10692" ThreadID="0" /> <Channel>Application</Channel> <Computer>VS2023.TMU.int</Computer> <Security /> </System> <EventData> <Data>Application: MSIXDeploy.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileLoadException at WinRT.Projections..cctor() Exception Info: System.TypeInitializationException at WinRT.Projections.RegisterAbiDelegate(System.Type[], System.Type) at WinRT.AbiDelegatesInitializer.InitalizeAbiDelegates() at <Module>..cctor() Exception Info: System.TypeInitializationException at MSIXDeploy.MainWindow.ApplyFilterToList(Boolean) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.Controls.Primitives.ToggleButton.OnIsCheckedChanged(System.Windows.DependencyObject, System.Windows.DependencyPropertyChangedEventArgs) at System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs) at System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs) at System.Windows.DependencyObject.NotifyPropertyChange(System.Windows.DependencyPropertyChangedEventArgs) at System.Windows.DependencyObject.UpdateEffectiveValue(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata, System.Windows.EffectiveValueEntry, System.Windows.EffectiveValueEntry ByRef, Boolean, Boolean, System.Windows.OperationType) at System.Windows.DependencyObject.SetValueCommon(System.Windows.DependencyProperty, System.Object, System.Windows.PropertyMetadata, Boolean, Boolean, System.Windows.OperationType, Boolean) at System.Windows.Baml2006.WpfMemberInvoker.SetValue(System.Object, System.Object) at MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetValue(System.Object, System.Xaml.XamlMember, System.Object) Exception Info: System.Windows.Markup.XamlParseException at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri) at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri) at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri) at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean) at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext) at System.Windows.Application.DoStartup() at System.Windows.Application.<.ctor>b__1_0(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at MSIXDeploy.App.Main() </Data> </EventData> </Event> I took a full dump (available upon request), and the analysis points to code the crash occurring in code that is processing in System.Windows.Markup.WpfXamlLoader:Load and an inner exception says Name Value Type ◢ InnerException {"Could not load file or assembly 'System.Numerics.Vectors, Version=4.1.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)":"System.Numerics.Vectors, Version=4.1.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"} System.Exception {System.IO.FileLoadException} I am pretty much out of my element in debugging XAML processing, but this pretty much smells like a Microsoft bug in an OS supplied component. Feel free to reach out to me for the dmp file or MSIX package if you'd like it.
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 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?
