Menu

#1379 Installing .Net update 3032662 breaks keepass

KeePass_2.x
closed
nobody
None
5
2015-05-17
2015-05-17
No

After I installed the windows (.NET) update 3032662 (see [1]) through windows automatic update KeePass won't start anymore and instead present an error message (attached in the stackdump.txt file).

I could reproduce the error by:
1. deinstalling the security update -> KeePass runs
2. installing the security update -> same error message

Environment:
- Keepass 2.29
- Windows 8.1 64bit

Workaround for now is to disable the update, but IMO this shuld be fixed in the software.

Thanks for your work!

[1] https://support.microsoft.com/en-us/kb/3032662

1 Attachments

Discussion

  • Dominik Reichl

    Dominik Reichl - 2015-05-17

    I cannot reproduce this. On my Windows 8.1 system, KeePass 2.29 still runs fine after installing the .NET update.

    Maybe something went wrong with the update installation on your system. If there's some issue with the assembly in the GAC, you should be able to resolve the issue by first uninstalling and then reinstalling KeePass (if you used the installer). If that doesn't help, my suggestion would be to reinstall .NET.

    Best regards,
    Dominik

     
  • Dominik Reichl

    Dominik Reichl - 2015-05-17
    • status: open --> closed
    • Priority: 2 --> 5
     
  • Markus Zingg

    Markus Zingg - 2015-05-17

    I do use a KeyFile. Maybe this has something to do with that (seeing the keyPromptForm class in the stack).

    I already tried to reinstall KeePass, it did not resolve the problem.

     
  • Dominik Reichl

    Dominik Reichl - 2015-05-17

    Key files don't have anything to do with it.

    As it can be seen from your stack trace, a System.BadImageFormatException is thrown for System.Security, which indicates a problem of your .NET installation or the GAC (and there's nothing that I could do in KeePass to workaround it).

    The reason why I suggested to reinstall KeePass was that I hoped that this would recreate the native KeePass image in the GAC, which could maybe have resolved the issue. As this wasn't the case, your only option will be to reinstall .NET.

    Best regards,
    Dominik

     

Log in to post a comment.