Another screenshot of the error, this one when directory navigation sync is off...
One screenshot of the error...
I must say that...
The error has appeared one time at the first execution after upgrading from 6.5.5, but then...
It disappeared, and I never managed to make it appear again.
So: version 6.5.5 installed -> Upgrade to 6.6.1 -> Run -> connect to site -> Try to use the commander UI enter a local folder which is a junction to another folder on the same ntfs drive -> Strange error (403? 430?) .
Restart WinSCP, try again, no error whatsoever...
I'm baffled!
Thanks for your report. I cannot reproduce this.
This is about the local panel, right? And a directory junction?
Does it happen with any directory junction? Or with some specific targets only? I've tried both a junction pointing to another folder on the same drive and a junction pointing to another (Windows) machine. Both can be entered/opened (if that's what you mean by navigating).
Also, please post the "strage errore".
Also, this happens on commander GUI on Windows 11 with the latest service packs.
As stated, the latest beta gives a strage errore when navigating junctions on NTFS drives, where the 6.5.x never had a single problem with them.