Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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

  • 2 antwurd
  • 1 hat dit probleem
  • 1 werjefte
  • Lêste antwurd fan 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.

Keazen oplossing

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

Dit antwurd yn kontekst lêze 👍 1

Alle antwurden (2)

more options

Keazen oplossing

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.