Windows PowerShell Home
Subst mapping not detected
4/19/2013 1:02:17 AM
User(s) can reproduce this bug
1.) We're creating local folder and use Subst to map it as H: drive (fake temporary home)
2.) Array of available PSDrives is NOT updated when subs is being used. That means that even though H:\ is mapped properly (I can see that outside of a Powershell) and it's detected properly when Powershell is restarted, it won't be dynamically added to list of available PSDrives for current session.
How often does this happen?
Have you seen this problem before in this product?
I do not know if this issue existed previously
1.) Use Subst to map folder as drive
2.) Try to execute Get-PSDrive from the same session
New drive is NOT visible and not available when accessed directly. New drive IS available from outside of this Powershell session.
3.) Open new Powershell session
4.) Try to execute Get-PSDrive from this new session
New drive is visible and available
In both cases, mapped drive should be visible and available to the end users
to post a comment.
Please enter a comment.
to post a workaround.
Please enter a workaround.
on 4/19/2013 at 1:06 AM
As a current workaround, I'm running New-PSDrive after Subst operation:
New-PSDrive -Name $DriveLetter -PSProvider FileSystem -Root "$($DriveLetter):\"
However, when this drive is removed (Subst $DriveLetter /d), it is NOT removed from list of PSDrives!
© 2013 Microsoft