I can’t seem to find much documentation on this issue since there’s not a lot of docs in general about windows builds.
When I connect to a windows shared server, I simply get the message “smb: invalid protocol.” My windows 11 install has smb1 2 and 3 enabled. No prompt for authentication happens either.
I can hack around this by mapping it to a network drive, but the connection is extremely slow for whatever reason that way.
The server of course works fine when using explorer.
I don’t know what info would be useful. This is the 25.08.1 version taken from the cdn of built binaries. Windows 11 is 23H2.
Unrelated but the Info Pane seems entirely unavailable. I assume there’s a reason for this but again, windows documentation is spotty seemingly. Not as concerned about this.
Workaround: creating a symlink to “mount” the network location to my C drive. Why that works so much better than using a mapped network drive, I don’t know. Does work though.
Thanks for supporting a windows build. I use Dolphin on all my home PCs and I crave UI consistently at work now.
The information panels depends on baloo and stuff, and isn’t supported for Windows at the moment. I could become supported.
This is the best course of action. The dolphin native smb protocol is Unix only. Dolphin then needs to access the windows share through regular filesystem mount.
While the network drive, it probably needs some special care, like dolphin does with its own smb implementation. And gets bad performance consequently. It might depend on the preview generation for instance.
Your feedback is very helpful.
I’d like to have contributors to help on Windows support, since we aren’t too far to offer a very good experience on this OS.