Edge 153 Bug Freezes Web Apps with Complex Rollback Fix

A newly identified defect in the latest release of Microsoft Edge is locking up web-based applications, rendering windows unresponsive to mouse and keyboard input. The issue, which shipped in version 153, has disrupted workflows for users who rely on browser-based tools for daily tasks, turning simple interactions into frustrating stalls.

Microsoft has acknowledged the problem and advised users to downgrade to version 152 as the primary solution. However, the company does not offer a simple toggle or automatic rollback feature. Instead, users must manually disable updates and use command-line tools to install an older version, a process that requires technical comfort and carries the risk of errors.

Web apps remain critical for daily work

For many professionals, web apps are not just convenient options but essential tools. Services like Slack and Airtable often lack native desktop applications or offer wrapped versions that provide little additional value over their browser counterparts. As reported by GN technics/software (en-US), many users prefer the flexibility of managing these services directly within their browser tabs, allowing for easier multitasking and integration with other desktop utilities.

The freezing behavior undermines this workflow by halting active sessions. While switching to an alternative browser like Chrome or Firefox can serve as a temporary workaround, it is not a permanent fix for those who prefer the Edge ecosystem. The lack of a native, one-click rollback option means that the burden of resolving the issue falls entirely on the user, who must act quickly to restore functionality.

Manual rollback requires administrative access

Reverting Edge to version 152 is a multi-step procedure that involves modifying system settings. Users must first open the local Group Policy Editor to disable automatic updates for the browser. This prevents the system from immediately overwriting the older version with the defective update. Without this step, any manual installation would likely be replaced within minutes.

After disabling updates, users need to download the specific MSI installer for version 152 from Microsoft's official site. The final step involves running a command in the Windows command prompt with administrator privileges. This command forces the installation of the older package, bypassing standard version checks. The process is tedious and requires precise input to avoid system instability.

Trade-offs of the manual workaround

While this method resolves the freezing issue, it introduces its own set of risks. Disabling automatic updates means users will not receive future security patches or bug fixes until they manually re-enable the update service. This creates a window of vulnerability where the browser may lack critical protections against emerging threats.

The complexity of the fix highlights a significant gap in user experience for enterprise and individual users alike. A simple software update should not require command-line knowledge to undo. Until Microsoft provides a more accessible rollback mechanism, users must weigh the immediate stability of an older version against the long-term security benefits of staying current.