Serious Discussion Microsoft Edge Stable (Chromium) Now Available for Download

I think it just means that they have removed the option that enabled strict tracking protection only for the private mode. Now whatever you use as the default, Standard/Strict is the default for both Normal and Private mode.
I have eliminated Edge so I cannot check; I thought they removed the third option of strict blocking and it is either on (the moderate) or off.
 
  • Like
Reactions: Sampei.Nihira
Edge has an interesting feature that I really miss, one that doesn’t exist in Chrome.
The ability to remove search engines that the browser adds automatically.

It bothers me that, in Chrome, I have a long list of search engines I’ll never use and am forced to delete every now and then.
In Edge, this can be done using the “ManagedSearchEngines” policy.

There is no corresponding policy in Chrome.
 
After recently deleting the list of added search engines, I’m testing three rules in uBlock Origin/AG, but they can also be added to uBlock Origin Lite.

I don’t think they match the 100% performance of Edge’s policy.

If any forum members want to try these three rules especially since they’ll likely browse much more than I do and will therefore find any bypass I can post them in the thread for the ad blocker they use.

Thanks.
 
  • Like
Reactions: simmerskool
My Microsoft Edge updated to version 146.0.3856.62
Edge getting a Sunday update seems weird, it probably fixes something important maybe a security issue?

8hOzqgz.jpeg
 
Last edited:
My Microsoft Edge updated to version 146.0.3856.62
Edge getting a Sunday update seems weird, it probably fixes something important maybe a security issue?

8hOzqgz.jpeg
All Chromium-based browsers are receiving updates today because the Chrome browser received a new security fix yesterday.
 
Microsoft has released Edge version 146, and instead of adding major features, the update is focused on removing and changing existing ones, some controversial, others surprisingly welcome.

Also in the article:
  • Collections Is Being Retired in Microsoft Edge
  • Edge Is Deprecating Custom Primary Passwords
  • Workspaces Are Moving to Edge Sync
  • macOS 12 Support Is Ending After Edge 150
  • Edge 146 Stops Clearing Saved Passwords with Browsing Data
 
Also in the article:
  • Collections Is Being Retired in Microsoft Edge
  • Edge Is Deprecating Custom Primary Passwords
  • Workspaces Are Moving to Edge Sync
  • macOS 12 Support Is Ending After Edge 150
  • Edge 146 Stops Clearing Saved Passwords with Browsing Data
This looks like a “cleanup and policy” release more than a feature release.

What stands out

  • Retiring Collections is probably the biggest user-facing change. That feature never seemed as central as bookmarks, tab groups, or syncing, so Microsoft may be removing something with relatively low usage. For people who relied on it, though, this is still disruptive.
  • Deprecating custom primary passwords is more sensitive. In general, removing an extra local protection layer can be unpopular, especially for users who preferred browser-level separation from the OS account. Whether this is a good change depends on what Microsoft is using instead and how clearly they explain the security model.
  • Workspaces moving to Edge Sync sounds like Microsoft is consolidating features under its sync infrastructure. That can improve consistency across devices, but it may also raise privacy or account-dependence concerns for some users.
  • Ending macOS 12 support after Edge 150 is not surprising. Browser vendors regularly drop older operating systems once they become harder to support securely.
  • Stopping saved passwords from being cleared with browsing data will likely be welcomed by many users, because accidental password deletion is a real annoyance. At the same time, users need to understand exactly what “clear browsing data” will and will not remove.

Security angle

The password-related changes are the most important here.

  • If Edge is removing a custom primary password feature, users who depended on it should review whether their Microsoft account, OS sign-in, and device encryption are strong enough for their threat model.
  • If saved passwords are no longer cleared with browsing data, that reduces accidental loss, but it also means users who want to fully wipe stored credentials may need to do that separately and deliberately.

Practical takeaway

For most users, the impact will probably be small unless they actively use Collections or specific password features.

For security-conscious users, it would be worth checking Microsoft’s official Edge release notes or policy documentation before updating workflows around password handling or synced workspaces.

Conclusion

Edge 146 seems less about innovation and more about simplifying the browser, reducing legacy options, and pushing users toward Microsoft’s preferred account and sync model. Some of that is practical, but some changes will understandably be seen as a loss of user control.
 
Good contribution, thanks for sharing the update. The removal of Collections may inconvenience those who used it, but the fix in handling saved passwords is an important improvement. Still, it’s worth remembering that passwords for critical services such as banking or corporate email should not be stored in the browser. Maintaining solid security habits remains the best defense. 🔒🛡️
 
I recall that some forum members have stated that they take a backup for their browser's saved passwords because they occasionally delete them by accident when they want to routinely clean the browser's data.
A wise move; I do not use its password manager, but I keep a backup of my favorites for the same reason.
 
Last edited: