Michael

Thanks Dominik, i gave that try, but wasn't successful. (made a TLS 1.3 key and set a zero DWORD for Server and Client, then restarted windows). Well, i've expected this result, because integrating the WebDAV URLs as drive letters and file reading/writing directly in Windows works. The error only occurs when KeePass itself wants to write to the URL. best, Michael

Thanks Dominik, i gave that try, but wasn't successful. (made a TLS 1.3 key and set a zero DWORD for Server and Client, then restarted windows). Well, i've expected this result, because integrating the WebDAV URLs as drive letters and reading/writing in Windows itself works. The error only occurs when KeePass itself wants to write to the URL. best, Michael

anyway, thanks a lot for your support, Paul

mhhh... looks there is no 5 there

mhhh... looks there is no 5 there

` dotnet --info Host: Version: 9.0.3 Architecture: x64 Commit: 831d23e561 RID: win-x64 .NET SDKs installed: No SDKs were found. .NET runtimes installed: Microsoft.AspNetCore.App 8.0.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 6.0.35 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 8.0.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 9.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App...

please, can anyone help? After switching from Win10 to Win11, KeePass refuses to save on webdav. When trying to save, it blocks until timeout, then tells something like "file may be corrupt...". The WevDAV URL is like https://myserver.com:2078/myfile.kdbx (accessing with user & password) Loading is no problem, but the writing fails. Checking the server, a 0kb myfile.kdbx.tmp file was created. On Win10, everything works fine, it's just Win11 (so the webdav can't be the problem). Tested on 3 different...

nope, Paul, all W10 settings are default. Tried to play with this option on win11, but didn't work.