Operating Systems
IBM OS/2
IBM and Microsoft jointly built OS/2 in the late 1980s to replace MS-DOS, but the partnership fractured as Windows 3.0 took off in 1990, and Microsoft walked away to build Windows on its own. IBM kept developing OS/2 alone through 2.0 in 1992 and the Warp line in 1994-1996, producing an operating system widely regarded as more technically capable than contemporary Windows. It never won meaningful market share, held back by IBM's pricing, weak third-party driver and application support, and a sales operation that could not match Microsoft's OEM relationships. IBM discontinued OS/2 sales in 2005 and ended support in 2006.
- Company
- IBM
- Started
- 1985
- Ended
- 2006
- Price of OS/2 2.0 at launch versus Windows 3.1
- $195 vs $150
- Collapse speed
- Gradual
- Preventability
- Medium
- Lesson transfer
- Industry-wide
- Last reviewed
- 2026-08-17
Narrative
The story
The ambition
In August 1985, IBM and Microsoft signed a Joint Development Agreement to build the successor to MS-DOS. The two companies had made each other rich through DOS, and both wanted the next operating system, an advanced 32-bit, protected-mode platform that could multitask properly and outgrow DOS's limits, to be theirs. IBM brought its enterprise credibility and its PS/2 hardware line; Microsoft brought the engineers who had built DOS. OS/2 1.0 shipped in December 1987, followed by OS/2 1.1 in October 1988 with the Presentation Manager graphical interface, and OS/2 1.2 in October 1989 with a new file system. The plan was that OS/2 would become the standard operating system of the PC industry, with IBM and Microsoft as its joint stewards.
The rise
Windows 3.0, released by Microsoft in May 1990, sold millions of copies within its first year, a scale of consumer success that OS/2 had never approached. That success reshaped Microsoft's priorities. Microsoft wanted an open hardware architecture that ran on any cheap PC clone; IBM wanted OS/2 to help sell IBM hardware. The companies also disagreed over API design and feature direction, and cultural friction between IBM's bureaucratic process and Microsoft's faster development style compounded the strategic split. By 1991, Microsoft was committing its energy to Windows and Windows NT rather than to joint OS/2 work, and the partnership effectively dissolved by 1992, leaving IBM to develop OS/2 on its own.
The cracks
IBM pressed ahead alone. OS/2 2.0 shipped in April 1992 as IBM's first fully independent release, the first 32-bit version of OS/2, with a new object-oriented interface called the Workplace Shell. IBM marketed it as "a better DOS than DOS and a better Windows than Windows," and it could run DOS and Windows applications alongside native OS/2 software. It launched at $195, against $150 for Windows 3.1. That gap mattered, because Windows came pre-installed on most new PCs while OS/2 had to be bought separately, and OS/2's reliance on Microsoft-controlled code in parts of the system meant IBM had to keep shipping Windows components inside OS/2 itself, undercutting its own price position. Hardware vendors, wary of investing in drivers for a platform with a small installed base, left OS/2 users with a narrower choice of supported printers, video cards, and other peripherals than Windows users had.
The collapse
IBM answered with OS/2 Warp 3 in October 1994, backed by a large advertising push aimed at consumers, and OS/2 Warp 4 in September 1996, which added Java support and speech recognition and became the last major release. Computer press and IBM's own technical staff continued to regard OS/2 as more capable than Windows: it multitasked more reliably and protected memory more effectively than Windows 3.1, and reviewers judged it competitive with or ahead of Windows 95 on stability. None of that converted into market share. IBM's sales organization could not match Microsoft's reach into PC manufacturers, who kept building Windows into new machines by default, and the developer ecosystem stayed thin because most software vendors wrote for the platform their customers already had, which was Windows. Windows 95, launched in August 1995 with the mass marketing and OEM bundling that OS/2 had never matched, cemented that gap. IBM scaled back the OS/2 team and confirmed Warp 4 would be its final major release.
The aftermath
IBM continued to sell and support OS/2 at a shrinking scale for another decade, with the final version, 4.52, released in December 2001. IBM discontinued OS/2 sales in December 2005 and ended all support at the close of 2006, formally closing out a platform it had first set out to build with Microsoft twenty-one years earlier. OS/2 did not disappear entirely: its reliability made it a fixture in specialized, unglamorous deployments such as bank ATMs and transit-system infrastructure, and outside vendors, first Serenity Systems with eComStation and later Arca Noae with ArcaOS, kept OS/2-derived systems alive commercially for years after IBM stepped away. But as a contender for the general-purpose PC desktop, OS/2 was over well before IBM's formal exit.
The lessons
OS/2 is a case where the better engineering did not win, and the reasons are almost all outside the code. IBM lost the operating-system platform war chiefly because it lost the distribution war: Windows shipped pre-installed on the PCs people were already buying, and OS/2 had to be sought out and paid for separately, a gap Windows 95's marketing and OEM bundling widened further. A thin driver and application ecosystem, itself a consequence of OS/2's small installed base, then reinforced the disadvantage in both directions, since fewer users meant less vendor incentive, which meant fewer users still. IBM's own pricing and its need to keep shipping Microsoft-controlled code inside OS/2 added friction on top of that. The deeper lesson is about platform economics rather than product quality: on operating systems, where value depends on drivers and applications built by outside parties, a network effect favoring the incumbent can beat a technically superior challenger even over a decade of continued investment.
Causal timeline
Failure Anatomy
- 1987-12
Joint Development Agreement
IBM and Microsoft sign an agreement to build OS/2 as the successor to MS-DOS; OS/2 1.0 ships in December 1987, followed by 1.1 (Presentation Manager, 1988) and 1.2 (new file system, 1989). [1]
- 1990
Windows 3.0 breaks the partnership
Windows 3.0's explosive 1990 success redirects Microsoft's priorities toward Windows and Windows NT; disagreements over hardware openness and API direction end the joint OS/2 effort by around 1992. [2]
Internal conflictStronger competitor - 1992-04
- 1995-08
- 2006-12
Wind-down and exit
IBM ships OS/2's final version, 4.52, in December 2001, discontinues sales in December 2005, and ends all support at the close of 2006. [9]
Structured analysis
What Went Wrong
Root causes
Losing the distribution war to Windows. Windows shipped pre-installed on most new PCs by default, while OS/2 had to be bought separately, and Microsoft's OEM relationships and marketing reach, sharpened further by the Windows 95 launch, outmatched IBM's sales organization. [4] [7]
A thin driver and application ecosystem. Hardware vendors and software developers built for the platform with the larger installed base, which was Windows, leaving OS/2 with fewer supported peripherals and fewer native applications, a gap that reinforced itself over time. [5] [6]
Contributing factors
The IBM-Microsoft partnership breaking apart. After Windows 3.0's 1990 success, Microsoft redirected its priorities toward Windows and Windows NT, and disagreements over hardware openness, API design, and development pace ended the joint OS/2 effort by around 1992, leaving IBM to build the platform alone. [2]
Pricing that undercut its own value proposition. OS/2 2.0 launched at $195 against $150 for Windows 3.1, and because OS/2 still relied on Microsoft-controlled code in parts of the system, IBM had to keep shipping Windows components inside its own product. [3]
Immediate trigger
Windows 95's launch cements the gap. Windows 95's August 1995 release, backed by mass consumer marketing and default OEM bundling that OS/2 had never matched, confirmed Windows as the PC standard and left IBM's OS/2 team without a path to meaningful desktop share. [7]
Visible symptoms
Technical praise without market share. OS/2 Warp was widely judged by the computer press and IBM's own engineers to be more stable and reliable than contemporary Windows, yet that reputation never translated into a meaningful share of the PC operating-system market. [8]
Warning signs
Hardware vendors declining to write OS/2 drivers. Because OS/2's installed base stayed small relative to Windows, peripheral makers were reluctant to invest in supporting it, leaving OS/2 users with a narrower range of supported hardware than Windows users had. [5]
Affected groups
Contested
Disputed points
Interpretations where credible accounts genuinely differ, presented as disputes, not settled facts.
Sources agree OS/2 was widely regarded as technically superior to contemporary Windows in stability and multitasking, but disagree on how much that mattered; The Register frames the loss almost entirely as a sales and licensing failure, while other accounts give more weight to the driver and application ecosystem gap as an independent cause rather than purely a symptom of poor distribution. [5] [8]
UnresolvedKeep reading
Related failures
Evidence
Claims & sources
Every numbered marker in the analysis links to the claim it rests on, and each claim to its sources.
- [1]
IBM and Microsoft signed a Joint Development Agreement in August 1985 to build OS/2 as the successor to MS-DOS, with OS/2 1.0 shipping in December 1987, 1.1 (with the Presentation Manager interface) in October 1988, and 1.2 in October 1989.
- [2]
Windows 3.0's explosive success after its 1990 release redirected Microsoft's priorities toward Windows and Windows NT, and disagreements between the companies ended the joint OS/2 development effort by around 1992, leaving IBM to develop OS/2 alone.
Moderate Reported explanation OS/2 What Was IBM's OS/2, and Why Did It Lose to Windows? 25 years of IBM's OS/2 - [3]
OS/2 2.0 launched in April 1992 at $195, against $150 for Windows 3.1, and because parts of OS/2 still relied on Microsoft-controlled code, IBM had to keep shipping Windows components inside its own product, which undercut its price position.
- [4]
Windows shipped pre-installed on most new PCs by default, while OS/2 had to be sought out and bought separately, giving Windows a decisive distribution advantage that IBM's own sales organization could not close.
Moderate Reported explanation What Was IBM's OS/2, and Why Did It Lose to Windows? So farewell then, OS/2 - [5]
Because OS/2's installed base stayed small relative to Windows, hardware vendors were reluctant to invest in writing OS/2 drivers, leaving OS/2 users with a narrower range of supported peripherals than Windows users had.
- [6]
OS/2's thin third-party application support and its small installed base reinforced each other, since software vendors built primarily for the platform their customers already used, which was Windows.
- [7]
Windows 95's August 1995 launch, backed by mass consumer marketing and default OEM bundling that OS/2 never matched, cemented Windows as the PC standard, and IBM subsequently scaled back the OS/2 team and confirmed Warp 4 as its final major release.
- [8]
Computer press reviewers and IBM's own technical staff generally regarded OS/2 Warp as more stable and technically capable than contemporary versions of Windows, including Windows 95, despite its lack of market share.
Moderate Reported explanation What Was IBM's OS/2, and Why Did It Lose to Windows? So farewell then, OS/2 25 years of IBM's OS/2 - [9]
IBM released OS/2's final version, 4.52, in December 2001, discontinued OS/2 sales in December 2005, and ended all support at the close of 2006.