Other issues or features related to Microsoft 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.
We are experiencing a reproducible issue where Microsoft Edge stops accepting all touchscreen input after additional tabs are opened or you click a couple of times on taskbar.
When the problem occurs, users cannot:
Microsoft Edge continues to respond normally to the touchpad, mouse and keyboard. Touch functionality elsewhere in Windows remains available.
Changing focus to another application and then returning to Edge temporarily restores touchscreen functionality.
The issue does not occur in Google Chrome under equivalent testing.
Testing confirmed that reverting an affected device to Microsoft Edge version 152.0.4191.53, which was in use on 27 August 2026, resolves the issue. This indicates a possible regression in a subsequent Microsoft Edge release.
Other issues or features related to Microsoft Edge on Windows 11
Focus toggle: Alt+Tab away and back, or tap the taskbar icon. You already found this restores touch temporarily.
Hardware acceleration: turn it off in edge://settings/system and retest. This often changes input and compositor behaviour.
Clean profile: run msedge.exe --guest or use a new profile with no extensions. That rules out extensions.
Flags: check edge://flags for touch or pointer-event entries and test one at a time.
Pause the update: on managed machines, pin the version with the Edge update policy TargetVersionPrefix and RollbackToTargetVersion. Test this on one device first.
Getting it fixed
Send feedback from Edge itself with Alt+Shift+I. Include the version, edge://version, the repro steps and the finding that 152.0.4191.53 works.
AI answer
This matches a known Edge regression introduced after 152.0.4191.53.
The closest documented fix is in Edge Stable 153.0.4234.46, which states that it fixed an issue where some web applications became unresponsive during user interaction and the affected browser window froze and stopped responding to mouse or keyboard input. For cases that continue after updating to the latest Stable version, the documented next step is to contact Microsoft Support to confirm whether additional fixes are required.
Based on the documented Surface and Windows guidance, the practical validation path is:
If a temporary mitigation is needed while validating the fix, the evidence provided supports staying on 152.0.4191.53 until the latest Stable build is tested.