Bill Rubin

Good point! Investigating the situation more deeply, I found the following: The ABP code path that causes successful deletion and renaming is the same code path with the same parameters as that which causes the invalid handle response. ABP has no code for deletion or renaming. Instead, ABP calls back to KeePass through the plugin interface to perform these functions. The deletion and renaming is encapsulated in a single plugin interface function called IKpFileTransaction::CommitWrite(). Based on...

Short Answer: Based on your description, and my assumption that the problem is a Windows 10 bug, a temporary workaround is to replace ABP 1.12 with ABP 1.11. Long Answer: In all releases of ABP before 1.12, the backup file is written directly on top of any previous backup file to the same directory. This means that the old backup file is effectively deleted as soon as ABP begins writing the new one. With this simple design, there is a risk that if ABP never finishes writing the new backup file (such...

As I see it, Martin has the right idea: Introduce one more level of indirection....

You're welcome. :-)

Conformance to the C++11 standard is not an all-or-nothing thing. Every compiler...

OK, it's fine with me if Dominik is willing to change the assignment of heapFullPathName...

I am the author of the FullPathName class that you have a problem with. I've been...