Linking Proxies via Mapped Network Drives Is Broken - 'Attach' Forgets Original File Path

[benjamina17887698]

Issue – When attempting to attach proxy video files from a mounted network drive, the ‘attach’ button takes the user right back to the root level of the PC (like ‘My PC’), showing all drives, and fails to follow the same file path as the original file location. This occurs with the proxy video files named correctly (e.g. filename_Proxy) and stored in a ‘Proxies’ folder right alongside the original full-resolution clip. This has only occured since I moved my workflow from a thunderbolt RAID array to a large Synology NAS device (which is properly mapped as a drive in windows). When all files are stored on standard desktop drives, the attach button follows the file path with no problems.
Steps to reproduce – 1. Store the original video file and the proxy video version on a mapped network drive, with the correct naming scheme and folder structure. 2. Import the original video file into Premiere Pro. 3. Attempt to ‘attach proxies’ and watch as Premiere falls back to the root of the computer and does not start the user at the original file location.
Expected result – Ideally, Premier should default the attach proxies search to start at the original file location, as it does if the files are all stored locally, not the root of the PC system.
Actual result – The ‘attach proxies’ button starts the user at the root of the computer system, meaning you have to navigate all the way back to the original file location and then into the ‘Proxies’ folder alongside it. When producing videos regularly, this is a NIGHTMARE and is time consuming every time!
Screen recording – Attached below
Adobe Premiere Pro version – 25.5.0 (Build 13)
Operating system – Windows 11, 24H2, OS Build 26100.4652
GPU driver version (Windows only) – Nvidia 581.29 (September 10, 2025)
Video format – H.264 MP4
Comparative information helps us understand more about when the issue occurs:
Does it affect all projects or only some projects? All projects
Does it affect new projects? Yes
When did the problem begin? Since moving from a thunderbolt-connected RAID array to a Mapped network drive Synology NAS (network attached storage)

[jamieclarke]

Hi @benjamina17887698 - 

Thanks for reporting this issue. I was able to reproduce it and will be filing a bug with the team. We’ll keep this thread updated as we learn more.

The behavior happens specifically when media is imported from a mapped drive letter rather than a UNC path. In the meantime, using the Media Browser or Import panel (which stores the UNC path) should avoid the problem.

Sorry for the trouble this has caused, and thank you again for bringing it to our attention.