This may or may not apply:
For testing with EEPC 5.2.4 you do not need to copy your big database. Test it as eval with fresh (empty) database. Create fresh, 5.2.4 install set and run it on your test PC (without any prior SafeBoot on it). That will prove if you still have a problem with 5.2.4.
I don't have any of the issue that I've seen people have on this forum, with regards to receiving 0020007 at or after preboot. My client with EEPC 5.2.4 is able to log onto PBA and restart to PBA with no issues. My issue is with a Panasonic CF - 18 and when I try to decrypt it using Safetech and try to authenticate, I receive the 0020007 error. This will not let me continue with the decryption process.
In my particular case (I'm the original poster) the issues was found to be a problem with the McAfee pre-boot code and the way it handled an error from that partiular BIOS. It only occurred when we used more than 3 partitions on that build. I'm not certain of the exact details but he BIOS manufacturer was as much to blame as McAfee. The issue was fixed with an amendement to on of the pre-boot files which was released, I think, in v5.2.7. You may find you have to upgrade to resolve your issues. Or it may not be related at all.