Unable to save files to network drive [SOLVED]

[rhodo]

I am currently unable to save files downloaded with EPF to my NAS. I had no trouble getting EPF to save files to my NAS in the past, but I recently noticed this issue because my C: drive ran out of free space. I believe this behavior started with the last update to 3.66.3.0, but it may have started sooner.

I am able to get EPF to navigate to the network drive and select it as the download destination in Project Properties. I have also selected the network drive as the default download location in Settings. The "Save: Destination folder" correctly displays the desired network location (\\computer_name\path\to\save\folder).

However, all files are saved to C:\computer_name\path\to\save\folder

I have tried mapping the network drive to a drive letter, but all files are still saved to C:

I should point out the computer running EPF is a Windows 10 VM inside UNRAID. I don't think this is a factor because it has always worked fine in the past, but I mention it just in case it's relevant to troubleshooting the issue.

Thanks for any assistance you can offer!

[Maksym]

Nothing related to how files are saved changed for a very long time. So, if it was working earlier and stopped working now - it's not the program's fault. Sorry.

But, in any case, mapping a network location to a drive letter will make it easier. Just not to the "C". Map to "F" or something like that, not to a system drive letter.

[rhodo]

I have found a solution to this issue.

1. Add windows firewall rule for EPF
After installing Malwarebytes Windows Firewall Control, I noticed that there was no firewall rule for EPF, so I added one. I don't know if a Windows Update may have removed a rule that was added during initial installation of EPF, but adding this rule now allows me to save files to a mapped network drive

2. Save files to mapped network drive
EPF will still not save files to a network shared drive (\\computer_name\path\to\save\folder). It will only save to a mapped drive (X:\path\to\save\folder). Even with windows firewall completely disabled. This is really not problem as long as you know that you must save downloaded files to the mapped drive, otherwise everything gets dumped in C:

[Maksym]

Thank you for sharing the solution!

[SpaceSuitSpacePants]

I'm experiencing the same issue with EPF running on a Windows 11 guest in Hyper-V. Although EPF accepts a UNC path (\\COMP\pictures) and even shows the files in its viewing area, it ends up saving them to a local directory (e.g., C:\COMP\pictures) instead of the network share. I've also tried using a mapped drive, but the same issue occurs. No other software in the VM has problems saving to the network drive.

Issues:

• EPF accepts the UNC path (\\COMP\pictures) but resolves it to a local path (C:\COMP\pictures) when saving files. A symlink created to point to the UNC share is also resolved to the UNC path—so the problem persists.

Solution:

• Create a Symlink to the Network Share:
  To create the symlink, open a Command Prompt and run:

  Code: Select all

  mklink /D "C:\Path\To\SymlinkFolder" "\\COMP\pictures"

  Use SUBST to Map a Virtual Drive to the Symlink:
  Open a non-elevated command prompt (do not run as administrator, since mappings created in admin mode might not appear in regular sessions) and run:

  Code: Select all

  subst X: "C:\Path\To\SymlinkFolder"

  This creates a virtual drive (X:) that points to the symlink, effectively “tricking” EPF into treating the network share as a local drive.
• Restart EPF:
  Close and reopen EPF so it can recognize the new drive mapping.

Note:
I'm not 100% sure if using the SUBST command is any different from mapping a drive through File Explorer in this context, but it worked reliably for me. If I run into more issues, I'll also check the firewall settings.

Hope this helps anyone facing the same problem!