Symlinks made by WinGet break when Windows Terminal is launched through PowerToys Run

[getchoo]

Microsoft PowerToys version

0.79.0

Installation method

PowerToys auto-update

Running as admin

No

Area(s) with issue?

PowerToys Run

Steps to reproduce

• Install package that WinGet creates links for (fnm is an example)
• Use PowerToys Run to launch Windows Terminal
• Attempt to use CLI command

✔️ Expected Behavior

The links WinGet creates will be usable whenever using them in Windows Terminal/Powershell

❌ Actual Behavior

After Windows Terminal is launched with PowerToys Run:

Powershell produces the following error when running the exe directly

ResourceUnavailable: Program 'fnm.exe' failed to run: An error occurred trying to start process 'C:\Users\setha\AppData\Local\Microsoft\WinGet\Links\fnm.exe' with working directory 'C:\Users\setha'. No application is associated with the specified file for this operation.At line:1 char:1
+ fnm --help
+ ~~~~~~~~~~.

The error from the command that's run in my $PROFILE seems to provide a bit more insight into what's going on here

ResourceUnavailable: C:\Users\setha\Documents\PowerShell\Microsoft.PowerShell_profile.ps1:1
Line |
   1 |  fnm env --use-on-cd | Out-String | Invoke-Expression
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Program 'fnm.exe' failed to run: An error occurred trying to start process
     | 'C:\Users\setha\AppData\Local\Microsoft\WinGet\Links\fnm.exe' with working directory 'C:\Users\setha'. The path
     | cannot be traversed because it contains an untrusted mount point.At
     | C:\Users\setha\Documents\PowerShell\Microsoft.PowerShell_profile.ps1:1 char:1 + fnm env --use-on-cd | Out-String
     | | Invoke-Expression + ~~~~~~~~~~~~~~~~~~~.

This does not happen when launching Windows Terminal directly or when using the Win+X menu

Other Software

WinGet v1.7.10582
Powershell v7.4.1
Windows Terminal v1.19.10573.0

[rdotts]

I'm also getting this with PowerToys 0.82.1 and both Powershell 5.1.22621.3672 and 7.4.2. As above, it results in an "untrusted mount point" error, but running Terminal from e.g. the start menu works fine. It also throws the error when using a keyboard shortcut reassignment to run "wt.exe".

Getting the direct path with "(Get-Target C:\users\USERNAME\AppData\Local\Microsoft\WinGet\Links\PROGRAM.exe).target" also works fine, as one would expect if the symlink is the issue.