Different incompatible(?) versions of MSED on different drives

[h-2]

So, I have three drives:

1. Samsung Evo 850 SATA
2. Samsung Evo 970 NVME
3. Samsung Evo 980 NVME (I just added this one)

The first two were already previously SEDed. I followed the instructions for the new one and it worked (except that I also needed the PSID-revert). However, the current version of sedutil seems to be incompatible with the old one. That means, that if I boot from the UEFI of the newest disk, the PBA will only unlock the newest disk (the others fail, although the password is the same). If I boot from any of the older disks, the situation is reversed. By doing multiple reboots and selecting different boot-devices, I can manage to boot a system where everything is unlocked, but obviously this is not usable in everyday life.

• why is the new PBA not backwards-compatible? I assume this is related to a change in the hashing algorithm mentioned on the releases page?
• Is there a way to upgrade an old password to a new one? I really don't want to erase the old disks...

Thank you very much!

P.S.: I crossposted this from https://github.com/Drive-Trust-Alliance/sedutil/issues/427, I hope that's OK.