Forum Discussion
MSIX Application Launch Failure: Exception Code 0xc0000005.
Hi everyone,
I'm facing an issue with an MSIX package where the application fails to launch, but the same application runs correctly when installed through its setup. I've thoroughly checked the installation, and all the required files seem to be present in the package. The only hint I have is the error message I received during debugging:
`
Application Name that generated the error:
MyAppWindows.exe, Version: 1.0.0.0, Timestamp:
0xcb0265d7
Module Name that generated the error:
TraceFixup32.dll, Version: Timestamp:
0x63f88fca
Exception Code: 0xc0000005
Error Offset: 0x000313c9
Process ID that generated the error: 0x0x67F()
Time of Application Start that generated
the error: 0x0x1D9AE8AA3071429
Application Path that generated the error:
C:\Program
Installer_l .O. I
AppData\MyAppWindows\MyAppWindows.exe
Module Path that generated the error: C:
\Program Files\WindowsApps\MyAppWindows-
Installer_l .().
\TraceFixup32.dll
Report ID:
6d5e4a0d-821a-408d-9e99-5d224b968919
Package Full Name that generated the error:
MyAppWindows-
Application ID related to the package that
generated the error: MYAPPWINDOWS
`
It appears that the application "MyAppWindows.exe" encounters an issue with the module "TraceFixup32.dll," resulting in an exception code of "0xc0000005," indicating an access violation error. This means the application is trying to access an invalid memory address, leading to the launch failure.
I've verified the MSIX package configuration, dependencies, and even examined the logs, but I couldn't find any clues to resolve this problem.
Has anyone encountered a similar issue with MSIX applications not launching? Any suggestions or insights to troubleshoot and fix this problem would be greatly appreciated.
Thank you in advance for your help!
The MfrFixup exists only in my fork of the PSF github/com/TimothyMangan (a long story not work rehashing here). But assuming that you are a developer and not including any files in your package under the VFS folder, then InstalledLocationVirtualization is the easiest way for you to solve the file write problem (if that is what your problem is -- you might still need to run ProcessMonitor).
InstalledLocationVirtualization (ILV for short) is a separate approach added by Microsoft to allow automatic redirection of attempts to overwrite files in the package. It doesn't always work by itself, but since it is just a few extra lines to add to the AppXManifest (shown below) it is easy to try.
In addition to the package-level extension (not application-level!) you'll need to ensure that the namespace for uap10 is included as a Package attribute at the top of the file (as in xmlns:uap10="..." and in the ignorable namespaces too).
<Package ....>
...
<Applications>
...
</Applications>
<Extensions>
<uap10:Extension Category="windows.installedLocationVirtualization">
<uap10:InstalledLocationVirtualization>
<uap10:UpdateActions ModifiedItems="keep" AddedItems="keep" DeletedItems="keep" /?
</uap10:InstalledLocationVirtualization>
</uap10:Extension>
</Extensions>
</Package>A reference for detail about ILV is in this white-paper MSIX InstalledLocationVirtualization (tmurgent.com) if you wanted to learn more about the ILV.
4 Replies
- TraceFixup from the PSF is only needed to help determine which fixups an application might require. I would expect that the error (a file permission issue) is actually due to the application call made which TraceFixup was monitoring. The could be due to accessing a file or registry key/value with permissions not allowed. These days, we usually determine what is needed using process monitor instead of the TraceFixup.
If the issue is file based, there are multiple solutions available, including the PSF FileRedirectionFixup (or newer MfrFixup), or adding the Package Extension "InstalledLocationVirtualization" to the AppXManifest file.
If the issue is registry based, the PSF RegLegacyFixup is usually called for.- Hello Timothy, I truly appreciate your time and expertise in addressing my problem. As a newcomer to this tool, I am still learning the ropes and trying to understand the best approach to resolve the file permission error. The information you provided about the PSF and its components, such as TraceFixup, has been enlightening.
Regarding the potential solutions you mentioned, including "PSF FileRedirectionFixup" and "InstalledLocationVirtualization," I would like to delve into their implementations. However, I must admit that "MfrFixup" has not been familiar to me in the context of PSF, and I wonder if it might have been a typo or if further clarifications are available.
As I proceed with this troubleshooting process, could you kindly guide me on where to begin? Should I focus on the AppXManifest file, or are there any other essential starting points you would recommend?
Thank you so much.The MfrFixup exists only in my fork of the PSF github/com/TimothyMangan (a long story not work rehashing here). But assuming that you are a developer and not including any files in your package under the VFS folder, then InstalledLocationVirtualization is the easiest way for you to solve the file write problem (if that is what your problem is -- you might still need to run ProcessMonitor).
InstalledLocationVirtualization (ILV for short) is a separate approach added by Microsoft to allow automatic redirection of attempts to overwrite files in the package. It doesn't always work by itself, but since it is just a few extra lines to add to the AppXManifest (shown below) it is easy to try.
In addition to the package-level extension (not application-level!) you'll need to ensure that the namespace for uap10 is included as a Package attribute at the top of the file (as in xmlns:uap10="..." and in the ignorable namespaces too).
<Package ....>
...
<Applications>
...
</Applications>
<Extensions>
<uap10:Extension Category="windows.installedLocationVirtualization">
<uap10:InstalledLocationVirtualization>
<uap10:UpdateActions ModifiedItems="keep" AddedItems="keep" DeletedItems="keep" /?
</uap10:InstalledLocationVirtualization>
</uap10:Extension>
</Extensions>
</Package>A reference for detail about ILV is in this white-paper MSIX InstalledLocationVirtualization (tmurgent.com) if you wanted to learn more about the ILV.
