Microsoft Edge users are reporting that the browser is disabling installed extensions, including popular ad blockers like uBlock Origin, without user permission. This appears to be related to a controlled rollout of a new mandatory extension called "Extensions Notifications" which seems to conflict with existing extensions, causing them to be automatically turned off. The issue is not affecting all users, suggesting it's an A/B test or staged rollout by Microsoft. While the exact purpose of the new extension is unclear, it might be intended to improve extension management or notify users about potentially malicious add-ons.
Recent reports indicate that Microsoft has commenced disabling certain browser extensions, notably including the popular ad-blocking utility uBlock Origin, within its Edge web browser. This action appears to be affecting a subset of Edge users seemingly at random, with no discernible pattern based on user configuration, specific extension versions, or Edge build numbers. The deactivation manifests as the extensions unexpectedly switching to an "off" state, effectively ceasing their functionality. Users encountering this issue have reported that manually re-enabling the extensions provides a temporary solution; however, the extensions are observed to be disabled again, often after a system reboot or simply after a period of time.
While Microsoft has not issued an official statement addressing this specific behavior, the prevailing speculation attributes it to a potential bug within a recent Edge update. This hypothesis arises from the seemingly sporadic and involuntary nature of the disablements, suggesting an unintended consequence rather than a deliberate policy change. Affected users have expressed frustration with the disruption to their browsing experience, particularly those who rely on extensions like uBlock Origin for ad blocking and privacy protection. The lack of clear communication from Microsoft regarding the root cause and the absence of a consistent solution further exacerbate user concerns. Currently, the only reported workaround involves manually reactivating the affected extensions each time they are disabled, a process that is both inconvenient and temporary. This ongoing issue underscores the challenges users face with automatic software updates and the potential for unintended consequences to disrupt established workflows and personalized browser configurations. The situation remains fluid, awaiting further investigation and official acknowledgement from Microsoft.
Summary of Comments ( 254 )
https://news.ycombinator.com/item?id=43201974
HN users largely express skepticism and concern over Microsoft disabling extensions in Edge. Several doubt the claim that it's unintentional, citing Microsoft's history of pushing its own products and services. Some suggest it's a bug related to sync or profile management, while others propose it's a deliberate attempt to steer users towards Microsoft's built-in tracking prevention or Edge's own ad platform. The potential for this behavior to erode user trust and push people towards other browsers is a recurring theme. Many commenters share personal anecdotes of Edge's aggressive defaults and unwanted behaviors, further fueling the suspicion around this incident. A few users provide technical insights, suggesting possible mechanisms behind the disabling, like manifest mismatches or corrupted profiles, and offering troubleshooting advice.
The Hacker News comments section for the submitted NeoWin article, "Microsoft begins turning off uBlock Origin and other extensions in Edge," contains a robust discussion with varied perspectives on the issue. Several users express concern and skepticism about Microsoft's motivations, suggesting this move is an attempt to bolster their own advertising revenue or exert more control over the user experience. Some commenters point to the increasing trend of browsers limiting extension functionality and worry about the future of ad blocking and privacy-focused extensions. The potential for abuse and unintended consequences of disabling extensions without explicit user consent is a recurring theme.
Several users share personal anecdotes of extensions being disabled without their knowledge, echoing the article's claims. They discuss the inconvenience and frustration this causes, especially for users who rely on these extensions for accessibility, productivity, or security. There's also speculation about the technical reasons behind the disabling, with some suggesting it may be related to profile syncing issues or conflicts between different versions of Edge.
A counter-narrative emerges from some commenters who argue that the issue might be a bug rather than a deliberate action by Microsoft. They highlight the lack of official confirmation from Microsoft and suggest waiting for further clarification before jumping to conclusions. Some users also point out that extensions being disabled could be a security measure to protect users from malicious or compromised extensions. There's a discussion about the responsibility of extension developers to adhere to browser guidelines and ensure compatibility.
Several commenters delve into technical details, discussing the mechanisms by which Edge manages extensions and the potential points of failure. They speculate about the role of Edge's internal update process and the possibility of corrupted extension data. Some users propose workarounds and troubleshooting steps for those experiencing the issue, such as reinstalling extensions, clearing browser data, or creating a new profile.
Finally, a few comments touch on the broader implications of the issue for the future of the web and the balance of power between browser vendors and extension developers. The discussion highlights the tension between user choice and platform control, and the importance of open standards and transparency in the development of web technologies. Some users express a desire for more robust mechanisms for users to control their browsing experience and protect their privacy.