Forum Widgets
Latest Discussions
Using MSIX to install a Windows service
Two questions: Is it possible to have a MSIX setup which contains just a Windows service? Is it possible to prepare such setup so that it installs it's service when run by regular user (with no Administrative privileges)?Solveda-okrasinskiFeb 14, 2025Copper Contributor168Views0likes2Comments
The strange problem of C # program calling C++dll
My C # calls C++DLL and runs it directly in VS2022 without any errors. We use LoadLibrary to load DLLs. Packaged as. msix package, after installation, click on the icon of the application to run, some DLLs, error message Error code 126 or 0. But running this. exe file directly in the installation directory (Windows apps/applications) does not generate any errors. I don't know where the problem lies now? How to solve it?Solvedbill_quFeb 14, 2025Copper Contributor151Views0likes5CommentsSingle MSIX package containing two parts: requiring/not requiring administrator privileges to run
My software consists of two parts: A and NA. Part A requires administrative rights to run. Part NA does not require administrative rights to run. I need to have a single MSIX installation for both parts. I have following questions: 1. Can such an installation be built? 2. Can the A part be installed (not run after installation, but installed) without administrative privileges? 3. Is there a sample/tutorial/documentation where this situation is covered?Solveda-okrasinskiFeb 10, 2025Copper Contributor114Views0likes2CommentsSigning MSIX packages with Azure Trusted Signing Accounts
I have a requirement to sign an MSIX package without access to a code signing certificate. I have successfully signed a powershell script using the Azure Trusted Signing Account: https://learn.microsoft.com/en-us/azure/trusted-signing/how-to-signing-integrations however when trying to sign either an exe of MSIX, i receive the signtool error: This file format cannot be signed because it is not recognized. Whereas the signtool documentation clearly states that .appx / .msix packages can be signed with this crypto tooling. There is no additional information in the AppX event viewer operational or debug areas that I can see. I have ensured that the publisher details match that of the certificate profile listed under the Trusted Signing Account resource in the Microsoft Packaging Tool, albeit I set a application specific publisher display name instead. Has anyone had any success using this process?SolvedGrahamGBJan 31, 2025Iron Contributor619Views0likes11Comments
Run a program included in a MSIX package from the package program entry point.
Hello. I've created an MSIX package that contains two programs: P1.EXE and P2.EXE. P1.EXE is the application entry point and it works ok. At some point of P1.EXE execution, P1.EXE runs P2.EXE. This works ok if application capabilities is defined as "Full Trust" but I don't want to have such a global access. Please help me to stablish the proper 'applicaction capabilities' combination than will allow P1.EXE to run P2.EXE Thanks in advance. VicenteSolvedVicGarJan 10, 2025Copper Contributor160Views0likes2CommentsMSIX 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.Solved416Views0likes2Comments
PsfLauncher and shortcut to url
Did not yet tried myself, but does anyone know if it is possible to create a MSIX shortcut, which does start a url to e.g. http://www.google.com using the default browser? Maybe with psflauncher and config.json configuration? I now use a cmd, containing ‘start https://www.google.com’, which does work. But maybe this can we made easier?SolvedPollewopsDec 12, 2024Iron Contributor126Views0likes2CommentsMSIX write HKLM in the bubble?
Already trying for some days, but can't make it work. Or is it not possible al all? I have MSIX in which (in the bubble!!!) i want to set hkcu and hklm registry settings. For hkcu it is working, but hklm is not writable. What i do wrong or is this not possible at all? I first want to know if it should be possible. If so, i can share my psflauncher and config.json config files.SolvedPollewopsDec 02, 2024Iron Contributor316Views1like7Comments
MSIX Packaging Tool 1.2024.405.0 Release available
There is a new release of the MMPT available in the Microsoft store. It is version 1.2024.405.0. The release notes may be found at MSIX Packaging Tool release notes - MSIX | Microsoft Learn . Seems mostly about updates to what they can do with their version of the PSF. Note: There is also a newer release build (1.2024.508.0) in the MMPT insider program mentioned on the page above. This would seem to be the support for the long awaited change to Azure Code Signing from the V2 to the new version that has been in preview mode itself for a long time. Perhaps that means we'll see GA on that soon.Solved676Views0likes1CommentNew version of MSIX Packaging Tool and WIndows App Runtime Dependency
Attention MSIX Packaging Tool team and Fiza_Azmi Reported to me by two different Microsoft customers. The latest version of the MSIX Packaging Tool seems to automatically add a package dependency for the WindowsApp_Runtime package, even when packaging an app that does not use the Windows SDK. This should not be in those packages, and while this should not block customers, it is causing them issues in situations where that package has not already been installed separately and automatic locating the package for installation in blocked. The tool should only add that dependency if the dlls associated with the WindowsApp sdk are in the package.Solved2KViews2likes3Comments
Resources
Tags
- MSIX73 Topics
- appinstaller7 Topics
- msix packaging tool7 Topics
- APPX5 Topics
- MSIX Packaging Tools4 Topics
- appattach3 Topics
- MSIX AppAttach launch failure3 Topics
- Access MSIX Container3 Topics
- MSIX LIMITATIONS3 Topics
- UWP3 Topics