Microsoft's Stable release notes list build 158.0.4370.33, dated November 19, 2026, as the main Edge 158 release. The scam-notification protection is in that build's feature list. This isn't the first time the feature has appeared in Microsoft's notes, though, and the backstory affects what you should expect on your own PC.
What the feature actually does
Microsoft describes a narrow, specific trigger. Neowin, reading the changelog, reported that Edge will now watch for any notifications that provide links to any website that Microsoft Defender SmartScreen blocks as a scam, phishing, or malware. The browser will then automatically stop that source from sending any other notifications and inform the user about what happened.
The steps are simple:
- A site you once allowed to send notifications pushes an alert.
- You click it, and it takes you to a page.
- SmartScreen classifies that page as a scam, phishing or malware site and blocks it.
- Edge removes the sending site's notification permission and tells you it did so.
Other outlets fill in some details. Windows Mode, citing the Microsoft Edge Blog and the Stable release notes, says when Microsoft Defender SmartScreen or Scareware blocker detects a scam that was pushed through a notification, Edge disables notifications from the site that sent it. The same report says the next time Edge starts, a bar explains that notifications from a suspicious site were blocked in your last session. Cryptika describes the same detection chain, including Scareware blocker. The formal release-note wording only names SmartScreen, so treat the Scareware blocker link as reported by those outlets rather than written into the changelog.
What it doesn't do: Microsoft doesn't claim Edge scans every notification, catches every scam, or blocks every bad notification source. Protection starts only after a notification lands you on a page SmartScreen already blocks. The first scam notification can still arrive. The feature stops the second, third and fiftieth.
Section summary: Edge now revokes notification permission from sites whose notifications lead to SmartScreen-blocked pages, and tells you when it happens. It shuts off repeat abuse. It doesn't screen notifications before they arrive.
"New in 158"? Not quite
This is the part a quick changelog skim misses. The feature isn't brand new in version 158. Third-party trackers that mirror Microsoft's notes list it under Version 152.0.4191.53: August 27, 2026 (Stable), and gHacks covered it at the time. gHacks also warned that several features in that release, including the option to unsubscribe from scam notifications, and the improved key icon, involve controlled feature rollouts and therefore may not show up on every device at once.
Microsoft's roadmap entry for the feature, RM568366, still lists its status as In development, with a rollout start of November 2026 (its release phase is General Availability).
The Edge 158 timeline looks like this:
| Milestone | What Microsoft's notes show |
|---|---|
| Edge 152 Stable (Aug 27, 2026) | Feature first listed, as a controlled rollout |
| Microsoft 365 roadmap RM568366 | In development; rollout start November 2026 |
| Edge 158 Beta (158.0.4370.1, Nov 4, 2026) | Listed again, with no controlled-rollout note |
| Edge 158 Stable (158.0.4370.33, Nov 19, 2026) | Listed in Feature Updates, with no controlled-rollout note in the entry |
What does that mean in practice? The 158 entries drop the "check back as we continue the rollout" line that the 152 listing carried. That points toward broad availability, but it's an inference, not a promise from Microsoft. The update itself also arrives gradually. Microsoft's release schedule says Stable dates mark the beginning of a progressive rollout, so some devices get the new version days after others. If you don't see the behavior yet, your PC may simply not have 158.
Section summary: The protection has been rolling out since Edge 152. Version 158 is where it appears in the Stable notes without the controlled-rollout caveat. The Edge 158 build itself still reaches devices over several days.
How to check, and undo, a block
Microsoft gives a direct settings path. Paste this into the Edge address bar:
edge://settings/privacy/sitePermissions/allPermissions/notifications
That page shows which sites can and can't send you notifications. Edge's automatic blocks show up there, and you can restore permission for any of them. Cryptika notes users can restore notifications if they believe the browser made an incorrect decision.
Before you click restore, think about why the site is on the list. SmartScreen flagged a page that site's notification sent you to. Unless you're sure it was a false positive, such as a legitimate site whose link was briefly misclassified, leave it blocked. Restoring the permission doesn't clear the site's reputation. It just opens the door again.
To check which Edge version you're running, go to edge://settings/help. That page also checks for and installs updates.
Why notification abuse deserves its own fix
Push-notification scams are cheap and effective. A site gets one "Allow" click, often through a fake CAPTCHA or a "click Allow to continue" prompt. After that, it can send alerts that look like they come from Windows itself: fake infection warnings, fake prize claims, fake tech support numbers. Blocking the scam page alone treats the symptom. The notification permission stays, so the next alert arrives tomorrow. (That's general industry context, not a Microsoft claim.)
Windows Mode sums up the reasoning: Blocking the notification sender, not only the scam page, was the logical next step. Cryptika reports that Microsoft also collects user reports about notification prompts, which can include the URL and a screenshot of the page that tried to persuade the visitor to enable notifications.
A fair objection: the whole thing depends on SmartScreen's verdict. A brand-new scam domain that SmartScreen hasn't classified yet won't trigger anything. Users who switch SmartScreen off lose the benefit too, by design. As a backstop, the feature is good. As a replacement for not clicking "Allow" on random sites, it isn't.
Also in Edge 158: Google data import from Settings
The Stable notes include a convenience change for people coming over from Google's ecosystem. Edge now lets you import Google account data, including passwords, bookmarks, history and autofill data, from Settings at any time after setup. Before this, Google account import only happened during first-run setup. Microsoft also merged Google Chrome import and Google account import into a single entry point in Settings.
Microsoft lists this as available for Windows devices, so macOS and Linux users shouldn't count on it yet. The Beta notes marked it as a controlled rollout, so it may not show up for everyone right away.
Admin corner: Edge 158 policy changes
Microsoft's Stable 158 notes confirm the policy changes:
New policies
ComponentUpdatesMode: configure component updatesCopilotBrowserUseAllowList: allow Copilot browser use on specified URLsCopilotBrowserUseBlockList: block Copilot browser use on specified URLs
Deprecated policies
EdgeSafeHostingExtensionEnabledPerformanceDetectorEnabled. Microsoft says the feature is being retired, with the policy expected to become obsolete in Edge 164.EdgeWalletCheckoutEnabled. Express checkout has been retired and is off by default.
Obsolete policies
BrowsingWithCopilotAllowListBrowsingWithCopilotBlockList
Other changes
CloudManagementEnrollmentTokennow supports macOS.
The Copilot changes need attention. If your organization used the old BrowsingWithCopilot allow and block lists, those policies are now obsolete. Move to the new CopilotBrowserUse pair, or the URL restrictions you set may quietly stop applying.
The same release notes include two deadlines admins should plan for:
- Workspaces V1 is disabled by default in Edge 158 and removed entirely in Edge 159.
- Browser-native XSLT will be off by default in Stable starting with Edge 159. The
XSLTEnabledpolicy can temporarily keep it on. Microsoft plans for that workaround to stop working in Edge 176.
With Edge now shipping major versions every two weeks, version 159 isn't far off.
The bottom line
Edge 158 doesn't introduce scam-notification protection. It finishes rolling it out. If a site you once allowed sends a notification that leads to a SmartScreen-blocked page, Edge revokes that site's notification permission and tells you. It's a narrow fix for a common problem, and it depends entirely on SmartScreen knowing the page is bad. Keep SmartScreen on, check your notification list now and then, and the next time a site asks you to "click Allow to prove you're human," don't click it.
Correction (November 20, 2026): The timeline misstated two details. The Microsoft 365 roadmap entry RM568366 lists the feature as In development with a rollout start of November 2026, not General Availability in October 2026. And the Edge 158 Beta (158.0.4370.1) listing of the feature carries no controlled-feature-rollout note; the note was already gone by the Beta listing, not dropped only in the Stable 158 notes.
References
- Microsoft Edge 158 helps protect you from scam website notifications Neowin · 2026-11-20T03:48:01+00:00
- Microsoft Edge Now Automatically Blocks Malicious Websites Sending Fake Virus Alert Notifications cryptika.com
- Microsoft Edge Update Adds Apple Sign-In and Scam Protection While Retiring Edge Drop and Video Translation - gHacks Tech News ghacks.net