Incompatibility with KeePass v2.53

Question

Incompatibility with KeePass v2.53

xwitty opened this issue a year ago · comments

Daniel Bölts · Answer 1 · Thu Jan 12 2023 17:38:46 GMT+0800 (China Standard Time)

try to use PLGX Release. xwitty ***@***.***> schrieb am Mi., 11. Jan. 2023, 20:39:

[image: 2023-01-11 20_34_28-KeePass] <https://user-images.githubusercontent.com/43315743/211901830-923b8b30-f8cf-4eba-973a-038493ee3c38.png> [image: 2023-01-11 20_34_59-Update Check - KeePass] <https://user-images.githubusercontent.com/43315743/211901835-c9fb6987-a56f-47a9-b13c-5e8eab5126db.png> — Reply to this email directly, view it on GitHub <#370>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACWW2XAUE6U4LTQIGHHUK3WR4EA5ANCNFSM6AAAAAATYNHTTU> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

WTher · Answer 2 · Wed Jan 18 2023 22:58:53 GMT+0800 (China Standard Time)

Hi,
I got the same issue, had to roll back to 2.52

Jackabomb · Answer 3 · Thu Jan 19 2023 00:36:25 GMT+0800 (China Standard Time)

@WilliamThoreau
Just to be clear, are you using the plgx extension as described here?

I am using KeePass 2.53 and KeeAnywhere 2.0.3 (PLGX) with no problem. I have this setup working on Windows 10 and Windows 7. I did not encounter any problems at all with the upgrade to KP 2.53.
However, I have never tried the .ZIP method or anything with a KeeAnywhere.DLL file.

xwitty · Answer 4 · Thu Jan 19 2023 00:44:08 GMT+0800 (China Standard Time)

try to use PLGX Release. xwitty @.***> schrieb am Mi., 11. Jan. 2023, 20:39:
…

Now I understood the question - yes, I am using PLGX (and not zip release).

WTher · Answer 5 · Thu Jan 19 2023 07:28:59 GMT+0800 (China Standard Time)

@Jackabomb Thanks.
Problem solved... I guessI made a mistake when upgrading to 2.53.

PJ Eby · Answer 6 · Sun Jan 22 2023 22:25:49 GMT+0800 (China Standard Time)

I can get it to work on 64-bit Windows 10 with 2.53 but not 32-bit Windows 7. 1.6.0 works with 2.53 on the 32-bit machine but not 2.0.0 or 2.0.3. I tried installing .NET 4.6.1 after uninstalling 4.6.2 in case that was the issue, but it didn't help. I even installed Keepass 2.52 in case that helped, but it also did not help.

(I also tried both zip and plgx - with wipe and reinstall inbetween.)

flotux2 · Answer 7 · Mon Feb 06 2023 15:12:41 GMT+0800 (China Standard Time)

I get a different error message when using the latest KeeAnywhere plugin as PLGX file:

I did an update of KeePass to version 2.53 and also installed on my Windows 11 PC all available updates (2023-01 patches and also .NET updates). So I cannot say if the problem is because of the update of KeePass or because of the Windows updates.
I did a downgrade to KeePass 2.52. But here I get exactly the same error message. I never had issues with KeeAnywhere in the past. Also the re-authentication worked.

I also removed my OneDrive account form the plugin and tried to freshly login. I can login to my Microsoft account and also get the message "Received verification code. Youmay now close this window." in the browser. But then I get the error message.

Rory JC · Answer 8 · Thu Apr 27 2023 22:49:49 GMT+0800 (China Standard Time)

I am updated to KeePass 2.53.1 and I am getting similar errors to everyone here.

Only way around it reverting back to 2.51.1.

I'm on Windows 11 with all the latest updates if that helps

I used the PLGX file to install like I always do.

cacophobe · Answer 9 · Thu Dec 21 2023 22:57:48 GMT+0800 (China Standard Time)

From my recent experience with KeePass 2.55 on Windows 11, it requires that KeePass is started with 'Admin' or 'root' privileges when initializing the plugin for the first time. My guess is it's because it needs access to the system's secure credentials storage. Once you have the credentials of your cloud provider authenticated and saved, you can start KeePass normally.