Installation problem on Windows with v2.4.1

[robin-nitrokey]

ModuleNotFoundError: No module named 'win32api'

[robin-nitrokey]

Possible causes:

• We’ve updated Python from 3.9 to 3.10 in da46e33.
• We’ve updated pywin32 from v305 to v311 in e7161d0.

[mmerklinger]

On which version of Windows did you see that? Did it appear right after starting the app? Was there already an older version of the app installed? If yes, which one?

[geoW-n]

Sorry for the inconvenience, the problem does solve itself, maybe booting is helpful.
I am running Microsoft Windows [Version 10.0.19045.6216] which is going out of order soon
I downloaded the nitrokey-app-v2.4.1-x64-windows-installer.msi with ff 141, usually I click the download button top of ff and start the program, here I opened the download directory (ff download button) and double clicking the program. 2.3.4 has been the program version running before.
First thing happened giving admin rights second thing the error message in question appears.

I do not boot every day. end day work hibernating, but I may have booted the machine in the meantime..
This morning e-mail remembered me of this case , I double clicked the same program and now it runs as expected fine.

[sschuberth]

I'm still getting the exact same error on Windows 11, directly after starting the app from the start menu.

And yes, and older version of the app was present before. In my case it was version 2.3.3 of the app, which got updated / overwritten by the version 2.4.1 installer.

[wschlich]

Same issue here on Windows 11.
Also updated from 2.3.3 to 2.4.1.
A reboot didn't help.
Installing 2.4.1 a 2nd time (installing over existing 2.4.1) solved the issue.

[daringer]

mmmh, could this be an installation / msi issue due to the updated signature we provide since v2.3.4 ?
So maybe really installing twice might be the "fix" here

[march42]

mmmh, could this be an installation / msi issue

For me, It seems to be. I fixed the issue earlier today with uninstalling and again installing afterwards.

due to the updated signature we provide since v2.3.4

I updated from 2.1.2 if it helps.

[sschuberth]

Installing 2.4.1 a 2nd time (installing over existing 2.4.1) solved the issue.

I can confirm that this also worked for me 👍🏻