Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

With 7.4.0-preview.6 (using PSReadLine 2.3.3 FWIW; also in 7.4.0-preview.5) I get this unexpected result when entering //pnjnas/pi/jee<TAB>:

//pnjnas/pi/\jeedom\

That kind of path causes a number of failures with most of my scripts.

With 7.3.7 or 7.4.0-preview.4, the same action results in a usable expansion:

\\pnjnas\pi\jeedom\

Expected behavior

Expansion should either expand everything with forward slashes (to match the "input style") or convert all slashes to backslashes (probably the latter for backwards compatibility / consistency with the Windows conventions).

\\pnjnas\pi\jeedom\

Actual behavior

the //server/share part of the pathspec is not converted to "Windows canonical form with backslashes":

//pnjnas/pi/\jeedom\

Error details

No response

Environment data

PSVersion                      7.4.0-preview.6
PSEdition                      Core
GitCommitId                    7.4.0-preview.6
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

No response