PSDriveInfo is null for Get-Item -Path <provider qualified path>

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

I’m implementing a custom cmdlet provider and stumbled upon an issue with provider qualified path:

• When getting an item with a rooted path like drive:/path/to/item the provider instance has assigned a PSDriveInfo instance on invocation by the base provider.
• When getting an item with a provider qualified path: provider\qualified::drive:/path/to/item the provider is invoked without having a PSDriveInfo instance assigned.

Within the provider I can compensate by parsing the drive name from the path and fetch the drive info from the session state: SessionState.Drive.Get("drive").

Also this changes the returned item which can be observed by the user:

• Get-item C:\ | fl * shows a PSDrive property.
• 'Get-item “Microsoft.PowerShell.Core\FileSystem::c:\ | fl *” doesn’t show a PSDrive property.

I’ve debugged this with the code base for v7.2.6 and it look to me that LocationGlobber.GetProviderPath(..) should return the drive info in this case as well or should be called a second time with the provider name removed from the paths maybe?

Expected behavior

PS> (get-item "Microsoft.PowerShell.Core\FileSystem::c:\").PSDrive -eq $null
False

Actual behavior

PS> (get-item "Microsoft.PowerShell.Core\FileSystem::c:\").PsDrive -eq $null
True

Error details

No response

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.6
PSEdition                      Core
GitCommitId                    7.2.6
OS                             Microsoft Windows 10.0.19043
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

[wgross]

I see, thank you!

[iSazonov]

This is definitely a departure from basic PowerShell concepts. Fixing this was declined in #5785.