Thomas S.

Just an idea. Has anyone ever tried to set up access to the NAS with the same user and PW as used in the active Windows account? Maybe Win10 / .NET is trying to do that when accessing the NAS?

Yes. If the PW database is opened promptly after copying a file on the share, there are hardly any problems. But if a certain time has passed before the PW-DB is to be opened, the problem comes up again. Since I do not always need the PW-DB right away, this is not a real gain in comfort. Another thing: if the error occurred, I cant send KeePass to the taskbar with the "close window button", absolut no reaction. This only works again after i have used the other window buttons. Somehow I have the impression...

Hi. You are not allone - I have exact the same problem - and I have opened a ticket at AVM - no solution at this point. Win10 1909 64bit SMB1 FritzBox 7490 I noticed that file explorer will not responds to the share (frozen), when keepass is trying to open the PWfile on this share. Something fully block the traffic. But I have no idear what is going on...

With "crashes" I meant that the app disappeared from the desktop, the window closed, it is gone without a trace. So it is "normal" that the log do stop logging at the point the scanner starts the scan and the app shut down. The scan stopps working before it starts the run, but hangs busy. I add a log2 with a normal scan with bitdepth 8.

And I have installed two additional libs for iscan to safe files in jpg and png. A conflict possible? libjpeg62 libpng12-0

With "crashes" I meant that the app disappeared from the desktop, the window closed, it is gone without a trace. So it is "normal" that the log do stop logging at the point the scanner starts the scan and the app shut down. The scan stopps working before it starts the run, but hangs busy. I add a little video. Bad quality, but it shows whats going on. I start a crashed session (dosn't matter), then reduce the bitdepth to 8 and starts the scan. This works. Then I increase the bitdepth to 16 and start...

With "crashes" I meant that the app disappeared from the desktop, the window closed, it is gone without a trace. So it is "normal" that the log do stop logging at the point the scanner starts the scan and the app shut down. The scan stopps working before it starts the run, but hangs busy. I add a little video. Bad quality, but it shows whats going on. I start a crashed session (dosn't matter), then reduce the bitdepth to 8 and starts the scan. This works. Then I increase the bitdepth to 16 and start...

With "crashes" I meant that the app disappeared from the desktop, the window closed, it is gone without a trace. So it is "normal" that the log do stop logging at the point the scanner starts the scan and the app shut down. The scan stopps working before it starts the run. I add a little video. Bad quality, but it shows whats going on. I start a crashed session (dosn't matter), then reduce the bitdepth to 8 and starts the scan. This works. Then I increase the bitdepth to 16 and start the scan - it...