Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

recaptcha problem

  • 7 отговора
  • 13 имат този проблем
  • 171 изгледи
  • Последен отговор от cor-el
  • Архивирани

Until yesterday everything was fine. I was able to complete recaptcha. But when I tried searching something today, I couldn't do it because of the recaptcha. It was stuck on infinite loading. Every website I visited the problem was there. I tried fixing it from the tips I found in the forum here but nothing seems to work. I was frustrated. Then I tried Brave browser and it was working. Please help me fix this problem. Thank you.

Until yesterday everything was fine. I was able to complete recaptcha. But when I tried searching something today, I couldn't do it because of the recaptcha. It was stuck on infinite loading. Every website I visited the problem was there. I tried fixing it from the tips I found in the forum here but nothing seems to work. I was frustrated. Then I tried Brave browser and it was working. Please help me fix this problem. Thank you.

Всички отговори (7)

Try clearing site cookies and disabling Tracking Protection for the site.

Does it still happen in Troubleshoot Mode?

Yes I did all of that. But the problem remains.

Only Firefox with a Windows user agent seems to be affected by this issue with reCAPTCHA not working. It works for me with a MAC user agent and with a Linux user agent. You can use a User-Agent Switcher extension and set the user agent to Chrome or Edge on Windows 11.

This has been reported to Google, so wait until Google fixes this and then undo this temporary fix.

Thanks a lot man. I'll try that. Any idea why is it happening?

Tried but still doesn't work.

You may need to clear site cookies for the change to take effect.

From this closed bug it looks that Google has fixed this issue, so you can test this by disabling the extension and use the default user agent.