KEY takes lot of resources in Windows 10 and slows browser!
McNano
Posts: 2
I updated my computer to windows 10 and continued using KEY, but i got big problem after that key takes like 3-4 % of my proserssor capacity (intel i7 5820K) when it's running. It also slows my firefox a lot when i type something or click something in browser it will take 0,5 to 2s to respond depending on time. same problem is also when using chrome but delay time is bit smaller. When i kill F-secure KEY prosess everythign works fast as it should be. This problem wasn't on windows 7 or windows 8.1 what i was using before. And it has become problem for all my three desktops after upgraded to Windows 10. Problem is still there even if i make clean install and install KEY first then the problem starts.
How iu solve this problem? It's really anoying to open KEY everytime when i need pasword and kill it just after.
Answers
I've been searching hours for the cause of exactly the same problem as stated above. Finally after killing process after process I've found f-secure key to be the problem.
Really disapointed by the new update. Currently I'm not able to use the software without delaying my webbrowsers ten fold.
Are there any plans to fix this. I'm a premium user, how do I get support on this?
Hello
@McNano are you already using the latest version 4 released recently?
@Rbbiz1 do you experience that on every browsers?
Could you try to disable autofill under Settings->General and see if problem persists?
I had it in Chrome and FF. Turning off autofill doesn't seem to fix it
I have been using it and also previous and both had same problem.
For me disabling that autofill from settings helped on firefox. But I haven't tested on Chrome yet.
Hi,
@Rbbiz1 can you confirm that the delays are still as important after disabling the autofill? This should resolve this type of issues.
@McNano thanks for the confirmation. The option to disable the autofill was only introduced in v4.0.102
It's better after the disable. Are you going to fix this issue? What function did I actually disable?
Hello Rbbiz1,
Thank you for your feedback. The function you disabled is explained in this article.
Our development team is already working on solutions to this problem.
It would be great if you could fix the autofill issue with KEY so it will no longer hammer the RAM and CPU. It is a very convenient function to have and it would be nice to be able to use it. It works great on my Mac, but on my Windows machine (which I use for work), KEY with autofill enabled completely renders my CRM software pretty much useless. That is a shame.
I love using KEY and have completely moved from LasPASS, but some things HAVE to be fixed in the versions to come.
I can report this same issue. With about 3 chrome windows open, F-Secure KEY will start using around 10-15% of CPU time in Windows 10 (upgraded from 7)
Disabling autofill makes the problem go away, but of course renders the KEYs main functionality useless.
Hello @MisterStuart @aarneo,
Thank you for reports. Some solutions are in the testing on that topic and we are trying to provide them as soon as possible.
If you want to do some software-specific testing, you can try to see how KEY works alongside Connectwise software http://www.connectwise.com/ (the CRM my company uses). It is pretty much unusable when KEY is running; even when autofill is turned off it's still very slow.
I also just wanted to take a moment to say that since LastPASS recently sold to LogMeIn there has been a MAJOR backlash of users who are looking to switch to another password manager. Currently a lot of companies that provide password management software and the space is rather crowded, but few do it well. F-Secure KEY really has a chance to seize this opportunity and fix issues with the software and make it AWESOME to attract new users. I really, REALLY want to use F-Secure KEY as my everyday password manager, but it just eats up too many resources so I am forced to go back to using LastPASS for the time being (even though I'd rather not). You all have the chance to really pick up some new users if you get things working properly. I, for one, will be telling everyone I know to switch to F-Secure KEY once all of the performance issues have been worked out, but until that happens, I cannot (with good conscience) recommend it as a good alternative to LastPASS.
Hi Ben. Just wanted to check in with you to see how those new solutions tests are coming along? Making any positive progress?
Cheers,
-mr. stuart
Hello Misterstuart,
We are already testing some solutions. But it will take time to reach production or you device. I'll try to let you know of the progress.
Hi there....any update please?
Check this thread: https://community.f-secure.com/t5/F-Secure-Key/What-happened-to-F-Secure-Key/td-p/78472
Thanks for the link.....fingers crossed....I'm guessing that browser plugin is similar to others.....
I agree, but as long as the plugins work and the new version reduces system load, then I don't really care! I just really want to get away from LastPASS, but I can't since it's the best solution at the moment. I have faith that KEY will be good soon. I had a thorough explanation from the developers that all of the issues are due to the Windows 10 access issues. The plugin will help I think.