Error "Failed to get known folder path" Launching App

[NickDorak]

I have built a new MSIX package using PsfTooling. All built successfully using recomendations provided by app. I then converted to VHD and published to AVD for testing. I have several apps in this package that require command line arguments to run, so PsfTooling setup some PsfLauncher apps to make it happen.

Apps in this MSIX package that don't use PsfLauncher run successfully, however any application that uses PsfLauncher only launch an OK box and never run the intended app...
Title: Package Support Framework
Message: Failed to get known folder path
Choices: OK

Any suggestions would be appreciated.

[TimMangan]

Nick,

Can you confirm the version of PsfTooling (and store or direct download from my site)?

It would also be helpful if you could test the MSIX package directly (without conversion) and/or share details on how it was converted to VHD and/or share the package with me (email tmangan@tmurgent.com) to investigate.

Regards,

Tim

[NickDorak]

I am using version 5.2.0 from your site as it was newer than 5.0.0 from the store.

The app I built is 1.2G (may be a little large for email) and requires connection to an internal network server (won't work on different network).

I use the following to convert to VHD...
$MsixFile = "C:\MSIX\PACKAGENAME_1.2.2.0_x64__by3skzpm54k1e.msix"
$MsixManager = "C:\MSIX\msixmgr"
$VhdPath = $MsixFile.replace(".msix",".vhd")
$Size = ([math]::round((Get-Item $MsixFile).length /1MB) * 3 ) *1MB #size must be in KB but 1MB increments
New-VHD -SizeBytes $Size -Path $VhdPath -Dynamic -Confirm:$false -Verbose
$VhdObject = Mount-VHD $VhdPath -Passthru
$Disk = Initialize-Disk -Passthru -Number $VhdObject.Number
$Partition = New-Partition -AssignDriveLetter -UseMaximumSize -DiskNumber $Disk.Number
Format-Volume -FileSystem NTFS -Confirm:$false -DriveLetter $Partition.DriveLetter -Force
$Destination = New-Item -Path ($Partition.DriveLetter + ":\") -Name "MSIX" -ItemType Directory
Set-Location ($MsixManager + "\x64\")
.\msixmgr.exe -Unpack -packagePath $MsixFile -destination $Destination.FullName -applyacls
Dismount-VHD $VhdPath

[NickDorak]

So I tried the manual MSIX install and I get the same "Failed to get known folder path" error when running the shortcut that has arguments.

Now, here's an even stranger part. When I tried some other shortcuts, I got the following error...
C:\Users\Tim\source\repos\MSIX-PackageSupportFramework\PsfLauncher\main.cpp(443)\PsfLauncher5.exe!006A1C29: (caller: 006A08EF) Exception(1) tid(1b68) 800704C7 The operation was canceled by the user.
Msg:[Error starting monitor using ShellExecuteEx]
The strange part is that the error is referring to a user "Tim", which isn't me or the account I used to create the package.

[TimMangan]

OK. So good to eliminate the VHD conversion from the mix. The Path shown in that error is the path from the build system, so no biggie there.

That the launcher was using ShellExecuteEx indicates that the target executable in the Json for PSFLAUNCHERFive is not an exe. This means that the launcher will want to use whatever program is registered for that file extension type. Can you extract and post the config.json file from the package? It will be helpful to know if this file (or URL) is local to the package or external and what FTA we are talking about.

Another avenue that could help would be to build the package using PsfToolingD shortcut instead of the release build. Then when you run the test, you can capture debug output using the SysInternals DebugView app and save/send the output to me. But let's start with the json file.

I've seen a couple of apps with non exe shortcuts, especially to documents, have issues that I that I've addressed in yet-to-be released PSF code. So we might just get lucky with that.

[NickDorak]

Thanks Tim, I have emailed you the JSON and Manifest files for the package.

[TimMangan]

Note: This issue was fixed in an update around May/June 2022, we just forgot to post it here.