Please feel free to provide feedback or file bugs here.

ActiveDirectory PSDrive problem with PSReadline in Windows 10

I am experiencing an issue with Windows 10 and the PSReadline module. Apparently when the PSReadline module is in memory, the default behavior for tab completion is to append a trailing backslash to the relative path. This is not too much of a problem with the file provider and the registry providers but it appears to wreak havoc on the Active Directory PS Provider.

This may be reproduced by navigating to the AD: drive and they trying to use tab completion for the Set-Location or Get-ChildItem cmdlets. You will receive the error Cannot find path because it does not exist.

The two workarounds are to use the backspace key to manually remove the trailing backslash or run Remove-Module PSReadline.

3 votes
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Robert McDonnell shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

Hi Robert,

Thanks for the report! I went ahead and opened an issue in the PSReadline GitHub repo to track this: https://github.com/lzybkr/PSReadLine/issues/473

I propose that it might be worth it to simply special case PSReadline to not append a trailing backslash while in the AD provider, but I think you should probably also file something on the AD team’s UserVoice to support trailing backslashes (though this work might be more difficult): https://windowsserver.uservoice.com/forums/304621-active-directory

Thanks,
Joey

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base