Forum Discussion
New-SMBMapping not showing in Explorer until Explorer process is closed/restarted
I'm writing a script to remap drives to new paths (file server migration), and I had everything working. I'm using Remove-SMBMapping and New-SMBMapping. While it was working there was a strange ...
You could try using the New-PSDrive cmdlet. i.e.
New-PSDrive -Name X -Root \\Fileserver\Share -PSProvider FileSystem
This creates a mapping which is visible in Windows Explorer straight away, you can use the -Persist parameter to make it permanent. The New-SMBMapping is for the PowerShell session itself until it closes?
New-PSDrive -Name X -Root \\Fileserver\Share -PSProvider FileSystem
This creates a mapping which is visible in Windows Explorer straight away, you can use the -Persist parameter to make it permanent. The New-SMBMapping is for the PowerShell session itself until it closes?
- No change. Anything I do within Powershell with drive letters is not reflected in the Explorer process.
Note: I am using Windows 11.
Further, I remember running into this problem a few months back but it only surfaced if I ever launched the script via the PS file from Explorer. If I launched it directly in Powershell, or simply manually typed the commands in Powershell it worked as expected. Now, all of a sudden, no matter what I do, if it's done in Powershell, Explorer will not see the change until it is restarted.- I'm also using Windows 11, I typed the command in a Windows Terminal and.. Now it doesn't work for me also.. PowerShell 5 and 7 in Windows Terminal, but also from a script file... Which it did yesterday...I don't get it 🙂
- I'm glad I'm not the only one!!!
