Windows 10 Is Quietly Force-Upgrading You to Chromium Edge

If you’re running Windows 10 and you open Edge this week and it suddenly looks different, that’s not a bug. Starting with the April 13 Patch Tuesday cumulative update, Microsoft is automatically swapping out the legacy EdgeHTML-based Edge for the Chromium-based version, delivered straight through Windows Update. No opt-in, no dialog asking permission — it just happens as part of your normal monthly patch cycle.

This has been coming for a while. Microsoft first shipped the Chromium-based Edge back in January 2020, and ever since then the plan was always to eventually retire the old EdgeHTML engine entirely rather than let it linger as a second, unmaintained browser sitting on millions of machines. This week’s rollout is the next big step in that phase-out, and it’s a meaningful one because it’s happening at the OS patching level rather than requiring anyone to manually download the new browser.

Why this matters more than it sounds

A lot of people never touched Edge at all, old or new, because Chrome and Firefox dominate market share. But EdgeHTML Edge is the default browser on a huge number of Windows 10 installs — kiosks, corporate machines, grandma’s laptop, whatever. Those users get quietly moved to a fundamentally different browser engine with different extension support, different rendering behavior, and a different UI. For most people this is a strict upgrade: better standards compliance, access to the Chrome extension store, faster JavaScript performance. But it’s still a forced change happening in the background, and that’s worth knowing about even if you don’t care which browser you use.

There’s also a security angle worth flagging. EdgeHTML hasn’t been getting the kind of engineering attention Chromium gets, and Chromium’s security response cycle is faster and better resourced simply because of how many organizations (Google, Microsoft, Brave, Opera, Vivaldi, and others) all have skin in the game. Consolidating Windows users onto a single, well-maintained rendering engine is a genuine security win, even if it comes with the mild annoyance of losing a UI you were used to.

If you’re an IT admin managing a fleet of Windows 10 machines, this is the kind of update you want to know is coming rather than discover after a help-desk ticket flood. Microsoft has offered enterprise tooling to block or delay the swap before, and I’d expect similar controls to apply here, but the default behavior for unmanaged consumer machines is clearly “just do it.”

None of this affects Windows 7 or 8.1 users, who already had to manually install the new Edge if they wanted it, since it doesn’t come bundled with those OS versions. But for the Windows 10 majority, EdgeHTML’s days as an actively-installed browser are numbered, and this patch is the moment that stops being theoretical.