Bug: Can't access some notwork mounted drives (Mountain Duck)

[MisterDenis]

Description

Hi.

I use Mountain Duck - based on Cyberduck - to mount some remote drives as network drives on my PC, notably OneDrive and a few SMB shares. This works well in Windows Explorer, but in Files I can't access them. I see the network drives but trying to access leads to the following error message:

ERROR_NO_NET_OR_BAD_PATH

I don't see anything in the log that would have anything to do with this, and all drives mounted with Mountain Duck behave the same. I've seen bug #17144 which seemed similar, but on Raidrive and to knowledge the two apps don't use the same methods to mount so I'm unsure if it's related.

This is a snippet from the debug log:
2025-11-17 10:58:14.5848|Information|The app is being activated. Activation type: LaunchActivatedEventArgs 2025-11-17 10:58:15.2760|Information|SIDELOAD: Checking for updates... 2025-11-17 10:58:15.3368|Information|Drive added: C:\, Fixed 2025-11-17 10:58:15.3809|Warning|Unauthorized: Attempting to add the device, D:\, failed at the StorageFolder initialization step. This device will be ignored. 2025-11-17 10:58:15.4499|Warning|Unauthorized: Attempting to add the device, E:\, failed at the StorageFolder initialization step. This device will be ignored. 2025-11-17 10:58:15.4709|Warning|Unauthorized: Attempting to add the device, F:\, failed at the StorageFolder initialization step. This device will be ignored. 2025-11-17 10:58:15.4957|Information|SIDELOAD: Current Package Name: Files 2025-11-17 10:58:15.4963|Information|SIDELOAD: Remote Package Name: Files 2025-11-17 10:58:15.4967|Information|SIDELOAD: Current Version: 4.0.11.0 2025-11-17 10:58:15.4971|Information|SIDELOAD: Remote Version: 4.0.11.0 2025-11-17 10:58:15.4975|Warning|SIDELOAD: Update not found. 2025-11-17 10:58:15.5072|Information|Drive added: G:\, Fixed 2025-11-17 10:58:15.5786|Information|Drive added: H:\, Network 2025-11-17 10:58:15.6498|Information|Drive added: O:\, Network 2025-11-17 10:58:15.6876|Information|Drive added: W:\, Network

You can ignore Drives D, E and F: they are local drives I don't show in Explorer.

Any assistance would be great!

Steps To Reproduce

1. Mount a network/online drive through Mountain Duck (version 5)
2. Attempt to access drive in Files
3. Get error

Files Version

4.0.11.0

Windows Version

Win 11 Pro 26100.4946 (1000.26100.197.0)

User ID

No response

Log File

debug.log

[yaira2]

@MisterDenis thank you for the report. This does sound similar to the issue you linked #17144. We haven't released the fix to stable yet, but you can try it in the preview version https://files.community/download. Can you check if it's still an issue in the preview build?

[MisterDenis]

@MisterDenis thank you for the report. This does sound similar to the issue you linked #17144. We haven't released the fix to stable yet, but you can try it in the preview version https://files.community/download. Can you check if it's still an issue in the preview build?

Thanks for the reply! I installed the preview (4.0.19) and sadly, I get the same errors and behaviours... One detail of note (maybe) is that this exclusively happens with drives mounted with Mountain Duck; if I connect to same SMB drive through Windows directly, then Files can access it without any issue.

[yaira2]

Thank you for checking.