I've noticed as of late when running Firefox - that KPM is responsible for lagging out text box entry and password fields.
As required - System information below -
Windows 11 Professional - Version 22H2 - OS Build : 22622.575
Kaspersky Installation Version - 21.3.10.391(h)
Firefox Version - 103.0.2 (64 bit)
When I'm running Firefox, a clean and fresh installation - all plugins disabled (tested in safe mode too), I have observed that KPM is responsible for slowing down text input, password fields and general communication through the browser. Disabling the plugin - is the only solution to ensuring that the problem does not occur. It is 100% repeatable and has become somewhat troublesome, especially as I type rather speedy. So I tend to finish my paragraph and then watch it slowly clacker its way into the text field.
Referring to User - Freud2004 in the thread written below - reveals the same issue, however, from 2 years prior. In terms of support, are there any planned fixes for this?
I patiently await your reply,
Sincerely,
PJG
Featured Replies
Please sign in to comment
You will be able to leave a comment after signing in
Good evening all,
I've noticed as of late when running Firefox - that KPM is responsible for lagging out text box entry and password fields.
As required - System information below -
Windows 11 Professional - Version 22H2 - OS Build : 22622.575
Kaspersky Installation Version - 21.3.10.391(h)
Firefox Version - 103.0.2 (64 bit)
When I'm running Firefox, a clean and fresh installation - all plugins disabled (tested in safe mode too), I have observed that KPM is responsible for slowing down text input, password fields and general communication through the browser. Disabling the plugin - is the only solution to ensuring that the problem does not occur. It is 100% repeatable and has become somewhat troublesome, especially as I type rather speedy. So I tend to finish my paragraph and then watch it slowly clacker its way into the text field.
Referring to User - Freud2004 in the thread written below - reveals the same issue, however, from 2 years prior. In terms of support, are there any planned fixes for this?
I patiently await your reply,
Sincerely,
PJG