Recently, I got a new laptop. Getting a new laptop is always exciting. This one came pre-installed with Windows, so I decided to give it a shot, despite my long history with Linux. Spoiler alert: it didn’t work out.

Windows feels like a toxic ex: an embarrassing mistake I keep trying to make work. While Linux is the stable, loving partner I always crawl back to, especially when my needs—CTFs, bug hunting, exploring networks—lean so heavily on its strengths.

Here’s how it played out.

Trying Windows: A Rocky Reunion

At first, Windows had some things going for it.

• Proprietary Hardware That Just Works
  Windows Hello and fingerprint authentication were nice to have. Convenient but not as responsive as my iPhone’s face ID.
• WSL (Windows Subsystem for Linux)
  WSL has come a long way—running tools like nmap natively was a pleasant surprise. I remember the lack of nmap support was frustrating for me in previous versions. I used to have it installed natively in Windows and would bounce between WSL and cmd to use it…bleh…
• Co-Pilot Integration
  Co-Pilot’s hot-key accessibility was an interesting plus, and I enjoyed the convenience. More of a novelty, though.
• Rediscovering Microsoft Edge
  As a longtime Firefox user, I wasn’t expecting much, but Edge surprised me. It was lightweight and fast, and it let me pin panels—perfect for keeping frequently used sites accessible across different tabs. It’s come a long way from being the meme-browser it once was.

For a moment, it seemed like Windows might stick. But then…

Why I Couldn’t Stick With Windows

1. WSL’s Hardware & Network Abstractions
   While WSL works great for some tasks, it’s useless when you need direct access to hardware or networks. For tasks such as wireless recon, that’s a deal-breaker. The abstraction layered over network devices felt limiting, and switching between WSL, PowerShell, and cmd was frustrating.
2. Co-Pilot’s Novelty Wore Off
   Initially helpful, Co-Pilot quickly became annoying. Its overly whimsical responses—like calling me a “young wizard” when I asked about /etc/hosts equivalents—drove me back to ChatGPT’s web app. Just be straight with me. I don’t need a cringe RPG-like response…
3. OneDrive’s Obsession With Control
   OneDrive insisted on syncing everything, including my desktop. After accidentally installing Tor to the desktop and moving the location, the app kept reappearing there. No thanks.
4. Lenovo’s Unwanted Baggage
   My laptop came with Lenovo’s support software and adware. Constant pop-ups, no clear way to disable them—why do hardware manufacturers do this?
5. Windows 11’s Resource-Hogging
   Windows 11 is unnecessarily graphics-heavy. Even on a powerful new laptop, it struggled to keep up with multiple apps and desktops. And the multi-monitor desktop switching was a nightmare. When I switched desktops on one monitor, it switched on the other. As someone who separates workflows across desktops, this drove me absolutely bonkers.

Back to Linux

Installing Ubuntu felt like coming home. Familiar, functional, and reliable.

Why Ubuntu?

It’s based on Debian (which I know well) and offers great out-of-the-box support for 2-in-1s. The touchscreen works, as does screen rotation. I don’t use my laptop as a tablet often, but it’s nice to know I can.

What’s Missing?

The one thing I miss from Windows is my fingerprint reader. It’s not supported yet, but I’m looking into workarounds like Linux equivalents of Windows Hello.

The Verdict

For my needs—CTFs, bug hunting, and exploring networks—Linux just makes sense. It’s lightweight, versatile, and doesn’t get in the way. Windows had its moments, but the limitations added up fast. For now, I’m back in Linux’s loving embrace, where things just work.

If you’re hesitant about switching to Linux or vice-versa, I hope my experience helps you weigh your options. Obviously, you have to try both to see what works for you!

Maybe one day, I’ll find a way to make Windows work for me (or have enough money to waste on a MacBook Pro). Until then, it’s Linux all the way.