[quote="martin"]Thanks for your report.
I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.[/quote]

Here are the log files.
There are a total of three files, and freezing occurred in all three cases.

The first file(WinSCP09DCtrace.log) is quite large because it took some time for the issue to occur, and I ended up doing unnecessary actions until the freeze happened.

So I created a second file(WinSCP30F8trace.log), but I didn’t check the exact time when the bug occurred.

In the third file(WinSCP1214trace.log), I confirmed that the freezing happened roughly between 15:09:08 and 15:09:28.

Thanks for your report.
I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.

Hello,
I use a remote disk setup for quick access to my NAS folders. Since the NAS is on a different network from my computer, I need to activate a VPN to access the disk. This setup works quite well, as I only need to activate the VPN when I need to access the NAS, which is not a major issue.

However, it seems that WinSCP attempts to access these local disks when launching and at regular intervals. When the program starts—or even quite frequently afterward—it becomes unresponsive. I initially thought this might be due to my settings, so I updated to the latest version, 6.5.1, but the issue persists.

After researching a bit, I suspected this issue is caused by the program trying to access NAS disks that are not available. Indeed, when I activated the VPN and made the disks accessible, the problem disappeared.

I understand this issue could arise if I had attempted to access the remote disks through WinSCP while the VPN was off. However, I did not attempt to access those disks. I only had a single tab open connected to my Downloads - Documents folder, yet the issue still occurred.

Therefore, I’d like to suggest implementing one of the following options:

• A feature that allows users to prevent WinSCP from trying to read specific disks.
  
  
• An improvement that prevents the program from becoming unresponsive when it attempts to access inaccessible disks.
  
  
• An alternative improvement where the program only hangs once when it initially encounters an inaccessible disk, but avoids repeated access attempts unless explicitly requested by the user. (I assume option 2 may be harder to implement, so option 3 might be an acceptable compromise.)