Posts Tagged ‘drive letter’
Source Insight Cannot See Network Drives
Symptom: Source Insight cannot see network drives that are mapped to drive letters.
This caused by a feature in Windows that blocks mapped drives in processes running with elevated privileges when the drives are mapped from a lesser privilege process.
If you are running Source Insight from an "elevated" command prompt (for example an Administrator command prompt), or you always run Source Insight as Administrator, but you are mapping the drives in Windows Explorer, then Source Insight may not be able to see the mapped drives. This is a security feature of Windows: If you map a drive using Windows Explorer, an elevated Command Prompt (or any other elevated process) will not be able to see it.
Workarounds
- Map the drive from an Administrator command prompt, using the "
NET USE ...." command. After that, any elevated process should see the mapped drives. - Run Windows Explorer in Administrator mode and then map the drives.
- Always run Source Insight from a normal (non-admin) command prompt or Windows Explorer.
- View other workarounds from this Microsoft article: https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command
Here are some external articles about the topic:
Article: http://woshub.com/how-to-access-mapped-network-drives-from-the-elevated-apps/