Forum Discussion
MSIX Package working on 23H3 but not 24H3: System.Numerics.Vectors conflict
- Jan 06, 2025
Being the developer, I managed to work around the issue with a change to the application. But the underlying issue that made the app not work on 24H2 would still exist for other apps.
I also enabled the fusion log. Entries on the exception are shown here:
=== Pre-bind state information === LOG: DisplayName = System.Numerics.Vectors, Version=4.1.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (Fully-specified) LOG: Appbase = file:///C:/Program Files/WindowsApps/TMEditX_5.3.0.16_x64__k7hsda8r3p9s2/ LOG: Initial PrivatePath = NULL Calling assembly : Microsoft.Windows.Appx.PackageManager.Commands, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35. === LOG: This bind starts in default load context. LOG: No application configuration file found. LOG: Using host configuration file: LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config. LOG: Post-policy reference: System.Numerics.Vectors, Version=4.1.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a LOG: Attempting download of new URL file:///C:/Program Files/WindowsApps/TMEditX_5.3.0.16_x64__k7hsda8r3p9s2/System.Numerics.Vectors.DLL. WRN: Comparing the assembly name resulted in the mismatch: Build Number ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.
This seems to point to PackageManager.commands (for access to the AppXPackage class returned by the powershell module).