Tom X

I have to add / correct myself: depending on the operations in the keepass app it crashes not only when closing the app. Actually thats more logical for me when pulling the mapped .exe and .dlls away underneath. (guess it depends of what of these is already in RAM) So unless there's a way to start and run keepass completely in RAM and indenpendent of the underlying storage I don't think that problem is solvable with a config option.

I've made these settings.. everything works fine without any error messages under normal circumstances. these are the files open normaly 586218 10501 DENY_WRITE 0x120089 RDONLY LEASE(RH) /xxx yyy/programme/keepass2/KeePass.XmlSerializers.dll Thu Jan 29 10:19:56 2026 586218 10501 DENY_WRITE 0x1000a1 RDONLY LEASE(RH) /xxx yyy/programme/keepass2/KeePass.exe Thu Jan 29 10:19:52 2026 586218 10501 DENY_WRITE 0x1000a1 RDONLY LEASE(RH) /xxx yyy/programme/keepass2/KeePassLibC64.dll Thu Jan 29 10:20:05 2026...

for deployment reasons we've put keepass2 portable on a read-only network share (samba with windows clients). This works fine except for rare reports about errors (see screenshots) when closing keepass2. My guess is that a client that goes into energy saving mode looses the handles to the keepass2 exe/dlls open on the fileserver and therefore somehow looses it's knowledge about whether/ where / how to save user config. I can provoke these error messages by - opening portable keepass2 from the share...