According to Microsoft's Stable channel release notes, version 156.0.4314.42 is the October 22, 2026 Stable main release. Microsoft summarizes the user-facing changes as "Updates to permissions, autofill, credentials, and managed startup in Microsoft Edge." PiunikaWeb, which first reported the release, said the 156.0.4314.42 update was already available on its test laptop. Microsoft rolls Stable updates out progressively over one or more days, so if your PC doesn't have it yet, it should arrive soon.
The headline features
Site permissions now look the same everywhere
Microsoft says site permissions have been reworked so they behave the same way on a website that asks for access and in Settings. When a page requests a permission, both the address bar (the Omnibox) and the Page Info dialog have changed. Microsoft also says permissions are now easier to find and change later in Settings.
Windows Mode, which also covered the release, put it simply: site permissions "look and work the same in the address bar, the site information panel and Settings".
This matters because permission prompts are a well-known security weak spot. When the prompt, the Page Info controls and the Settings page all look different, people tend to click whatever makes the dialog go away. A consistent design won't stop careless clicking, but it makes "what did I allow, and how do I take it back?" a much easier question to answer.
What Microsoft doesn't say: it doesn't list which permissions are affected, and it doesn't promise every user will see the new design right away.
Autofill can now fill in passports and driver's licenses
On desktop, Edge can now autofill more document types, including passports and driver's licenses, plus what Microsoft calls "other specialized forms." This works in addition to your saved addresses.
PiunikaWeb called this the most practical part of the update for anyone who regularly fills in government or travel forms. That's fair: anyone who has typed a 9-digit passport number into three airline forms in one evening will appreciate it.
Keep your expectations realistic, though. Microsoft's notes don't say:
- which countries are supported
- which document fields Edge recognizes
- where the feature lives in Settings
- whether every form will be detected correctly
Badly built government websites will still be badly built. Also think about what you're storing. A passport number kept in your browser is only as safe as your Windows account and your Edge profile. If you share a PC or a profile, decide carefully whether this convenience is worth it.
The key icon now opens full login details, with notes
The key icon in the address bar now does more. Pick any saved login from it and you get a detailed panel where you can:
- copy the username
- reveal and copy the password
- add a personal note to that login
Microsoft gives three examples of what a note might hold: security questions, what the account is for, and recovery details. All of this works without opening Settings or the full password manager. Windows Mode points out that the key icon is part of Microsoft Password Manager, which added passkey sync in late 2025.
A word of caution, based on general security practice rather than anything Microsoft has published: the release notes don't explain how these notes are encrypted or protected. Storing recovery codes next to the password they recover puts both keys in the same place. A dedicated password manager with a strong master password and MFA is still the safer place for your most sensitive accounts.
What changes for managed PCs
Users can choose whether Edge starts with Windows
On managed devices, Edge is adding an opt-in prompt that lets users decide whether the browser opens automatically when Windows starts. Administrators can control this with the LaunchEdgeOnWindowsStartupEnabled policy, which supports three settings: opt-in, opt-out, and user choice.
Microsoft calls this a controlled feature rollout, so many users won't see it yet. To be clear, this is an optional choice. It is not a new default that makes Edge launch on every work PC. As Windows Mode put it, "It's a gradual rollout, and your IT team can set the choice for you."
Fix: Edge wouldn't open after a scheduled update restart
Version 156 fixes a bug where some users with existing browser profiles couldn't launch Edge after a scheduled update restart triggered by the Microsoft Edge management service. Microsoft's known-issues page says the problem hit some users who had upgraded to Stable 155, and that 156.0.4314.42 fixes it.
Before the fix, Microsoft's workaround for affected devices had two parts:
- Turn off the scheduled update-restart task in the Edge management service.
- Delete the contents of the
Microsoft Edge User Data\Policyfolder, keeping thePrimary Accountfile.
That workaround is only background now. On 156 you shouldn't need it, and nobody should be deleting profile data as general housekeeping.
PDF reader policy deprecated, but the reader isn't changing yet
PiunikaWeb described this as "a shift to a new PDF viewer," which needs some clarification. Microsoft's notes say that as part of the transition to the new PDF viewer experience, Microsoft Edge version 156 marks the NewPDFReaderEnabled enterprise policy as deprecated. The policy becomes obsolete at the earliest with Microsoft Edge version 162.
So this release doesn't switch you to a new PDF viewer or remove the old one. What it does is start the clock on a policy. If your organization uses NewPDFReaderEnabled to keep users on a particular PDF experience, you now have a few releases to test before it stops working. With the two-week cadence, that could come sooner than you'd think.
Other policy changes
Three policies are worth checking in your baselines:
- New:
RemixAvailability(controls whether Remix is available) - Deprecated:
AutofillAddressEnabledandAutofillCreditCardEnabled - Deprecated:
NewPDFReaderEnabled(see above)
Microsoft doesn't say what replaces the two autofill policies. Organizations that use them to block autofill for addresses or payment cards should watch future release notes closely, especially now that autofill covers identity documents.
Coming in version 157: the old Windows sign-in method goes away
Separately from what ships in 156, Microsoft says Edge plans to retire its legacy direct-WAM sign-in implementation on Windows in version 157, completing the transition to OneAuth. OneAuth continues to use Windows Web Account Manager (WAM) internally; WAM itself is not being deprecated.
In plain terms, Edge is dropping its old way of calling Windows' account broker directly. WAM itself stays. According to Microsoft, "The vast majority of users have already transitioned automatically with no interruption." Any remaining profiles will switch over when they update to 157. In rare cases, users may have to sign in to Edge again.
Microsoft's suggested checks for admins:
- Open
edge://signin-internalsand look under Edge Auth Library Information → Library for any managed profiles that still show WAM. - To test early, or to check profiles that previously had the transition disabled, close every Edge process, including background processes, and then launch
msedge.exe --enable-features=msForceOneAuthWAM. The flag does nothing if Edge is already running. - Report any sign-in problems to Microsoft Support before Edge 157 ships.
Microsoft's release schedule lists Stable 157 for the week of November 5, 2026, and notes that dates are approximate. That leaves roughly two weeks to test.
Other announcements in the 156 notes
PiunikaWeb didn't cover these, but they're listed alongside 156 and matter to many organizations:
- XSLT is being deprecated. Edge will disable the XSLTProcessor JavaScript API and XML processing instructions that reference XSLT stylesheets by default. That happens in Stable with version 159, after 157 does it in Canary, Dev and Beta. The
XSLTEnabledpolicy and an origin trial can buy temporary time, but both are planned to stop working in Edge 176. As Windows Mode notes, a few older business apps and XML feeds use it, while most everyday websites don't. - Copilot URL redirect. Admins should update allow lists to include
*.cloud.microsoftbefore Microsoft 365 Copilot Chat in Edge is redirected. Tenant admins can find details under MC1462915. - Tracing changes.
edge://tracingcan no longer collect traces. You now need to use Perfetto UI.
Extended Stable and security
This release is also an Extended Stable build. Microsoft's Edge blog said that under the new schedule, Extended Stable receives updates every fourth release (for example, 156, 160, 164), still about every eight weeks. Organizations on that channel will get this whole set of changes in one go, so the policy deprecations above matter even more for them.
Microsoft's security notes say the Stable build incorporates the latest Security Updates of the Chromium project, but CVEs will be added as soon as available. As of this writing, no specific vulnerabilities have been listed, and there's no sign of a zero-day fix.
What isn't in the release notes
PiunikaWeb also said that after updating, Edge showed a slideshow summarizing the changes, including a slide about the scareware blocker. It also mentioned a redesigned Copilot side pane that is rolling out. Neither appears in Microsoft's list of 156 feature updates. The scareware blocker is an existing Edge feature, and nothing shows it's new in 156. Treat these as things one tester saw, not as confirmed parts of this release.
How to update
- Open Edge and go to Settings and more (…) → Help and feedback → About Microsoft Edge, or type
edge://settings/helpin the address bar. - Let Edge check for updates, then restart when it asks.
- The update worked if the version shows 156.0.4314.42 (or later).
If it doesn't show up yet, that's the staged rollout, and it should arrive within a few days. The managed-startup prompt is a separate staged rollout, so it may appear later even if you already have 156.
Bottom line: For home users, Edge 156 adds autofill for passports and driver's licenses, a more useful key icon for saved logins, and permission controls that look the same everywhere. For IT teams, the important items are the PDF policy and autofill policy deprecations, the startup policy, the XSLT timeline, and most urgently the switch to OneAuth sign-in in version 157. Check edge://signin-internals on your managed profiles before 157 arrives.
References
- Microsoft Edge v156 improves site permissions, adds document autofill, & login notes - PiunikaWeb PiunikaWeb · 2026-10-24T21:29:18+00:00
- Microsoft Edge release notes for Stable Channel | Microsoft Learn learn.microsoft.com
- Edge 156: New Permissions, Document Autofill and Key Icon - Windows Mode windowsmode.com