Clarify that AppX reparse points do not support listing their targets anymore in v7.2+ #10168
Closed
3 tasks done
Labels
area-management
Area - Microsoft.PowerShell.Management module
area-providers
Area - PowerShell providers
issue-doc-bug
Issue - error in documentation
Prerequisites
Get-Foo
cmdlet" instead of "Typo."Links
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_FileSystem_Provider?view=powershell-7.4
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_FileSystem_Provider?view=powershell-7.3
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_FileSystem_Provider?view=powershell-7.2
https://learn.microsoft.com/en-us/powershell/module/Microsoft.PowerShell.Management/Get-ChildItem?view=powershell-7.4
https://learn.microsoft.com/en-us/powershell/module/Microsoft.PowerShell.Management/Get-ChildItem?view=powershell-7.3
https://learn.microsoft.com/en-us/powershell/module/Microsoft.PowerShell.Management/Get-ChildItem?view=powershell-7.2
Summary
Support for determining the targets of AppX reparse points (aka AppExecLinks, such as
winget
/ Microsoft Store-installed applications) was removed in v7.3, and, according to @sdwheeler, back-ported to v7.2Details
The upshot for AppX reparse points in v7.2+ is:
They no longer print their target after
->
in the formatted output.->
part PowerShell/PowerShell#19794 suggests eventually removing->
too.Their type-native
.LinkTarget
property and their ETS.LinkType
and.Target
properties (an alias of.LinkTarget
) are all$null
; the type-native.ResolvedTarget
property now returns the reparse point's own full path.Visually, the
l
as the first character in theMode
column is now the only indicator that the item is a reparse point.To programmatically identify an AppX reparse point now requires:
$item.Attributes.HasFlag([System.IO.FileAttributes] 'ReparsePoint') -and $null -eq $item.LinkType
$item.Mode -like 'l*' -and $null -eq $item.LinkType
Suggested Fix
It's probably worth mentioning at least a condensed version of the above in the linked topics.
The text was updated successfully, but these errors were encountered: