Registry hack bricks 600 PCs and forces $1M CD-ROM write-off
Nov 9, 2026, 8:01 AM UTC
•Marta Kowalska
•3min read
A former engineer at a small business accounting software vendor forced registry changes to boost installation rates, and the update broke hundreds of customer PCs. The company replaced the machines and pulled the CDs from stores, writing off about $1 million in discs and packaging.
A reader known as Oriel once worked for a vendor of small business accounting software, back when the company shipped its products on CD-ROMs that customers bought in shops. His team’s mistake bricked more than 600 customer PCs and ended with about $1 million in discs and packaging going into the bin.
The vendor released a new version every year and timed each release to arrive before a major holiday. The year before Oriel’s story, the installer failed on some PCs running Windows 95 and Windows ME because of registry corruption. The team wanted better installation numbers the next year, so it chose to force the software to update registry keys before installing.
“We wanted to increase our successful installation metrics, so in conjunction with the installation team, a key decision was made – by me – to force the updating of registry keys to enable the install,” Oriel wrote.
The approach worked for the installer. It did not work for the rest of the machine. Support lines soon filled with calls from customers whose other software had stopped working after they installed the accounting package. “Installing a new version of our application had borked the customer’s machine completely,” Oriel wrote.
The company chose a blunt response. It told affected customers to buy a new PC and promised to cover the cost. “In the week prior to the holiday, we replaced over 600 machines,” Oriel said.
Chasing a reproduction
Developers could not reproduce the fault, so they could not see what the installer had changed. Their plan needed a machine with a Windows registry restore point created before the install. They could roll that machine back, confirm it worked, then install the software and watch what broke.
Support agents searched for customers willing to hand over their PCs. Few customers had ever created a restore point, so the search stalled. The day before the holiday, one customer offered a machine.
The customer lived a few hours’ drive away. An engineer drove there on the morning of the holiday, swapped the broken PC for a new one, and set it up to the customer’s specifications. The job took so long that the customer invited him to stay for the holiday meal. He then drove back to headquarters with the damaged machine.
The cost of the fix
The next day, the team reproduced the fault, found the cause, and built a version of the application that left other software alone. Oriel then attended a meeting with senior executives. They decided to pull the faulty CDs from stores. That decision wrote off roughly $1 million in discs and packaging.
The lesson is plain. A change that makes one installer succeed can break the system around it. Test the change on machines with the configurations customers actually run, and build a rollback path before release. The team in this story had to learn both lessons at the cost of 600 PCs and a seven-figure write-off.
Readers who have made similar mistakes can share their stories through the reader-contributed column that runs this kind of account.
imon Sharwood, theregister, Nov 9, 2026
