Network drive bug... no connection with TC until connected with Explorer

[SysATI]

Hi,

I have a small bug / annoying problem...

It started a few weeks ago and I wonder if it is my setup of some bug in the last release (9.22a) ?

When I restart my computer (I rarely do)
- network drives aren't connected (i.e. physically connected, but no yet accessed)
- the drive icons on TC appear with a red "X" on them (so far everything is normal)
- when I click on the drive, instead of connecting and then displaying the drive content, TC freezes...

If I close TC and try to re-access it, no problem, the drive has been connected and it opens...

If I use Windows Explorer instead of TC, no problem, the drive connects and opens...
IF I open the drive with Explorer (and connect it) before TC then I have no problem...

But if the drive is disconnected and red "X"ed TC cannot open it anymore.

Never had this problem until now...
And I've been using TC on windows for over 20 years

Any idea / solution ?

[ghisler(Author)]

TC calls a function (WNetAddConnection3) with parameter CONNECT_INTERACTIVE when a connection is lost. There is also an alternate connection method which goes via Explorer. You can enable it via wincmd.ini:
To section [Configuration] please add:
UseShellConnect=1

[SysATI]

Thanks, I'll try that...

So far it doesn't help much... but I'll reboot the PC maybe it'll help ?

(if I disconnect a connected drive with TC, the result is the same, freeze...)