"The folder name is not valid" when choosing save path and selected a folder shortcut #9777

New issue

Closed

opened 2026-02-21 20:22:40 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 20:22:40 -05:00

Owner

Originally created by @gundamftw on GitHub (Feb 20, 2020).

Please provide the following information

qBittorrent version and Operating System

v. 4.2.1, Windows 10 64 bit

What is the problem

When choosing a save path on where to store my torrent content, if I selected a folder shortcut, it gives me a error "the folder name is not valid"

What is the expected behavior

When clicked on that folder shortcut, it should jump to the folder that the shortcut is pointing to.

Steps to reproduce

Create a shortcut of a folder in the computer. Click on any magnet link to start the saving dialog, click the "browse" icon to launch the saving path dialog box, select that folder shortcut.

Extra info(if any)

The folder shortcut works normally when I'm browsing to load a torrent file.

Originally created by @gundamftw on GitHub (Feb 20, 2020). **Please provide the following information** ### qBittorrent version and Operating System v. 4.2.1, Windows 10 64 bit ### What is the problem When choosing a save path on where to store my torrent content, if I selected a folder shortcut, it gives me a error "the folder name is not valid" ### What is the expected behavior When clicked on that folder shortcut, it should jump to the folder that the shortcut is pointing to. ### Steps to reproduce Create a shortcut of a folder in the computer. Click on any magnet link to start the saving dialog, click the "browse" icon to launch the saving path dialog box, select that folder shortcut. ### Extra info(if any) The folder shortcut works normally when I'm browsing to load a torrent file.

deekerman

2026-02-21 20:22:40 -05:00

closed this issue
added the
Duplicate
label

deekerman commented

2026-02-21 20:22:44 -05:00

Author

Owner

@thalieht commented on GitHub (Feb 20, 2020):

Duplicate of #7900.
Looks like a problem with FileSystemPathEdit or one of its components because it works correctly when using "Set location..."

@thalieht commented on GitHub (Feb 20, 2020): Duplicate of #7900. Looks like a problem with `FileSystemPathEdit` or one of its components because it works correctly when using "Set location..."