Persistent problems with auto-fill

Any suggestions regarding persistant misbehaviour of auto-fill? For the past month or two it's been next to useless on chrome on both home and office PCs. Have reinstalled add-in, ensured running applications as administrator, reinstalled programe, turned browser autofill on/off and it fixes it on occasion but the fix is temporary. The link between the add-in and application seems the problem: even when apparently active in the add-in and logged in to the app, the command to lock key from the add-in does not work and nor does the password call-down. At a loss as to what to do, so any suggestions welcome. 

Best Answer

  • UkkoUkko Posts: 2,960
    Accepted Answer

    Hello,

     

    Sorry for my reply. I'm only an F-Secure user (their home solutions).

    OS is Win 10 Pro and Key v is 4.8.110

    just as my own feedback. I tried to install F-Secure KEY and Google Chrome under my Windows 10 system.

     

    And it was possible to lock KEY from Google Chrome F-Secure KEY extension (and autofill?! entries - but I did not check it enough).

     

    My F-Secure KEY version (as clean installation) was something like 4.9.58.0 (probably there available some updates compared to your build; executable setup file is signed at 26.06.2018). And Google Chrome is 68.0.3440.84 (64-bit).

    Maybe good to try from upgrade KEY (before suggested Chrome reinstallation).

     

    Thanks!

Answers

  • SethuSethu Posts: 571

    Hi @RedJim,

     

    Thank you for trying  out some troubleshoot steps, we have had several customer affected that after upgrading to version 4.3.108, the autofill functionality in F-Secure KEY check not working.  Have you performed the steps from this article ? 

     

    If yes, but the issue still reamin. May I know the version of F-secure KEY and your operating system? 

  • RedJimRedJim Posts: 12

    Yes, the chrome extension is installed, was reinstalled, and the problem persists. ctrl-F2 or icon don't bring up the password drop-downs despite the add-in seemingly recognising key being open. OS is Win 10 Pro and Key v is 4.8.110

  • SethuSethu Posts: 571

    Hello @RedJim,

     

    Thank you for providing us the version of F-secure KEY app, its hard to say without analyse the diagnostic report or remote the affected machine's. Because there are a number of problems that can manifest from cached data stored on your computer. In some case,  the clearing browser cache not working in usual way due to browser files corrupted, as such we were able to solve the issue for some customer by performing completely Uninstall & Re-Install Google Chrome and then try to enabling the F-secure KEY extenstion with Chrome browser successfully. 

     

    If you are unable to perform the steps, the best way to reach our Chat support or Phone support

  • RedJimRedJim Posts: 12

    Bingo. Perhaps there's an auto-update 'new version' prompt that wasn't pushed out to the existing versions. Reinstalled what seems to be the most recent key from the website msi rather than my auto-update version and the fresh install reconnected the browser/program communications issue. I think this has fixed it: thanks! :) 

    Ukko
This discussion has been closed.