KB5121003 drops refresh rates and breaks HDR on Windows 11 (August 17, 2026)

What the display symptoms are

Three distinct complaints are grouped together in Notebookcheck's August 17, 2026 write-up by author Darryl Linington: monitors dropping to a lower refresh rate on their own, screens going black at sign-in or on wake, and HDR either failing to engage or rendering washed out.

They were listed the day before too. Windows Latest on August 16, 2026 put broken HDR and refresh-rate drops in its round-up of KB5121003 problems, alongside the game crashes and the Windows Hello failures. The affected builds are the same in both accounts: 26200.9168 on Windows 11 25H2 and 26100.9168 on 24H2, after the August 11, 2026 update.

What nobody has produced is a reproduction. The reports describe the symptoms as intermittent, which is exactly the profile that resists diagnosis: a refresh rate that reverts sometimes, a black screen on some wakes, HDR that works until it does not.

Why these are not the RGB driver crashes

The loudest KB5121003 story this week is the game crashes covered in the August 16 post, and it has a named cause. Notebookcheck quotes Embark Studios, which makes THE FINALS, saying that 'the update changed something that broke compatibility with that file' about inpoutx64.sys, a driver that arrives with hardware utilities such as Razer's update software.

The display complaints do not fit that explanation. They are reported on machines with no RGB utility installed, so there is no inpoutx64.sys to blame and nothing to remove. Notebookcheck keeps them in a separate bucket for that reason, as display-related changes bundled into the August update.

That distinction matters in practice. If your monitor is dropping to 60 Hz, deleting a kernel driver you may not even have is not a treatment for it, and it costs you whatever installed the driver. Two problems in one update are still two problems.

What has not been published

There is no Microsoft known-issue entry for the display symptoms as of August 17, 2026. That means no acknowledgement, no official workaround, no fix build and no list of affected hardware.

There is also no published pattern by GPU vendor, driver version, panel, cable type or connection standard. I am not going to invent one. What exists today is a set of user reports, two outlets grouping them the same way, and a single common factor, which is that the machines took KB5121003.

One more gap worth naming: nobody has said whether the refresh-rate drop and the black screens are the same fault seen from two angles or two unrelated regressions. They are reported together because they arrived together.

The rollback, and what it costs

With no fix and no workaround, the only lever left is removing the update, from Settings, then Windows Update, then Update history, then Uninstall updates. Both outlets are blunt about the price of pulling that lever.

Notebookcheck calls the uninstall a last resort because KB5121003 closes an actively exploited zero-day, which it names LegacyHive, and Windows Latest describes the update as addressing up to 400 security issues. Rolling it back means a machine with working HDR and no protection against a flaw that is being used against real systems right now.

So the calculus is narrow. If a display fault makes the PC genuinely unusable, an uninstall buys you working hardware for as long as you leave the patches off. If it is an annoyance, the security side of the trade is worth more than the convenience.

What you can do today

There is nothing to install for this on August 17, 2026, so the useful work is narrowing the symptom and holding the security line. In order:

1. Write down exactly what fails: which monitor, which port, and whether it happens at sign-in, on wake or at random. Intermittent faults get fixed on the strength of that detail.

2. Confirm the build. Press Windows and R, type winver and press Enter. Expect 26200.9168 on 25H2 or 26100.9168 on 24H2.

3. Set the refresh rate back by hand in Settings, then System, then Display, then Advanced display, and note whether it holds after a restart.

4. If HDR looks wrong, turn it off under Settings, then System, then Display, and check whether the picture is correct without it. That separates an HDR fault from a panel or cable problem.

5. Keep the update unless the machine is unusable. If you do uninstall it, from Settings, then Windows Update, then Update history, then Uninstall updates, plan to put the patches back as soon as you can.

6. Do not remove inpoutx64.sys for a display fault. That driver belongs to the game crashes, and taking it out costs you the utility that installed it.