Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

Since Win 10, every mouse and keyboard input in FF takes 2 secs. to take effect.

  • 2 valiny
  • 1 manana an'ity olana ity
  • 1 view
  • Valiny farany nomen'i MrWonderful

more options

Since installing Windows 10, it takes a full second or two for a scrolling move (e.g.) to take effect. I'll turn the scroll wheel, and it will take 2-3 seconds for the page to actually move. Same thing waiting for a neutral cursor to turn into a "live" hand. In fact, I'm writing this via Chrome, since FF has becomes so slow and frustrating.

Since installing Windows 10, it takes a full second or two for a scrolling move (e.g.) to take effect. I'll turn the scroll wheel, and it will take 2-3 seconds for the page to actually move. Same thing waiting for a neutral cursor to turn into a "live" hand. In fact, I'm writing this via Chrome, since FF has becomes so slow and frustrating.

Vahaolana nofidina

What is your computer system and Firefox?

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options)
key, and then starting Firefox. Is the problem still there?


Start your Computer in safe mode with networking. Then start Firefox. Try Safe web sites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

Hamaky an'ity valiny ity @ sehatra 👍 1

All Replies (2)

more options

Vahaolana Nofidina

What is your computer system and Firefox?

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options)
key, and then starting Firefox. Is the problem still there?


Start your Computer in safe mode with networking. Then start Firefox. Try Safe web sites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

more options

I didn't have to do this, because a different solution worked--re-starting FF. Thanks.