Every time I'm away from the location where my mapped (to S:\) network drive is located (and thus inaccessible), the PowerShell ISE stalls in the "Loading..." screen.
The profile.ps1 never gets a chance to run because the PowerShell ISE never escapes from the Loading... screen.
The normal PowerShell prompt works fine, but I doesn't provide all the nice features of the PowerShell ISE, so I would like to find a way to get the PowerShell ISE to work when I'm away from the physical location where the mapped network drive works.
If I remember to unmap the network drive before I leave that location, everything is fine. It's when I forget to unmap the drive prior to shutting down and moving to a different location that this problem rears its ugly head.
It's as if the PowerShell ISE is trying to access the underlying UNC \\whatever\something\ even though there is no hope of doing so if I'm physically away from the location where that UNC exists.
Is there some way to fix this issue that doesn't involve reinstalling Windows 10 Enterprise 64-bit?