User thought 'General Failure' was a hacker's name

Key Takeaways

• A VP in 2000 believed 'General Failure' was a hacker infiltrating his PC
• The cryptic Windows error actually indicated a dead hard drive
• User-hostile error messages remain a persistent problem in enterprise IT

Around the year 2000, a vice president at a retail company called his IT department in a panic. Someone named 'General Failure' was reading his C: drive. The intruder must be using a military handle to mask their identity. Except there was no intruder. The VP had misread a Windows error message, and his hard drive was simply dying.

The story comes from The Register's long-running 'On Call' column, which collects reader-submitted tech support war stories. A sysadmin pseudonymously called 'Lee' shared the tale of his time managing Novell servers and desktop support for over a thousand employees at a retail headquarters.

What the VP actually saw

The VP complained he couldn't access any files because 'someone else was using them.' Lee found this odd. He asked if the exec was seeing a standard 'file in use' dialog from Word or Excel. No, the VP replied. The message said 'General failure is reading Drive C:' and the name was obviously a hacker's alias.

Lee pressed for the exact wording. The VP re-read the dialog and corrected himself: 'General failure reading Drive C:' No 'is.' No hacker.

The message was a standard Windows error indicating a hardware failure, specifically a dead or dying disk. Windows has never been known for friendly error messages, but 'General Failure' stands out as particularly confusing for non-technical users. The phrase sounds like a name, not a diagnostic. Paired with the word 'reading,' it's easy to see how someone might imagine a person accessing their files.

Good news and bad news

Lee delivered the diagnosis. The bad news: the VP's disk was dead. The good news: no one was actually snooping around on the network. The company didn't have a 'miscreant rummaging around,' as Lee put it. A support call was arranged, and the VP got a new disk, possibly a whole new PC.

The story fits a well-worn genre of IT humor. Users searching for the 'Any Key' on their keyboard. Users believing 'Abort, Retry, Fail?' was a threat. The famous paradox of 'Keyboard not found, press F1 to continue.' These stories circulate endlessly in IT communities because they highlight a real and persistent problem: error messages written by engineers for engineers, deployed to everyone.

Why this keeps happening

Usability studies from the 1990s and 2000s found that over 70% of PC users reported confusion over technical error messages. That number has likely improved as interfaces have matured, but the underlying tension remains. Developers write error messages under time pressure, often defaulting to technical jargon or system-level terminology. Users, especially non-technical ones, interpret those messages literally.

'General Failure' is a legacy from MS-DOS, where error messages were terse by necessity. The phrase persists in various forms in Windows, though modern versions tend to present friendlier wording like 'Something went wrong' or 'Windows can't access this disk.' The improvement is incremental. Enterprise software, internal tools, and legacy systems still produce messages that read like riddles.

For IT leaders, the lesson is straightforward: error message design matters. When your users see a confusing message, they call your support team. Or worse, they assume they've been hacked and escalate to management. Either way, someone's Friday afternoon gets derailed.

The broader pattern

Lee's story resonated because it captures a moment of collision between two mental models. The VP thought in terms of people and threats. The system spoke in technical categories. Neither was wrong, but they weren't speaking the same language.

This gap persists in enterprise IT. Users misinterpret security warnings, ignore legitimate alerts because they've seen too many false alarms, or escalate non-issues because the wording sounds severe. The solution isn't to dumb everything down. It's to write messages that accurately convey both the problem and the appropriate response.

As The Register's column shows, the best IT support stories often come down to communication failures. The technology works or fails in predictable ways. The humans, less so.

Frequently Asked Questions

What does 'General Failure reading Drive C:' mean?

It's a Windows error indicating the system cannot read from the specified drive, usually due to hardware failure, a corrupted disk, or a disconnected device. It does not refer to a person or hacker.

Why do Windows error messages use confusing names like 'General Failure'?

The term dates back to MS-DOS, when screen space was limited and messages were written for technical audiences. 'General' indicates a non-specific failure type, but it reads like a military rank to non-technical users.

How can IT teams reduce user confusion over error messages?

Rewrite error messages in plain language that explains what happened, what it means, and what the user should do next. Include contact information for support when appropriate.

What was Novell NetWare?

Novell NetWare was a network operating system that dominated enterprise networking in the late 1980s and early 1990s, reaching over 90% market share before losing ground to Windows Server.

Source: www.theregister.com