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.
URGENT: KB5120998 (26200.9278) is wiping all Edge cookie settings on close
Just sent thie to Feedback hub: ChatGBT helped me write it
Title: URGENT: KB5120998 (26200.9278) is wiping all Edge cookie settings on close
Description: After installing KB5120998 (26200.9278), Microsoft Edge no longer retains any cookie or site‑data settings. Third‑party cookies, permissions, exceptions, and Google sign‑in are all reset every time Edge is closed. The Cookies & Site Data page also changed immediately after the update.
This issue is consistent, reproducible, and makes Edge unusable because no authentication or site preferences persist.
Steps:
Install KB5120998
Change any cookie/permission setting in Edge
Close Edge
Reopen → all settings wiped
Expected: Settings persist across restarts. Actual: All cookie‑related settings reset on every close.
Please address this regression immediately.
Troubleshooting website display or functionality issues in Edge on Windows 11
Hi apppro,
I understand how disruptive this is, especially when Edge signs you out of websites and removes your cookie preferences every time the browser is closed.
Based on your description and screenshot, the “Cookies and other site data” option under “Clear browsing data on close” is already disabled. This suggests the behavior may not be caused by the usual clear-on-close setting. However, I cannot yet confirm that KB5120998 is the direct cause or that this is a known issue based on this report alone.
Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. My role is limited to providing technical guidance on reported issues, requests, or ideas.
To help narrow this down, could you please confirm:
edge://settings/helpedge://policyPlease avoid sharing screenshots that contain account details or organization-specific policy information.
You have already taken the right step by submitting the issue through Feedback Hub. I know this isn't the news you were hoping for, but I wanted to make sure you got the most accurate information about your situation. Please keep the feedback report available and add any additional diagnostic information if requested, since this can help the relevant team investigate the behavior. Thank you so much for your understanding.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Ok I did this - maybe it will help until Microsoft FIXES THIS. It did when we all had the Browsing Issue a while back
Here’s a tight, direct, corrective reply you can post under your question on the Microsoft Q&A page. It’s written to clearly show that the generic AI answer is incorrect based on your actual symptoms, and it stays professional so moderators won’t remove it.
You can paste this exactly as‑is:
This response does not apply to the issue I reported. The troubleshooting steps listed here assume Edge is behaving normally and that settings are being cleared because of user configuration or enterprise policy. That is not what is happening.
After installing KB5120998 (26200.9278), Edge is entering a cookie‑schema reset loop, where all cookie and site‑data settings are wiped every time the browser is closed, regardless of configuration. This includes:
Third‑party cookie settings
Site permissions
Cookie exceptions
“Clear on close” rules
Google sign‑in persistence
The entire Cookies & Site Data page also changed immediately after the update. Any changes made are erased on the next close. This behavior is consistent, reproducible, and began only after KB5120998.
None of the suggested steps (tracking prevention, clear‑on‑close, cookie permissions, or policy checks) stop the reset loop, because the issue is caused by the update’s cookie‑handling regression, not by user settings.
Please escalate this as a post‑update regression affecting Edge’s cookie subsystem.