I'm not sure if this is the correct forum, but I have a Windows 8.1 workstation, not domain joined, and I can't see my mapped drives in powershell ISE.  I'm trying to open a script for editing that resides on a server, I have the drive mapped in Windows explorer, but when I try to access that drive in the ISE it is not there, If I type it in I get the message that Windows cannot find the location. Even from the powershell console I can't CD to the drive.. Has anyone seen this? 

Thanks

Update, I can connect if I use the UNC name, but have to supply credentials again even though I already connected when I mapped the drive.... 

I may have spoken too early, it let me get to the location, but has not opened the script, ISE is now (Not Responding)

• Edited by Bryan99 Wednesday, January 15, 2014 2:41 PM

Hi,

As what you mentioned that you can get the Network drive mapped by UNC name, but the credential is required. Would you please let me know what name you use in script to map drive bring you the issue?

Here I just would like to share you that you can save the credential locally on your computer by Credential Manager

Please type "Credential Manager" in the Windows Search and add a generic credential:

Address: \\NetworkAttachedName

Login: \LoginName

Pass: ******

For the PowerShell ISE stopped working issue, please upload the event log and app crash dump file for powershell_ise.exe for further research.

First enable app crash dump collection by copying following words into notepad, saving it as dump.reg and importing it:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\localdumps\powershell_ise.exe]

"DumpFolder"=hex(2):63,00,3a,00,5c,00,63,00,72,00,61,00,73,00,68,00,64,00,75,\

  00,6d,00,70,00,73,00,00,00

"DumpCount"=dword:00000010

"DumpType"=dword:00000001

"CustomDumpFlags"=dword:00000000

Then, please repro the issue. If No response error appears, please find the crashdump file under c:\.

Look forward to your response.