Affected Version
Collapse 1.84.4
Bug Behavior
User Experience
The app blocks me with an "insufficient storage space" error when I select a folder that is actually a volume mount point for a secondary SSD (e.g., C:\mount\steam_ssd). It seems to incorrectly check the free space of the host C:\ drive instead of the target SSD, ignoring the hundreds of gigabytes actually available.
(See attached screenshots for evidence)
Expected Behavior
Detect free space for the mounted volume, instead of drive letter.
Steps to reproduce
Mount a secondary drive with ample free space to a NTFS folder on a near-full drive (e.g., C:\mount\target_ssd).
Set the application's storage/installation path to C:\mount\target_ssd.
Observe the false positive "insufficient space" warning based on the host C:\ drive's capacity.
Related Issues
No response
Screenshot(s)
Additional Information
Technical Details
The bug likely stems from truncating the selected path to the root drive letter (C:) before querying available space. To fix this, pass the full user-selected directory path directly to the disk space API (like GetDiskFreeSpaceEx on Windows) so it can correctly resolve volume mount points or junctions.
https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-getdiskfreespaceexw
Affected Version
Collapse 1.84.4
Bug Behavior
User Experience
The app blocks me with an "insufficient storage space" error when I select a folder that is actually a volume mount point for a secondary SSD (e.g., C:\mount\steam_ssd). It seems to incorrectly check the free space of the host C:\ drive instead of the target SSD, ignoring the hundreds of gigabytes actually available.
(See attached screenshots for evidence)
Expected Behavior
Detect free space for the mounted volume, instead of drive letter.
Steps to reproduce
Mount a secondary drive with ample free space to a NTFS folder on a near-full drive (e.g., C:\mount\target_ssd).
Set the application's storage/installation path to C:\mount\target_ssd.
Observe the false positive "insufficient space" warning based on the host C:\ drive's capacity.
Related Issues
No response
Screenshot(s)
Additional Information
Technical Details
The bug likely stems from truncating the selected path to the root drive letter (C:) before querying available space. To fix this, pass the full user-selected directory path directly to the disk space API (like GetDiskFreeSpaceEx on Windows) so it can correctly resolve volume mount points or junctions.
https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-getdiskfreespaceexw