Topic
Issue Summary
If encountering an issue where mapped network drives are not visible in the Botflow (for example, when using the Open Data action) or in the file selection dialog, even though they are visible and accessible in File Explorer.
Root Cause
Windows maps drives per user session, and elevated (administrator) processes do not automatically have access to mapped drives created in the normal user session. This session isolation affects any automation tool or RPA Bot running in an admin context.
How to Identify the Issue
User can see and access mapped drives manually in File Explorer
Botflow or file dialog fails to list or access mapped drives (e.g., K:, Y:)
Manually entering a UNC path (
\\server\share) often worksDrives disappear again after a reboot
Drag-and-drop into Open Data also fails, but UNC paths succeed
Elevated Command Prompt (
Run as Administrator) does not show the mapped drives:net use
Instructions
Enable Mapped Drives for Elevated Processes
Step-by-Step Instructions
Open the Registry Editor
- Press
Windows + R, typeregedit, press Enter
- Press
Navigate to the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\SystemCreate a new DWORD (32-bit) Value
Right-click the
Systemfolder → New → DWORD (32-bit) ValueName it:
EnableLinkedConnectionsSet its value to:
1
Reboot the machine
The change only takes effect after a restart.
If you are still encountering issues, please send an email to support@nintex.com, Please mention this article when you send an email.
Additional Information
Alternate Workaround
Instead of using drive letters (e.g., Y:\Project\file.xlsx), use the UNC path directly:
\\ServerName\ShareName\Project\file.xlsxThis works regardless of elevation and avoids mapped drive issues altogether.
When to Use This
Use this procedure when:
Botflows cannot access mapped drives
File dialogs show only local folders
The issue is resolved temporarily but returns after reboot
- Microsoft documentation: https://support.microsoft.com/en-us/help/297684
Note
Editing the Windows Registry requires administrator rights. Always advise the customer to involve their IT team if needed.
