You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we use the Microsoft Package Support Framework (PSF) shipped with MSIX to run some pre launch scripts on some applications, we got this error when the application launches after installation:
This error is already described on the following URL ([https://techcommunity.microsoft.com/t5/msix/psflauncher64-exe-the-system-cannot-find-the-file-specified/m-p/3274042]) by Tim Mangan and is already fixed in Tim's PSF more than a year ago.
In our environment we don't have the feature Windows PowerShell 2.0 installed and therefore we don't have the key: [HKEY_LOCAL_MACHINE\Software\Microsoft\PowerShell\1]
Installed = 1
As Tim mentioned in the article above, this is a bug which is still in the Microsoft PSF, where the PSF can't determine whether PowerShell is installed or not.
Can the solution from Tim's PSF also be incorporated into the Microsoft PSF?
The text was updated successfully, but these errors were encountered:
When we use the Microsoft Package Support Framework (PSF) shipped with MSIX to run some pre launch scripts on some applications, we got this error when the application launches after installation:
This error is already described on the following URL ([https://techcommunity.microsoft.com/t5/msix/psflauncher64-exe-the-system-cannot-find-the-file-specified/m-p/3274042]) by Tim Mangan and is already fixed in Tim's PSF more than a year ago.
In our environment we don't have the feature Windows PowerShell 2.0 installed and therefore we don't have the key: [HKEY_LOCAL_MACHINE\Software\Microsoft\PowerShell\1]
Installed = 1
As Tim mentioned in the article above, this is a bug which is still in the Microsoft PSF, where the PSF can't determine whether PowerShell is installed or not.
Can the solution from Tim's PSF also be incorporated into the Microsoft PSF?
The text was updated successfully, but these errors were encountered: