100 Days Later: Microsoft Is Still Steering Windows and Copilot Users to Edge

Microsoft continues steering Windows and Copilot users to Edge 100 days after the issue was first exposed.
This report focuses on a persistent problem: 100 days after the practice was publicly exposed, Microsoft continues to route users to Edge through Windows system components and Copilot, overriding their chosen default browser. The article examines the issue from three angles — business logic (controlling the default browser means controlling search, ad revenue, and AI entry points), platform power dynamics (Microsoft acts as both rule-setter and market player), and the regulatory landscape (the EU's DMA has prompted regional concessions, but its geographic limits mean the disparity persists globally). For users, explicitly set browser preferences can still be bypassed at certain entry points; for third-party browser makers, system-level friction remains a near-insurmountable structural barrier. With AI assistants becoming the next major traffic gateway, this battle over entry-point control shows no signs of cooling.
The Controversy Over Microsoft's Browser Steering Continues
An article titled 100 days later: Microsoft still steers Windows and Copilot users to Edge has been drawing attention on Hacker News. The core argument is straightforward: even months after the issue was publicly discussed, Microsoft continues to use system-level design to funnel Windows and Copilot users toward its own Edge browser.
This isn't a new story. For years, Microsoft has faced criticism for introducing friction around default browser settings in Windows — such as forcing Edge to open links clicked within system components, making the process of setting a different default browser unnecessarily cumbersome, or repeatedly nudging users to switch through pop-ups and prompts. The significance of "100 days" in this report is its implication that, despite public exposure and discussion, nothing has substantively changed.
The Product Logic Behind the "Steering"
Why Microsoft Does This
From a business perspective, the browser is the primary gateway to the internet. Controlling the default browser means controlling search traffic (Bing), advertising revenue, and — increasingly — the AI assistant entry point (Copilot). As Copilot becomes more deeply integrated into Windows, Edge has become the natural vessel for Microsoft's AI strategy.
When users initiate a web search through Copilot or click on a result link, the system tends to open it in Edge rather than the user's chosen default browser. While technically "convenient," this design fundamentally undermines user choice and puts third-party browsers like Chrome and Firefox at a structural disadvantage.
The Battle for System-Level Default Privileges
These practices continue to spark controversy because they touch on the power boundary between OS vendors and the broader app ecosystem. The operating system is both "referee" and "player": Microsoft sets the rules for default apps while being one of the biggest beneficiaries of those rules. When this dual role manifests at a critical gateway like the browser, questions of fairness become unavoidable.
Microsoft's aggressive behavior in browser competition is no stranger to antitrust scrutiny. In the late 1990s, Microsoft's bundling of Internet Explorer with Windows and its efforts to suppress Netscape led to a landmark antitrust lawsuit by the U.S. Department of Justice — United States v. Microsoft Corp. Courts initially ruled that Microsoft had engaged in monopolistic behavior and should be broken up; the case was ultimately settled with behavioral remedies requiring Microsoft to open system interfaces to third parties and prohibiting certain exclusionary agreements. This history provides important context for today's debate: the abuse of "gateway control" by platforms has precedent, and public exposure alone rarely drives lasting change — systemic regulatory intervention tends to be far more effective. The current controversy around Edge and Copilot is structurally similar to the IE bundling issue of that era, with AI assistants now adding even greater strategic value to gateway control.
The Regulatory and Compliance Context
Under regulatory frameworks like the EU's Digital Markets Act (DMA), "gatekeeper" platforms are required to give users more freedom in choosing default apps and are prohibited from self-preferencing. Microsoft has made some concessions in Europe — such as allowing Edge to be more thoroughly uninstalled and honoring default browser settings. But these changes are often limited to specific regions, and the experience varies significantly worldwide.
The "100 days" milestone is a reminder that public exposure and reputational pressure can generate attention, but without sustained regulatory constraints or competitive pressure, platform vendors have limited incentive to abandon established practices.
The Digital Markets Act (DMA) was formally adopted in 2022 and began applying to platforms designated as "gatekeepers" in 2023. To qualify as a gatekeeper, a company must meet certain thresholds: annual turnover in the European Economic Area exceeding €7.5 billion, or a market capitalization above €75 billion, with at least 45 million monthly active end users in at least three member states. Microsoft was added to the gatekeeper list based on Windows and Teams, among other products. One of the DMA's core prohibitions is against gatekeepers technically privileging their own services over comparable third-party services — so-called "self-preferencing." Violations can result in fines of up to 10% of global annual turnover, rising to 20% for repeat or serious infringements. It was under this pressure that Microsoft introduced a more accessible default browser switching interface in the European Economic Area in 2024 and allowed users to more thoroughly remove Edge. But this also highlights the DMA's geographic limitations — its enforcement stops at Europe's borders, and Microsoft faces no equivalent compliance obligations in other markets.
What This Means for Users and Developers
For ordinary users, this means that even if you've explicitly set a preferred browser, you may still find Edge being opened in certain contexts — particularly through system components and Copilot — effectively bypassing your settings. Completely avoiding this often requires third-party tools or manual system configuration changes.
For third-party browser vendors and developers, this kind of system-level friction creates a structural barrier that's difficult to overcome. Even a superior product can struggle to compete with a platform's built-in app when it comes to capturing default entry points.
It's worth noting that the Hacker News discussion of this report was relatively modest (7 points, 1 comment), and the article itself is largely confined to the factual observation that "the problem remains unsolved," with limited technical detail or any official response from Microsoft. For readers interested in browser competition and platform governance, it reads more like a footnote in an ongoing story than a revelatory new finding.
Conclusion
The battle over default browser status is, on the surface, a tug-of-war between Microsoft and its competitors. At a deeper level, it's a long-running question of how OS vendors balance commercial interests against user choice. As AI assistants emerge as powerful new traffic entry points, the competition over "gateway control" will only intensify. For users, understanding the logic behind these system-level design choices is the first step toward taking more active control of your own digital experience.
Related articles

Chain of Thought Isn't Just for AI: How Humans Can Use CoT to Improve Thinking Quality
Chain of Thought isn't just a prompt trick for large models. Starting from a Hacker News discussion, this article analyzes why CoT works for human thinking too, breaks down actionable ways to transfer it, and highlights the key differences between human CoT and machine CoT.
Cloudflare Teams Up with OpenAI: Closi…
Cloudflare Teams Up with OpenAI: Closing the Loop from Vulnerability Discovery to Defense with AI
Cloudflare uses OpenAI Daybreak to investigate security vulnerabilities and generate reviewable remediation plans, while developers use Codex to boost coding efficiency and quality.

Orca Multi-Agent Orchestration in Practice: A Guide to Parallel Collaboration with Claude and Codex
Orca is Stable AI's free open-source agent workbench supporting 34 agents like Claude Code and Codex in parallel. Learn its Git worktree isolation, multi-model orchestration, and mobile management.