Dev error bricked 600 PCs, caused $1M CD-ROM write-off
First reported by The Register ·
If you bought accounting software on CD-ROM, this incident highlights a risk you previously accepted.
A software development error at a CD-ROM software vendor led to the bricking of approximately 600 customer PCs, resulting in a $1 million write-off for unsold inventory. The incident occurred when a new annual version of small business accounting software was released just before a major holiday. A decision was made to force the updating of Windows registry keys during installation to improve successful installation metrics. However, this change corrupted the registry on a significant number of machines, rendering them inoperable and causing all other software to fail. The vendor responded by offering to replace affected machines at no cost to the customer, leading to over 600 PC replacements in the week prior to the holiday. The company subsequently pulled the faulty CDs from circulation, leading to the substantial inventory write-off.
This incident underscores the critical importance of thorough testing in software development, particularly for applications that interact with core operating system components like the Windows Registry. The vendor's decision to force registry updates without fully anticipating potential side effects directly led to a catastrophic failure impacting a substantial number of users and incurring significant financial losses. It highlights a past era where physical media distribution and less sophisticated testing methodologies made such widespread failures more probable and costly to rectify.
The scenario also points to the customer-centric approach the company took in its damage control, prioritizing customer satisfaction by replacing entire PCs, a costly but perhaps necessary step to maintain brand trust. The inability of the development team to immediately reproduce the issue, even with access to a customer's machine, emphasizes the complexity of diagnosing problems in diverse user environments and the challenges of managing software rollbacks and updates in a pre-internet era.
AI-written summary. May contain errors.