PR Summary

Fix #6232
Fix #13136

Fix New-Item fails to create file links or creates links pointing to incorrect locations when the target path contains wildcard characters.

Make the -Target and -Value parameters of New-Item treat the path as a literal.

PR Context

When using the New-Item command to create file links, if the target path contains wildcard characters, they are incorrectly interpreted. The following scenarios occur:

• When creating a hard link, if the link path is an absolute path, the creation will always fail.
• When creating a symbolic link:
  • If the wildcard characters in the link path are not escaped with a backtick, the creation will fail.
  • If the wildcard characters in the link path are escaped with a backtick, a link pointing to an incorrect path will be created.

• When creating a Junction, the situation is similar to the above.

Example:

New-Item lk21.txt -ItemType HardLink -Target 'D:\[test].txt'
# New-Item: Could not find item D:\[test].txt.

# The `Get-Item` command can correctly retrieve the file.
Get-Item -LP 'D:\[test].txt'
#    Directory: D:\
# Mode                 LastWriteTime         Length Name
# ----                 -------------         ------ ----
# -a---           2025/3/15    14:26              9 [test].txt

Now, the path is correctly parsed to create the link.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    - [ ] Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
      (which runs in a different PS Host).
      • Issue filed:
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
      • Issue filed:
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
      • Issue filed:
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
      • Issue filed: