Scan a website for consumer and competition risks, report a problem, and search live cases. Not a law firm.

CounterLayer
← Case library

US · remedy · ~8 min read

United States v. Microsoft Corp.

1998–2002 · PC operating systems, web browsers

The US government said Microsoft used its control of Windows to crush browser competition—especially Netscape—by bundling Internet Explorer and pressuring PC makers. Courts agreed Microsoft broke competition rules in important ways. The company was not broken up, but it had to change how it treated partners and rivals for years.

The story

In the 1990s, Windows sat on nearly every personal computer that mattered. If you built software, you usually needed Windows to reach customers. That kind of gatekeeping power is exactly what antitrust law watches closely.

Netscape’s browser was popular and threatened to become a new layer people used on top of Windows. Microsoft responded by pouring resources into Internet Explorer and making it hard for PC makers and users to choose something else.

Prosecutors argued this was not ordinary hard competition. They said Microsoft used monopoly power in operating systems to win a different market—browsers—and to protect Windows itself from future threats.

The case became one of the most famous tech antitrust fights in US history: courtroom demos, emails, and a public debate about whether government should rein in a software giant.

Why it matters

If one company controls the platform everyone uses, it can decide which apps thrive and which die—even when customers might prefer a rival.

This case is the ancestor of today’s fights about app stores, default search engines, and “self-preferencing.” When you hear those debates, Microsoft is often the historical reference point.

For small developers and startups, the lesson is simple: platform rules are not just product design. They can be competition issues when the platform is unavoidable.

What was claimed

Microsoft had monopoly power in PC operating systems.

It illegally maintained that monopoly by excluding browser rivals and locking in PC makers with restrictive deals.

Bundling Internet Explorer with Windows was part of a strategy to harm competition, not just a helpful feature.

The other side

Microsoft argued it was innovating and giving consumers a free browser.

It said integrating software is normal, and that antitrust law should not freeze product design.

It also argued rivals were not as locked out as prosecutors claimed.

What it means for you

You do not need to be a lawyer to spot the pattern: a must-have platform + pressure to use the platform owner’s add-on + punishment for using rivals.

Remedies focused on behavior (how Microsoft dealt with others), not permanently splitting Windows from Office or browsers.

Later tech cases often ask: is this the Microsoft playbook again, or something different?

Bottom line

A dominant platform company can get in trouble when it uses that dominance to shut rivals out of neighboring markets. Microsoft changed practices under court oversight; it was not dismantled.

Timeline

  1. 1990s

    Windows becomes the default PC platform

    Most home and office PCs shipped with Windows. That made Windows the doorway almost every software company had to pass through.

  2. May 18, 1998

    US government sues

    The Department of Justice and several states accused Microsoft of illegally protecting its Windows monopoly, especially around Internet Explorer.

  3. 2000–2001

    Trial, liability, then appeal

    A trial court found serious violations and even considered breaking up Microsoft. An appeals court kept key liability findings but rejected the breakup plan as ordered.

  4. 2001–2002

    Settlement and monitoring

    Microsoft agreed to rules about how it dealt with PC makers and rivals, with years of oversight instead of a corporate split.

Key dates

Complaint filed
May 18, 1998
District court findings
April 3, 2000
Appeals court decision
June 28, 2001
Settlement approved
November 1, 2002

Formal snapshot

Summary: DOJ alleged Microsoft maintained an OS monopoly by integrating Internet Explorer and restricting OEMs and rivals.

Regulator / plaintiff argument: Exclusionary agreements and technological tying raised rivals’ costs and protected the Windows monopoly.

Outcome: Liability findings; settlement/consent decree with behavioral remedies (API disclosure, OEM flexibility).

Remedies: Behavioral restrictions; monitoring; no full breakup after appeal path.

Conduct tags

tyingexclusivityabuse of dominance

Laws referenced

  • Sherman Act §1 — 15 U.S.C. §1
  • Sherman Act §2 — 15 U.S.C. §2

Companies

Sources

Reader signals

0 reads · synced via local demo storage — add NEXT_PUBLIC_SUPABASE_* to enable shared likes and comments

Comments

    No comments yet — start the thread.