When you enter whatsapp web site, the page show a message asking you to update google chrome. “WhatsApp works with Google Chrome 36+”
I have the same issue, Yesterday it worked fine. Has Whatsapp updated their web.whatsapp.com or what has happened ?
What version of Chrome is the secure browser based on ?
V70
When I use Google Chrome or Mozzilla Firefox, I have no problem. When I use Avast Secure Browser, sometimes the problem comes.
Also have the same issue since updating to V70, now i have to keep a google chrome window open just for whatsapp web
Hi guys, I forwarded it to the devs.
Hi Guys,
I’m sorry for the delayed response. This is being caused by how the WhatsApp website performs the browser detection. This can be worked around by enabling “Anti-Fingerprinting” in the Security & Privacy Center (to open Security & Privacy Center, click the Avast logo next to the menu icon to the right of the address bar).
I too am having this problem, and the “fix” mentioned above does not do anything for me unfortunately. I have tried turning every part of the security center off, rebooting the browser as well as my pc, but the whatsapp website still tells me:
WhatsApp works with Google Chrome 36+
To use WhatsApp, update Chrome or use Mozilla Firefox, Safari, Microsoft Edge or Opera.
I have the same issue today, Yesterday it worked fine. Has Whatsapp updated their web.whatsapp.com or what has happened ?
I even downloading the latest version of Avast secure browser, and reboot pc, still the same error.
Anyone have the solution?
Short of having BWhit, an avast team member rejoin the topic, best contact WhatsApp devs.
Hi arjan.janissen and Seemon, I’m sorry that the issue is persisting for you. As mchain says, the only permanent resolution to this is for the WhatsApp devs to change how they detect the browser. For the workaround, rebooting should not be necessary, but the Anti-Fingerprinting component must be turned on (the other toggle-able Security Center settings are unlikely to affect the issue).
Some users have reported that the workaround wasn’t effective until they had used the Privacy Cleaner (accessible from the Security Center) to clear “Cookies and other site data”, “Cached images and files” and “Passwords and other sign-in data”. I would advise to close the WhatsApp website, use the Privacy Cleaner to clear this data (Open Privacy Cleaner from the Security Center, click the “Advanced” tab, select the Time range for “All Time”, select the listed items and click “Clear Data”), and then attempt to open the WhatsApp website again.
Please let me know if you still experience any further issues with the website.
Still not working and whatsapp web recommend to use chrome, firefox etc.
Posting in an old threat is never a good idea.
Start your own topic and give as much detail as possible.
“Some users have reported that the workaround wasn’t effective until they had used the Privacy Cleaner (accessible from the Security Center) to clear “Cookies and other site data”, “Cached images and files” and “Passwords and other sign-in data”. I would advise to close the WhatsApp website, use the Privacy Cleaner to clear this data (Open Privacy Cleaner from the Security Center, click the “Advanced” tab, select the Time range for “All Time”, select the listed items and click “Clear Data”), and then attempt to open the WhatsApp website again.”
Used the above method, still not working.
I have to used firefox or chrome to solve the problem!
Starting with April 8, 2020, the Whtasap web failed again. It workd until the day before.
Although the solution provided above worked during 2019, this time it does not work anymore.
Is there a way to make Avast Browser to report browser identity as Chrome?
Hello, im having the same issue and i did all the indicated steps.
Does any one know who to fix it?
Hi. I would like to take a deeper look into this problem, but I cannot recreate it on my side. Could you please send me a screenshot of secure://settings/diagnosticInfo ? It should help me to find a solution to your problem.
Hi guys,
Those problems should be fixed in version 80.1 that we started to deploy recently to all users.
Could you please check that you were already updated to 80.1 (secure://settings/help) and if the issue still persist there?