F-Secure Key extremely slow

mashmash Posts: 19

F-Secure Key takes 5 to 10 seconds to respond to key presses, i.e. press Edit and it takes 10 seconds to get to the edit screen, 5 seconds to look at a password.  "fskey.exe *32" is using 30% cpu on my PC (Win7 64bit).  I am using version 4.3.108 but the previous version was also extremely slow.

Here are some sections from the log file where there seems to be problems ...

 

[2016-05-11 09:08:07:867] IapsService: IapsService verify
[2016-05-11 09:08:07:867] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:08:07:867] PurchaseService: Checking ticket validity...
[2016-05-11 09:08:07:867] PurchaseService: Start ticket verify
[2016-05-11 09:08:07:867] PurchaseService: verify ticket for sync
[2016-05-11 09:08:07:867] IapsService: IapsService verify
[2016-05-11 09:08:07:867] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:08:07:867] PurchaseService: Checking ticket validity...
[2016-05-11 09:08:07:867] PurchaseService: Start ticket verify
[2016-05-11 09:08:07:867] PurchaseService: verify ticket for sync
[2016-05-11 09:08:07:867] IapsService: IapsService verify
[2016-05-11 09:08:07:867] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:08:07:867] PurchaseService: Checking ticket validity...
[2016-05-11 09:08:07:867] PurchaseService: Start ticket verify
[2016-05-11 09:08:07:867] PurchaseService: verify ticket for sync
[2016-05-11 09:08:07:867] IapsService: IapsService verify
[2016-05-11 09:08:07:867] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:08:07:867] PurchaseService: Checking ticket validity...
[2016-05-11 09:08:07:867] PurchaseService: Start ticket verify
[2016-05-11 09:08:07:867] PurchaseService: verify ticket for sync
[2016-05-11 09:08:07:867] IapsService: IapsService verify
[2016-05-11 09:08:07:867] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:08:07:867] PurchaseService: Checking ticket validity...
[2016-05-11 09:08:07:867] PurchaseService: Start ticket verify
[2016-05-11 09:08:07:867] PurchaseService: verify ticket for sync
[2016-05-11 09:08:07:867] IapsService: IapsService verify
[2016-05-11 09:08:07:867] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:08:07:867] PurchaseService: Checking ticket validity...
[2016-05-11 09:08:07:867] PurchaseService: Start ticket verify
[2016-05-11 09:08:07:867] PurchaseService: verify ticket for sync
[2016-05-11 09:08:07:867] IapsService: IapsService verify
[2016-05-11 09:08:07:867] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:08:07:867] PurchaseService: Checking ticket validity...
[2016-05-11 09:08:07:867] PurchaseService: Start ticket verify
[2016-05-11 09:08:07:867] PurchaseService: verify ticket for sync
[2016-05-11 09:08:07:867] IapsService: IapsService verify
[2016-05-11 09:08:07:877] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:08:07:877] PurchaseService: Checking ticket validity...
[2016-05-11 09:08:07:877] PurchaseService: Start ticket verify
[2016-05-11 09:08:07:877] PurchaseService: verify ticket for sync
[2016-05-11 09:08:12:139] IapsService: IAPS verify failed: BAD REQUEST / 1009
[2016-05-11 09:08:12:139] PurchaseService: ticket verification nok: BAD REQUEST / not-verified
[2016-05-11 09:08:12:139] PurchaseService: ticket marked not-verified
[2016-05-11 09:08:12:149] PurchaseService: Ticket verification failed
[2016-05-11 09:08:12:149] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 09:08:12:579] StorageService: syncPush, uuid xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2016-05-11 09:08:12:579] SyncService: API uploadCurrent...
[2016-05-11 09:08:12:639] PurchaseService: Remove operator settings
[2016-05-11 09:08:12:639] IapsService: IAPS verify failed: BAD REQUEST / 1009
[2016-05-11 09:08:12:639] PurchaseService: ticket verification nok: BAD REQUEST / not-verified
[2016-05-11 09:08:12:639] PurchaseService: ticket marked not-verified
[2016-05-11 09:08:12:649] PurchaseService: Ticket verification failed
[2016-05-11 09:08:12:649] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 09:08:13:079] StorageService: isSyncPossible: already syncing
[2016-05-11 09:08:13:079] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 09:08:13:079] PurchaseService: Remove operator settings
[2016-05-11 09:08:13:079] IapsService: IAPS verify failed: BAD REQUEST / 1009
[2016-05-11 09:08:13:079] PurchaseService: ticket verification nok: BAD REQUEST / not-verified
[2016-05-11 09:08:13:079] PurchaseService: ticket marked not-verified
[2016-05-11 09:08:13:079] PurchaseService: Ticket verification failed
[2016-05-11 09:08:13:079] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 09:08:13:502] StorageService: isSyncPossible: already syncing
[2016-05-11 09:08:13:502] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 09:08:13:502] PurchaseService: Remove operator settings
[2016-05-11 09:08:13:503] IapsService: IAPS verify failed: BAD REQUEST / 1009
[2016-05-11 09:08:13:503] PurchaseService: ticket verification nok: BAD REQUEST / not-verified
[2016-05-11 09:08:13:503] PurchaseService: ticket marked not-verified
[2016-05-11 09:08:13:504] PurchaseService: Ticket verification failed
[2016-05-11 09:08:13:504] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 09:08:13:842] StorageService: isSyncPossible: already syncing
[2016-05-11 09:08:13:842] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 09:08:13:842] PurchaseService: Remove operator settings
[2016-05-11 09:52:44:955] PurchaseService: Start ticket verify
[2016-05-11 09:52:44:955] PurchaseService: verify ticket for sync
[2016-05-11 09:52:44:955] IapsService: IapsService verify
[2016-05-11 09:52:44:955] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:52:44:955] PurchaseService: Checking ticket validity...
[2016-05-11 09:52:44:955] PurchaseService: Start ticket verify
[2016-05-11 09:52:44:955] PurchaseService: verify ticket for sync
[2016-05-11 09:52:44:955] IapsService: IapsService verify
[2016-05-11 09:52:44:955] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:52:44:955] PurchaseService: Checking ticket validity...
[2016-05-11 09:52:44:955] PurchaseService: Start ticket verify
[2016-05-11 09:52:44:955] PurchaseService: verify ticket for sync
[2016-05-11 09:52:44:955] IapsService: IapsService verify
[2016-05-11 09:52:44:955] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:52:44:955] PurchaseService: Checking ticket validity...
[2016-05-11 09:52:44:955] PurchaseService: Start ticket verify
[2016-05-11 09:52:44:955] PurchaseService: verify ticket for sync
[2016-05-11 09:52:44:955] IapsService: IapsService verify
[2016-05-11 09:52:44:955] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 09:52:44:955] PurchaseService: Checking ticket validity...
[2016-05-11 09:56:35:330] PurchaseService: ticket verification nok: BAD REQUEST / not-verified
[2016-05-11 09:56:35:330] PurchaseService: ticket marked not-verified
[2016-05-11 09:56:35:331] PurchaseService: Ticket verification failed
[2016-05-11 09:56:35:331] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 09:56:35:779] StorageService: isSyncPossible: already syncing
[2016-05-11 09:56:35:779] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 09:56:35:779] PurchaseService: Remove operator settings
[2016-05-11 09:56:35:780] IapsService: IAPS verify failed: BAD REQUEST / 1009
[2016-05-11 09:56:35:780] PurchaseService: ticket verification nok: BAD REQUEST / not-verified
[2016-05-11 09:56:35:780] PurchaseService: ticket marked not-verified
[2016-05-11 09:56:35:781] PurchaseService: Ticket verification failed
[2016-05-11 09:56:35:781] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 09:56:36:120] StorageService: isSyncPossible: already syncing
[2016-05-11 09:56:36:120] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 09:56:36:120] PurchaseService: Remove operator settings
[2016-05-11 09:56:36:121] IapsService: IAPS verify failed: BAD REQUEST / 1009
[2016-05-11 09:56:36:121] PurchaseService: ticket verification nok: BAD REQUEST / not-verified
[2016-05-11 09:56:36:121] PurchaseService: ticket marked not-verified
[2016-05-11 09:56:36:121] PurchaseService: Ticket verification failed
[2016-05-11 09:56:36:121] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 09:56:36:468] StorageService: isSyncPossible: already syncing
[2016-05-11 09:56:36:468] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 09:56:36:468] PurchaseService: Remove operator settings
[2016-05-11 09:56:36:469] IapsService: IAPS verify failed: BAD REQUEST / 1009
[2016-05-11 09:56:36:469] PurchaseService: ticket verification nok: BAD REQUEST / not-verified
[2016-05-11 09:56:36:469] PurchaseService: ticket marked not-verified
[2016-05-11 09:56:36:470] PurchaseService: Ticket verification failed
[2016-05-11 09:56:36:470] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 09:56:36:802] StorageService: isSyncPossible: already syncing
[2016-05-11 09:56:36:803] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 09:56:36:803] PurchaseService: Remove operator settings
[2016-05-11 09:56:36:804] IapsService: IAPS verify failed: BAD REQUEST / 1009
[2016-05-11 10:03:39:792] IapsService: IapsService verify
[2016-05-11 10:03:39:793] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 10:03:39:793] PurchaseService: Checking ticket validity...
[2016-05-11 10:03:39:793] PurchaseService: Start ticket verify
[2016-05-11 10:03:39:793] PurchaseService: verify ticket for sync
[2016-05-11 10:03:39:793] IapsService: IapsService verify
[2016-05-11 10:03:39:794] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 10:03:39:794] PurchaseService: Checking ticket validity...
[2016-05-11 10:03:39:794] PurchaseService: Start ticket verify
[2016-05-11 10:03:39:794] PurchaseService: verify ticket for sync
[2016-05-11 10:03:39:794] IapsService: IapsService verify
[2016-05-11 10:03:39:794] PurchaseService: Couldn't verify ticket. Allow service temporarily and try to verify later
[2016-05-11 10:03:39:794] PurchaseService: Checking ticket validity...
[2016-05-11 10:03:39:794] PurchaseService: Start ticket verify
[2016-05-11 10:03:39:795] PurchaseService: verify ticket for sync
[2016-05-11 10:08:40:178] StorageService: isSyncPossible: already syncing
[2016-05-11 10:08:40:178] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 10:08:40:178] PurchaseService: Remove operator settings
[2016-05-11 10:08:40:179] PurchaseService: ticket verification nok: error / network-failure
[2016-05-11 10:08:40:179] PurchaseService: Ticket verification failed
[2016-05-11 10:08:40:179] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 10:08:40:463] StorageService: isSyncPossible: already syncing
[2016-05-11 10:08:40:464] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 10:08:40:464] PurchaseService: Remove operator settings
[2016-05-11 10:08:40:464] PurchaseService: ticket verification nok: error / network-failure
[2016-05-11 10:08:40:465] PurchaseService: Ticket verification failed
[2016-05-11 10:08:40:465] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 10:08:40:748] StorageService: isSyncPossible: already syncing
[2016-05-11 10:08:40:748] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 10:08:40:748] PurchaseService: Remove operator settings
[2016-05-11 10:08:40:749] PurchaseService: ticket verification nok: error / network-failure
[2016-05-11 10:08:40:749] PurchaseService: Ticket verification failed
[2016-05-11 10:08:40:749] StorageService: onTicketsChanged, tickets count: 1219
[2016-05-11 10:08:41:033] StorageService: isSyncPossible: already syncing
[2016-05-11 10:08:41:033] StorageService: syncPush: Skipping, sync is blocked
[2016-05-11 10:08:41:033] PurchaseService: Remove operator settings
[2016-05-11 10:08:41:033] PurchaseService: ticket verification nok: error / network-failure
[2016-05-11 10:08:41:034] PurchaseService: Ticket verification failed
[2016-05-11 10:08:41:034] StorageService: onTicketsChanged, tickets count: 1219
StigSivertsen

