Network Drive not connecting after reboot of client machine

Hi,

when the SFTP client machine is rebooted, the nework drive is still there in the Windows explorer, but it is not connected.
What I did

• When mapping the network drive, I selected "reconnect on logon"
• I also added the "Recovery" key on all sshfs* folders in the registry

Still, when booting up, the drive is disconnected until I make a double click on it.

I guess this is similar to https://github.com/winfsp/sshfs-win/issues/108

My environment is:

• Windows 11 Home 23H2
• Latest version of SSHFS-Win

to be more precise: When I startup my PC, in the Event Log I see an event like this:

launcher-x64: The service WinFsp.Launcher has been started.

When I then double click the disonnected network drive, and wait until it is connected, I see those messages:

launcher-x64: The service WinFsp.Launcher has been started.
launcher-x64: create sshfs\someuser@somehost = 0
sshfs: The service sshfs has been started.

Start by reproducing the reboot and logon sequence on Windows 11, then compare the Event Log entries before and after opening the disconnected drive. Trace the WinFsp.Launcher and sshfs service startup path; done means a mapped drive set to reconnect on logon connects automatically after reboot without a double-click.