About Computer Fix Desk

What changed, and what it changed for you

When this site began, it was just a place to dump notes from my own failed fixes—no research, no testing, just whatever I’d scribbled down after pulling my hair out over a frozen Windows update.

The guides were thin, the tone was defensive, and the only thing consistent was the frustration.

Now, every guide is built around a real problem someone actually reported. The tone is still direct, but the steps are tested, the screenshots are labeled, and the ‘solutions’ aren’t just copied from forums.

You’ll still find the same stubbornness about making tech less scary, but now it’s backed by actual work—like verifying that a ‘blue screen’ fix really works on a dual-boot Linux/Windows setup.

The one that took years

The biggest change was learning to stop writing for myself. For years, I assumed if it worked for me, it would work for anyone. That’s why the first guides were full of assumptions—like ‘just restart the router’ or ‘check the cables’—without explaining why those steps matter.

The problem wasn’t the advice; it was that I never asked what the reader actually needed.

It took a reader email to change it. Someone wrote in to say they’d followed a ‘fix your slow PC’ guide step by step, only to realize halfway through that their issue was a failing SSD, not malware. The guide had skipped the ‘check your hardware first’ part entirely.

That was the moment I realized: if I didn’t know what the reader *didn’t* know, I was writing useless notes.

Fixing it cost time. Now, every guide starts with a checklist of common misdiagnoses—like ‘Is it software, hardware, or user error?’—before diving into solutions. It’s slower to write, but it means someone with a dead USB port won’t waste three hours trying to ‘reinstall drivers’ when the cable was bent.

The trade-off? Clearer guides, fewer angry comments about ‘this didn’t work.’

Meet the author

I used to think tech problems were either stupid or impossible. If your computer froze, it was because you’d installed the wrong software—or you were just bad at it.

That attitude led to guides that blamed the user (‘did you try turning it off and on again?’) instead of explaining the actual steps. The worst part? I’d write something like that, hit publish, and move on without checking if it helped.

I also believed that if I could fix it, anyone could. That’s why the first tutorials skipped basics like ‘how to open the task manager’ or ‘what a registry key actually is.’ I assumed readers would already know—or figure it out. They didn’t.

One reader sent a screenshot of their task manager with a red circle around the ‘End Task’ button, asking why it was grayed out. I’d never noticed that wasn’t obvious.

What changed was realizing that frustration isn’t the enemy—it’s the starting point.

Now, I write like Clifford Thibodeaux, the guy who still pulls his hair out when his printer stops working, but who also knows how to explain why the toner cartridge might be the issue without making the reader feel dumb.

This site exists because I refuse to treat tech like it’s magic. If a blue screen is just a system’s last warning, then the job isn’t to debug the panic—it’s to debug the crash.

What did not change

The tone hasn’t. I still write like someone who’s just figured something out themselves—no corporate speak, no ‘best practices’ jargon. If I don’t know the answer, I’ll say so. If a fix is a guess, I’ll call it that.

The focus on actual problems hasn’t. This isn’t a site for ‘how to build a PC from scratch’ if you just need to fix a fan that won’t spin.

The weird, specific issues are still here—the ones that make you Google for hours before finding a single forum post that might help.

What is still being fixed

The biggest gap is mobile troubleshooting. Right now, most guides assume you’re using a desktop or laptop. That’s changing—we’re adding more Android and iOS fixes—but it’s slow because half the issues are device-specific.

If you’ve got a problem with your phone or tablet that isn’t covered, that’s what we’re working on next.

Want to help? The contact page is where to send screenshots of your error messages, descriptions of what *didn’t* work when you tried the guides, or even just a ‘this fix didn’t work for me’ note. Every one of those gets logged for future updates.