Comments

  • BenBen Posts: 2,640

    Hello mash, 

     

    I'll get back to you by private message on this problem.

  • KorvaooKorvaoo Posts: 7
    i have same problem atleast on 1 laptop, win 10 64bit.
  • bluecrossbluecross Posts: 9

    Same here! Win10 64bit.

  • Yep, same problem here. I tried also to reinstall the application (F-Secure Key 4.3.117). Fskey.exe is using all available CPU and rendering the application useless. I have the very same issue happening on my personal Windows 10, as well on my work computer (Win 10 as well).

     

    And got another issue - I just tried to reinstall the application, which worked fine. However, when trying to connect the devices, I got error notification that I would not have enough disk space to perform the sync? I admit, that there's only 8 GBs+ available but this should be plenty for my user data (~2.5 MB).

     

     

  • JassuJassu Posts: 42

    @Lauri_Lattoni wrote:

     

    And got another issue - I just tried to reinstall the application, which worked fine. However, when trying to connect the devices, I got error notification that I would not have enough disk space to perform the sync? I admit, that there's only 8 GBs+ available but this should be plenty for my user data (~2.5 MB).

     

     


    Theres another thread about this : https://community.f-secure.com/t5/F-Secure-KEY/Not-enough-space-to-synchronize/td-p/83289

  • BenBen Posts: 2,640

    Hello all, 

     

    The Key team is working on new versions to fix these issues. The versions should be available early next week. 

  • mashmash Posts: 19

    Hi Ben, will the new version apply to Android devices as KEY has become really slow on my Samsung Galaxy Tab Pro (SM-T320, Android version 4.4.2.) over the last couple of days.  F-Secure KEY version 4.2.5.

    If you require me to send you the log file, please let me know where it is located.

  • BenBen Posts: 2,640

    The Key team is still working on a fix for this issue.

     

    I'll keep you updated on the development.

  • KorvaooKorvaoo Posts: 7

    Looks like new version is totally unusable Smiley Sad it works fine first day but now cant log in at all.

  • KorvaooKorvaoo Posts: 7

    ...and after x.119 no help, so i tryed reinstal software. Now it tells me i have no space for sync... i could use my passwords on pc's thanks Smiley Tongue

    THof
  • BenBen Posts: 2,640

    Hi all, 

     

    could you try to download the latest android and desktops versions available. 

    Once you devices are up to date, edit or create a new entry on android so that the devices would sync. 

    That should help recovering from the current problems with KEY.

     

     

  • UkkoUkko Posts: 2,995 Superuser

    Hello,

     

    Does it possible that latest (?!) F-Secure Key for Windows platform (.msi-file) not signed (by certificate)?!

     

    Or there any reasons based on my browser (?! I tried to download it just by Internet Explorer 11 64bit, Windows 10).

    Each time.. there not signed .msi-file (previously it was signed). And Smart Screen also noted this... as during try to launch it: the launch is prevented as "not signed application" (by trusted anyone).

     

    I mean just "installer" as .msi-file (which possible to download). Probably other files (?! after/during installation) will be signed (not check it yet)..

     

    Sorry for reply.

     

    Thanks.

    THof
  • THofTHof Posts: 5
    Hi,

    I've downloaded the new version, with absolutely no improvement on performance. (I have a ticket opened for that same issue on a Win7-64bit PC).
    I've tried deleting the F-Secure KEY data, to force a re-sync, and now I can't even get it to sync...
    When I enter the sync code, it starts by telling me it wasn't able to reach the sync server, then it asks for my masterpassword... And finally it tells me there's not enough space to sync my passwords and I'm sent back to the "enter sync code" screen.
    Upon closing the application and opening it again, I'm prompted for my master password, which the application considers as invalid...
    So basically, I'll have to type all of my 30+ characters passwords every single time until this is fixed...
    A major upset as far as I'm concerned.
  • THofTHof Posts: 5
    + unsigned installer, that's not too good.
    Ukko
  • THofTHof Posts: 5
    It does look like a time formatting issue...
     
    My phone (and my PC back when it worked), both indicated an expiration to my subscription on the 1st of March 46206.
    Converting that date to a UNIX epoch, yields somewhere between 1395958406400 (at midnight) and 1395958492799 (at 23:59:59)... If taken as an epoch in milliseconds, this seems awfully close to my original date of purchase, which is logged as (in Pwdmgr.log) 1395926320030 (Thu, 27 Mar 2014 13:18:40.030 GMT).
    Actually, if I take one year off to that date (to presumably retrieve the value before I was last billed on March 27th this year) and convert the 1st of March 46205 to an epoch, I get something along the lines of 1395926870400, which, read as a millisecond epoch equates to Thu, 27 Mar 2014 13:27:50.400 GMT.
    This is honestly much to close to be a coincidence.
    I'm guessing you guys had an issue with subscriptions being considered as valid due to a difference in representations, and tried to fix it...
    However, with the change fixing the subscription expirations by parsing the format correctly, you also introduced a side effect where for every year added to the subscription originally, only 1/1000th (i.e. roughly 8 hours) of a year is now granted. (That is: a year was added to the date as it was read previously, and since the parsing is fixed and no longer reads a millisecond as a second, the years added in the meantime are now only worth a few hours).
     
    Please fix...
  • I'm experience the same problem on win10 64bit. The application is useless and if this not fixed asap I will find another password manager!

  • KorvaooKorvaoo Posts: 7

    latest version on android and both my pc's and works without internet access. As soon as giving permission to net, client freezes and stops response for ever.

    mash
  • mashmash Posts: 19

    @Korvaoo, good tip, thank you.  At least I can now see my passwords.

  • BenBen Posts: 2,640

    Hello Korvaoo, 

     

    Did you already try to make a modification on an entry on the android side? That should trigger the syncing and help resolve the issue. 

  • BenBen Posts: 2,640

    In addition the signing issue should also be now resolved.

     

    Let us know if you still have issues

    THof
  • KorvaooKorvaoo Posts: 7

    It works! thaks :)

  • hopeavalohopeavalo Posts: 2

    I'm still having problems. After giving my master password and clicking Unlock the Key freezes and does not response. Earlier it was just veeeery slow but now it is not responding to anything.

     

    Steps taken:
    1. Android updated automatically on my phone yesterday
    2. I updated Mac client to latest few hours ago
    3. Modified one password in Android
    4. Launched Mac client - Key freezes

     

    I also have Key on my home PC (win10) and few days ago it was having same freeze problem.

  • hopeavalohopeavalo Posts: 2

    OK. No more problem!

    Needed to add step 5: Keep Mac client open for about one hour even if it looks like dead. 

     

    Now Key works normally on my Mac.

  • bluecrossbluecross Posts: 9

    Dos not work at all. latest version is installed (Win10). Cant login at all.

  • BenBen Posts: 2,640

    Hello @bluecross

     

    did you also upgrade your android installation and made a modification on the mobile device?

  • trantakotrantako Posts: 2

    The fix worked for my Win10 PC, but my Mac is now stuck at Key login screen - already several hours. The app doesn't respond to anything. Now what? Already tried re-installing, didn't help.

    Notice that to be able to post this question, I had to reset my F-Secury community password, because that (and all myt other passwords) are now locked by F-Secure Key that suddenly has become worse than ransomware - you can't get your data back even by paying money to somebody.

     

    This issue and how it has been handled has pretty much ruined my trust to F-Secure as a company. The whole idea of using a password manager software requires ultimate trust to the app and its developer, but somehow they managed to create a situation that pretty much locks you out of your own passwords simultaneously across multiple devices and operating systems. The only thing that prevented total catastrophe was that I had Android version of the app that still works (fingers crossed).

    Previously I liked the software and recommended it to my friends and colleagues, even considered taking it in use company-wide in our business, but that is not going to happen anymore. This app has some severe design issues if something like this can happen and keep struggling for so long.

  • bluecrossbluecross Posts: 9

    Android version works well! I can add/change keys by apps. Problem is now Win10 version. It has been upgraded today also.

  • BenBen Posts: 2,640

    @bluecrossthe reason behind making a modification to the android  device is that it will trigger a synchronization with the windows version and that should resolve the problems on PC. If not please get in touch with our support here.

  • mashmash Posts: 19

    After forcing a sync by editing an Android entry as @Ben instruced, the only way I could fix KEY on my PC was to uninstall it (including User Data), reinstall, get sync code from Android KEY and enter this into KEY on my PC.

This discussion has been closed.