Windows' August Update Is Out - The Five-Step Routine That Gets the Fixes Without the Gamble

Published:

Windows’ August update is rolling out now, and the reports started coming in within days. AMD boards with dead USB ports. Crackling audio. Blue screens on reboot. Microsoft has since confirmed the biggest one: KB5121003 was crashing games by interacting badly with RGB-lighting driver software, and a separate update (KB5120708) broke printing in some apps.

Here is the routine that gets you this month’s fixes without the gamble.

TL;DR: Wait two to three days after Patch Tuesday. Back up your Documents and Pictures first - it takes five minutes. Pause updates while the reports come in. Check Microsoft’s release health page before you click Install. If it goes wrong anyway, use System Restore or roll back the update.

Step 1: Back Up First - the Five-Minute Version

A full system backup is the gold standard. But if you have never done one, do not let that stop you. The version that matters most when an update goes wrong is your files: Documents and Pictures.

  1. Plug in a USB drive, or open your cloud storage folder (OneDrive, Google Drive, iCloud)
  2. Copy your Documents and Pictures folders into it
  3. Open a couple of the copied files to confirm they actually copied

Five minutes. If the update breaks your PC, your files are safe, and that is the part you cannot get back. Windows can always be reinstalled. Your tax documents cannot.

Step 2: Wait Two to Three Days After Patch Tuesday

Microsoft releases updates on the second Tuesday of every month. That is Patch Tuesday. This month it was August 11, and the update is KB5121003 (builds 26100.9168 and 26200.9168).

Within days, system administrators were posting about AMD X470 boards losing USB ports after reboot, with DRIVER_POWER_STATE_FAILURE errors (stop code 0x9F). Others reported crackling audio. The r/sysadmin threads filled with blue screens.

The reports are no longer just community reports: Microsoft has confirmed the game crashes - the culprit was an interaction with RGB-lighting driver software, and the fix is to update or remove that software - and it has confirmed KB5120708 broke printing in some apps. Plenty of people still installed the update with no trouble at all.

That mixed picture is exactly why you wait. Not because the update is definitely broken. Because you do not know yet whether it is, and the cost of waiting is small.

Step 3: Pause Updates

While you wait, tell Windows to hold off:

  1. Open Settings
  2. Go to Windows Update
  3. Click Pause updates
  4. Choose one week

This does not skip the update. It delays it. You will still get every security fix - you just get them after the reports have come in, instead of in the middle of them.

Step 4: Check the Release Health Page Before You Click

Before you unpause and install, spend thirty seconds on Microsoft’s Windows release health page. This is the page Microsoft updates when something is actually wrong. If the August update has been added to the known issues list, keep waiting. If the page is clean, install with confidence.

This is the step most people skip, and it is the one that turns a gamble into a decision. You are not guessing anymore. You are reading the same page that IT departments read.

Step 5: If It Goes Wrong Anyway, Roll Back

Sometimes you do everything right and the update still misbehaves. That is not the end of the world. You have two tools:

System Restore. Type “create a restore point” into the Start menu search, open System Properties, and click System Restore. Pick a restore point from before the update and let Windows roll back your system settings.

Uninstall the update. Open Settings > Windows Update > Update history > Uninstall updates. Find KB5121003 (or whatever this month’s update is), click Uninstall, and restart.

This is not hypothetical. Last month’s update broke Dell PCs, and Microsoft had to ship an emergency out-of-band fix (KB5121767). If the same thing happens this month, the rollback is the same: uninstall, wait for the fix, install again later. I wrote up exactly what to do when that happened.

Which Windows Am I On? (Thirty Seconds)

If you are on Windows 11 24H2, this matters more than usual. Press Win + R, type winver, and press Enter. The window that pops up tells you your version and build.

24H2 users, mark October 13, 2026 on a calendar. That is the day Windows 11 24H2 stops receiving security updates. After that date, a bad update is not a temporary problem - it is permanent. There is no next month’s fix coming.

That deadline is why the routine is worth building now, while updates are still safe enough to be routine.

One More Thing: Windows 26H2

You have probably seen the headlines: Windows 26H2 is coming, and Microsoft has officially announced it for around October (PCMag and PCWorld covered the announcement). The good news for people who dread feature updates: 26H2 is an enablement package. That means it is a small switch that turns on features already in your system, not a full reinstall. It should be the last big change of the year.

The same routine applies when it arrives: wait a few days, check the release health page, then let it install.

What to Do Now

  1. Back up your Documents and Pictures (five minutes)
  2. Open Settings > Windows Update and pause updates for one week
  3. On Thursday or Friday, check the release health page for KB5121003
  4. If the page is clean, unpause and install
  5. If something goes wrong, use System Restore or uninstall the update

Updates aren’t optional. But they don’t have to be a gamble.


Want more practical tech guides like this one? They land in your inbox every week. Sign up for the newsletter - no spam, unsubscribe anytime.