Edge 157 Stable: update to 157.0.4341.42

If Microsoft Edge on your home PC or Mac still shows 156.x, you have a new finish line. On Thursday, November 5, 2026, Microsoft shipped Edge 157.0.4341.42 on the Stable channel. The security release notes say that build incorporates the latest Chromium security updates. The Stable channel notes list it as the main Edge 157 release.

This replaces our Edge 156.0.4314.56 note. Updating Chrome does not update Edge. Updating Edge does not update Chrome. Same habit: install, fully quit, relaunch, then prove it with edge://version.

What Microsoft shipped on November 5

From Microsoft’s security notes for November 5, 2026:

• Stable: Microsoft Edge 157.0.4341.42 incorporates the latest Chromium security updates
• Microsoft says CVEs will be added as soon as they are available

You do not need the full CVE table to act. You need the new build running.

Outside Microsoft’s notes, GovCERT.HK’s November 6 alert says Edge versions prior to 157.0.4341.42 are affected by multiple browser vulnerabilities. Successful abuse could lead to remote code execution, denial of service, information disclosure, security-restriction bypass, or tampering. The recommended fix is 157.0.4341.42 or later. HKCERT’s November 9 bulletin repeats the same fixed build and lists many CVE IDs tied to that update window. Treat those pages as independent confirmations that 157.0.4341.42 is the Stable target, not as a reason to invent attack stories Microsoft has not claimed.

The same day Google already had Chrome 157 Stable rolling with a large Chromium security batch. Edge’s security note does not re-list every Chromium CVE yet. Install Edge 157, then confirm the running build yourself.

Why 156 is not enough anymore

If edge://version still shows 156.0.4314.56, 156.0.4314.58, or any other 156 build on the everyday Stable channel, you did the right thing earlier. You still need 157.0.4341.42 (or a newer 157 Stable build if Microsoft already moved past it).

If you are on Extended Stable instead of normal Stable, Microsoft’s channel table for this week lists 156.0.4314.70 (November 5, 2026) as the Extended Stable minor update. That is a different train. Most home readers are on ordinary Stable and should land on 157.0.4341.42.

Same habit every time:

1. Update
2. Fully quit and relaunch
3. Prove it with edge://version

An update that has downloaded is not running until Edge restarts. The version page shows what is actually running.

Everyday changes worth noticing after you patch

Microsoft’s Stable notes for 157.0.4341.42 also call out a few home-visible changes. Patch first. Then poke at these if you care:

• Faster launches on some Windows 11 builds. Edge on Windows now supports Accelerated App Launch, which Microsoft says opens Edge more consistently when the browser is already running in the background. It is enabled on Windows 11 versions 25H2, 26H1, and 26H2, and needs Edge 150 or later. See Microsoft’s Accelerated App Launches note for the wording.
• Apple account sign-in. You can sign in to Edge with an Apple account from the profile menu, in addition to a Microsoft account.
• Fading tabs are gone. The Fade inactive tabs setting is removed. Tabs no longer fade.
• Clearer memory info on tab hover cards. Hover cards now separate preview images from memory-usage details.
• Rare sign-in again. Microsoft finished retiring a legacy Windows sign-in path in 157. Most people notice nothing. A few profiles may need to sign in to Edge again after the update.

Skip the administrator XSLT and policy theater in this write-up. On a home PC, the job is still the build number.

How to update and verify on a home PC or Mac

1. Open Microsoft Edge on the computer you browse with.
2. Check for updates:
   • Windows / Linux: Menu (three dots) > Help and feedback > About Microsoft Edge.
   • Mac: Edge menu > About Microsoft Edge.
3. Stay on that page until the download finishes and Edge offers a restart, or until it already shows 157.0.4341.42 (or a newer 157.0.4341.x).
4. Restart when prompted. Do not click Later and leave old windows open for hours.
5. If the version still looks old, fully quit Edge (every window). On Windows, confirm no leftover msedge.exe helpers in Task Manager. On Mac, use Edge > Quit Microsoft Edge. Open Edge again.
6. Type edge://version in the address bar. You want 157.0.4341.42 or a newer 157 build.
7. Repeat on other machines you use, including a laptop that sleeps with Edge still open and any shared family PC.

If About Edge does not offer 157 yet, give it a day, then check again. Prefer Edge’s own About page or Microsoft’s download links over random “Edge offline installer” packs.

Phone Edge is separate

Desktop Edge updates do not patch Edge on your phone. Microsoft’s security notes list Edge for Android and iOS on their own dates; the most recent mobile entry around this window is 156.0.4314.56 on November 2. Check Google Play or the App Store on the phone, update, then open the app once so the new build actually launches.

Do this / don’t do that

Do

• Force About Microsoft Edge, relaunch, and confirm edge://version shows 157.0.4341.42 or newer.
• Install the Stable jump today rather than waiting for the weekend.
• Keep Chrome, Firefox, Safari, and Brave on their own update habits if you use more than one browser at home. Firefox 159.0.1 is a separate checklist.

Don’t

• Do not stop at 156.0.4314.56 because you “already did Edge 156.”
• Do not assume a Windows Update reboot alone refreshed Edge if edge://version is still on 156.
• Do not wait for Microsoft’s CVE list to fill in before updating.
• Do not download random Edge installer packs from third-party sites.

Bottom line

Microsoft’s November 5, 2026 Stable release ships Edge 157.0.4341.42 with the latest Chromium security updates (security notes, Stable notes). Independent alerts from GovCERT.HK and HKCERT treat that build as the fix line. On your own computer: open About Microsoft Edge, install, fully quit and relaunch, confirm edge://version. That is the whole job.

Image: Official Microsoft Edge page art from microsoft.com/edge.