Troubleshooting website display or functionality issues in Edge on Windows 11
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Yesterday (11-5-2025), I started receiving the following error message when accessing Microsoft Rewards via Microsoft Edge.
This page isn’t working right now
If the problem continues, contact the site owner.
HTTP ERROR 400
The issue still occurs today (11-6-2025), and has never occurred in the past.
Is there a way ro resolve the issue?
Thanks,
John
PS: If I refresh the page, I can access Microsoft Rewards; however, it only occurs on initial launch.
Troubleshooting website display or functionality issues in Edge on Windows 11
Thanks for posting to the forum, John. A Bad Request HTTP ERROR 400 in Microsoft Edge when using Microsoft Rewards usually means there's an issue with cookies, large request headers, or cached info. If refreshing helps briefly, the issue likely involves saved session info.
Here’s how to fix it:
Clear Rewards Cookies & Cache: In Edge, go to Settings > Privacy, search, and services > Clear browsing data > Choose what to clear. Pick Cookies and other site data and Cached images and files, set the time to All time, and click Clear. Or, clear cookies just for rewards.microsoft.com via edge://settings/privacy/cookies/AllCookies.
Use InPrivate Mode or Another Browser: If it works in InPrivate, the problem is in your cached cookies or extensions.
Disable VPN/Proxy and Extensions: These can mess with Microsoft Rewards. Turn them off and try again.
Check for Large Cookies: If cookies are too big, Edge gives 400 errors. Clearing them often fixes this.
Update Edge: Go to edge://settings/help to get the newest version.
If it still doesn't work, reach out to Microsoft Rewards support at rewards.bing.com/support.
All the best,
Rez
AI answer
To resolve an HTTP ERROR 400 when accessing Microsoft Rewards in Microsoft Edge, you can try the following troubleshooting steps:
If the problem continues after trying these steps, it may be beneficial to contact Microsoft support for further assistance.
References: