Apr 01 2022 01:50 PM
Apr 01 2022 01:50 PM
We use the Package Support Framework on some our applications shipped with MSIX to run some post installation scripts.
We have had a few users that have gotten the above error when the application launches after installation. Please excuse the German; it translates to "The system cannot find the specified file".
We are unfortunately unable to reproduce the issue on any of our machines/virtual-machines and haven't been able to figure out what is going on with this small minority of users.
My only hunch is that there is some incompatibility with their PowerShell versions or system architecture. We have made it clear that our application only runs on x64 architectures, as we have not included the PSF 32-bit executables and libraries along with the MSIX package.
Is it possible that some people can be running windows on x64, but require 32-bit versions of PSF? If so that is an easy fix but I haven't been able to confirm.
Any help/information would be much appreciated. If it is not something we can fix on our side of things I would like to at least help these users get the issue resolved through our support process.
Thanks in advance!
Apr 01 2022 04:24 PM
Apr 08 2022 07:18 AM
I think you misunderstood the question. I am the developer of the application, that is packaged as MSIX with the Package Support Framework. I have a number of users that cannot launch the application and they are getting the above error and I do not know why.
Apr 08 2022 07:51 AM
You actually have to go into your system hardware to change the writing on your hardware from 32 bit to 64, bit to be able to run the 64 bit programs there is other atrubutes you have to change. But i would not be able to give that information to you properly without seeing whats on your system.
Apr 08 2022 08:47 AM
Apr 08 2022 11:23 AM
Apr 14 2022 09:16 AM
I am aware of an old flaw in the detection logic used by the Psflauncher to determine if powershell is present on the system, and some of the user's systems might be affected. I have fixed that issue in my fork (https://github.com/TimMangan/MSIX-PackageSupportFramework).