OmniMend
Match the Edge 153 incident
The narrow match is an Edge 153 web application that stops responding while you interact with it. Microsoft says the affected browser window may stop accepting both mouse and keyboard input. That is different from a tab that crashes with an error page, Edge failing to open, or the whole PC freezing.
| Observed symptom | How it fits | What to record |
|---|---|---|
| A web app becomes unresponsive and its Edge window stops accepting input | Matches Microsoft's Edge 153 incident wording. | Full Edge version, web app, tab or installed-app mode, exact action, and time. |
| One tab crashes, but the window still accepts input | Not the same symptom boundary. | Crash message, page URL, extension state, and whether another site works. |
| Edge will not launch | Not enough to assign this incident. | Launch path, visible process, error, update state, and managed status. |
| The pointer, keyboard, and other applications all freeze | Points beyond one Edge window. | Whole-system response, display state, audio, power, and restart result. |
Protect unsaved work first
Before ending the frozen window, check whether another Edge window or another Windows application still responds. Save work in responsive applications. Note any form, draft, upload, call, or transaction that may not have completed. Do not repeat a purchase, submission, or file upload until you can confirm its result.
If the affected window will not respond, capture the time, page or installed web app, exact action, and what remained responsive. Avoid posting private URLs, account names, session tokens, form contents, or customer data in a public support request.
Record the full Edge version
Open Settings and more > Help and feedback > About Microsoft Edge, or enter edge://settings/help in a responsive Edge window. Record the complete version, not only 153. Also record the Windows edition and version, whether Edge says it is managed, and whether the web app runs in a tab or as an installed app.
Microsoft's known-issues page names 153.0.4234.48 as a fixed Stable build. The release notes put the explicit web-application fix under 153.0.4234.46 and list .48 as the later Stable update. This means .48 or a later Stable build is the relevant boundary, not major version 153 by itself.
Update Edge through the supported channel
On the About Microsoft Edge page, let Edge check for an update. If an update is available, use Download and install. If the page says a restart is required, close only after protecting work, then restart Edge to apply it. Return to the About page and read the full version again.
Do not download a browser build from a third-party site or force a rollback to 152. Microsoft's temporary rollback note remains in the incident table, but the same record now names a fixed Stable build. Current guidance should use the supported Stable update first.
If update controls are missing or dimmed, the browser may be managed. Contact the organization instead of changing policy, services, scheduled tasks, or registry values.
Repeat the same action once
Return to the same web app and repeat the smallest safe action that caused the freeze. Keep the account, network, web-app mode, and action the same. Record whether the app accepts mouse and keyboard input, whether the entire Edge window stays responsive, and whether the problem returns after a normal restart.
A successful retest supports the fixed-build path, but it does not prove that every browser or web-app problem is gone. Do not add extension changes, profile cleanup, cache clearing, or Windows repair to the same test.
If the web app still freezes
Confirm the current full Stable version and a completed browser restart. Then preserve the affected app, tab or installed-app mode, exact action, time, Windows version, managed status, and whether another web app remains responsive. Microsoft's release notes tell users with similar symptoms after the latest Stable update to contact Microsoft Support to confirm whether another fix is needed.
A workplace or school device belongs with its administrator. If one specific service fails across multiple browsers or devices, check that service's official status and support path. Do not erase the Edge profile or browsing data before support has the original evidence.
Keep other freeze symptoms separate
If a single Windows application hangs outside Edge, use the app not responding guide. If the pointer, keyboard, audio, and other applications freeze together, use the Windows 11 freezing guide. If a browser tab crashes rather than becoming unresponsive, use the browser tab crash guide.
Do not assign the Edge 153 incident from timing alone. The full browser version and the exact input failure are the useful gates.
Where OmniMend fits
On a supported Windows x64 PC, OmniMend can organize read-only Windows, application, event, update, configuration, and retest evidence around a freeze. Diagnosis is read-only. A supported repair inside OmniMend requires approval and a result check.
OmniMend does not update or roll back Edge, change browser policy, clear a profile, recover unsaved web-app data, repair a website, or replace Microsoft, the service owner, or an organization administrator.
If you want a separate Windows evidence record, review OmniMend's diagnostic scope or download OmniMend. Read the privacy information before sharing a report.
Editorial sources
Checked September 23, 2026 against Microsoft Learn's Edge known-issues record and Stable Channel release notes, plus Microsoft Support's Edge update settings. A September 17 independent report and a recent user report support timing and symptom language only. Microsoft supplies the symptom boundary, fixed-build status, update route, and support handoff. OmniMend added the evidence order, retest limit, related-guide routes, and product boundary. No source establishes an affected-user count or supports profile deletion as the first step.