https://bugs.kde.org/show_bug.cgi?id=419294
--- Comment #28 from Benny <jf...@web.de> --- Hi Maik, Hi Gilles, I give up. Sorry for wasting your time. I've tested for hours now and I can't find a root cause. Three physical Windows 10 systems reacting the same way, it doesn't matter if it is a local share or remote share. The error comes up every few times. The Windows 8 VM (from 2012, not updated at all) has the same behavior. Now I've installed a clean Windows 10 1909 in vmware, created the local share and it's working! Updated to the latest Windows Defender updates and OS updates, connected to my network, and it keeps working. I am at my wit's end. The physical Windows 10 system all have in common, that they've been upgraded over and over from previous Windows 10 versions... but else, on one Kaspersky security software is running, on the others Windows Defender. On two 1909 is running, on one 1903 with Windows Defender. I checked about Windows Defender and Firewall (as you've mentioned Maik), disabled them. No changes. At the moment I believe it's a wired Windows bug. I can live with it, because everything else is running smoothly. @Maik: Could you please remove the "File:" call again? It's running better without as far as I can see. Thank you again for your fast support. And I love digiKam. Benny -- You are receiving this mail because: You are watching all bug changes.
