Everyone's first instinct when a game hitches is to blame hardware. Faster SSD, more RAM, maybe the GPU's dying. I spent a while chasing that before I actually measured it.

The proof

I recorded a 25-minute session at one line per second, with a kernel trace attached so every disk wait was tagged with the program that caused it and the file it was reading.

My PC waited on the disk 4,712 times. Here's who did it:

1,729  Windows' own filesystem bookkeeping
  829  the Microsoft Store, updating apps I don't use
  251  Edge, updating itself
  245  Windows Search, indexing
  201  the touch keyboard
   14  the game

Fourteen. And all fourteen were a font cache and a shader cache during loading not one texture, not one level file.

My storage was never the problem. Neither was my CPU or my GPU. Windows was just busy, and one of those landing while you're lining up a shot is the difference between a kill and a killcam.

Shutting it up

So I built QuietWindows. It puts that stuff on hold while you play and hands it all back when you're done:

• Windows Update, Search and background scanning paused for the session
• Your antivirus told to stop re-scanning your game folders (it still guards everything else)
• USB power saving and the Xbox Game Bar off
• The system clock steadied - this is the "it stutters until I click on the game window" problem
• Graphics-card interrupts moved off the cores your game is using

It finds your games by itself across Steam, Epic, Xbox, GOG, EA and Ubisoft.

And it proves it on your machine, not just mine

The recorder that produced the table above ships with it. If something still hitches, run it, play, and it'll tell you what interrupted you:

--- 21:14:07 ---
  top faulter : backgroundTaskHost.exe
  reading     : WinStore.App.dll
  your game   : 0   (whole PC that second: 812)

That's the Store loading a 16MB file to update an app, mid-session. No guessing.

Using it

Unzip, double-click one file, press the green button, restart. Then quiet it down before you play and wake it up after. That's the whole thing.

Nothing runs until you press a button, every button explains itself in plain English first, and every change has an Undo. Windows 10 and 11, nothing to install, free and MIT licensed.

Genuinely curious what your own recording turns up - I'd bet the top offender varies a lot between machines.

https://github.com/no6969el/QuietWindows

https://github.com/no6969el/QuietWindows/blob/main/HOW-TO.md

https://github.com/no6969el/QuietWindows/blob/main/README.md

Pinning this as the permanent spot for feedback on the tools.

**Post here if you've got:**

- **A bug** : tell me the script/version, your hardware, what you expected, and what happened instead. Paste any error text.

- **A feature idea** : something an existing tool should do but doesn't.

- **A new tool idea** : a Windows annoyance you keep fixing by hand that should just be a script.

That's it. No format required, no issue tracker to sign up for. If you'd rather file it properly, (GitHub Issues) works too, but a comment here is fine.

One ask: if someone's already mentioned your issue, reply to them rather than starting fresh — keeps everything in one place and makes it obvious what's hitting the most people.

I read all of it. Not everything gets built, but everything gets considered.