Forum Discussion
MSIX Application Launch Failure: Exception Code 0xc0000005.
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.
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.
- Timothy, God Bless You!!!!
Following your instructions, I tried adding the new extensions to the existing "<Extensions>" section in my manifest file, but it resulted in a mysterious generic error, preventing me from creating the .msix package. However, in the end I tried to create a separate "<Extensions>" tree with "uap10" and resolved the problem magically, and now the software launches flawlessly.
As I mentioned before, I'm relatively new to programming, having embarked on this journey about six months ago. In the process of learning, I managed to develop a program using Winforms/C#. Your timely intervention saved me from what I thought was an impending catastrophe. I had invested countless hours, day and night, into developing the program, and it would have been disheartening to see it go to waste.
Now, next step, I'm facing some challenges related to writing files after the user enters the license information. The program seems to struggle with writing the necessary activation files in the same folder. As you know, I built it with the logic of Winforms applications, and it lacks the modern libraries required for automatic activation via the Windows Store. I will run some tests, but if I encounter any roadblocks, I plan to open a new topic addressing the permission issues.
It's individuals like you who make the programming community so special.
I feel truly blessed to have crossed paths with you on the Microsoft Forum, and I can't emphasize enough how much your help means to me.
Warmest regards