KB5121003 restarts Windows 11 two or three times and blanks the screen (August 15, 2026)

What people are seeing

The complaint that dominated August 15, 2026 was not a crash. It was an install that looked like one. People applied the August security update, the PC restarted, restarted again, and then went to a black screen and stayed there.

Windows Latest put numbers on its own machine: two reboots, more than 15 minutes of install time, and roughly 10 minutes of that spent looking at a black screen. No spinner, no percentage, no message. The build afterwards was 26200.9168 on 25H2 and 26100.9168 on 24H2, which is KB5121003 applied correctly.

That silence is the whole problem. A person watching a black screen for ten minutes after a security update has no way to tell a firmware step from a bricked machine, and the natural reaction, holding the power button, is the one action worth avoiding.

Why the update restarts more than once

The extra restarts belong to the Secure Boot certificate update. Windows Latest describes the sequence as one reboot while the Secure Boot changes are staged, one as the firmware applies the updated certificates, and one as Windows starts using the newly signed bootloader. Microsoft's wording, quoted in the same piece, is 'There are multiple reboots required for the process of updating the certificates' and 'Once the certificates are updated, you won't see these multiple reboots anymore'.

Microsoft set this up in advance. The Windows message center entry on Microsoft Learn, dated August 11, 2026, says that 'With recent and upcoming Windows updates over the next few months, a limited number of consumer and business devices might experience one additional restart during installation', and that the restart 'occurs after a Secure Boot certificate update is applied as part of the Secure Boot update process'.

The same entry explains why this arrives on some machines and not others. The update 'expands high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates', and certificates reach devices 'only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout'. So two identical PCs can take the certificate change in different months.

One extra restart, or three

These two accounts do not line up, and I am not going to pretend they do. Microsoft's message center says one additional restart on a limited number of devices. The reports collected by Windows Latest describe two or three restart cycles and a long blank interval.

Nothing published on or before August 15, 2026 reconciles the difference. It may be that the additional restart Microsoft counts is the one beyond the update's own normal reboot, or that the firmware step behaves differently across vendors. Neither explanation is confirmed, so the practical reading is the conservative one: expect more than one restart, and expect it to take longer than a normal Patch Tuesday.

How to tell this apart from an install that really failed

Once the machine is back at the desktop, winver settles it. A successful KB5121003 install leaves 25H2 at 26200.9168 and 24H2 at 26100.9168. If the build has not moved, the update did not apply, and the multi-restart explanation is not your answer.

Microsoft's position is also that this is a one-time event per machine, not a new monthly pattern: once the certificates are updated, the additional restarts stop. So if a later update repeats the long black screen on the same PC, that is worth treating as a separate problem rather than as this one.

What you can do today

There is no patch here and nothing to repair. The work is not interrupting a firmware write. In order:

1. Install the August update when you can leave the machine alone for half an hour, not five minutes before you need it.

2. When the screen goes black during the install, leave it. Do not hold the power button and do not cut the power. This is the step where the firmware is taking the new certificates.

3. Give it at least 20 minutes before you treat it as stuck. The measured case was about 10 minutes of black screen inside a 15-plus minute install.

4. When the desktop returns, press Windows and R, type winver and press Enter. Confirm 26200.9168 on 25H2 or 26100.9168 on 24H2.

5. If the build did not move, look at Settings, then Windows Update, then Update history, and treat it as a failed install rather than as the certificate sequence.

6. If you look after several PCs, stagger the installs. A row of machines all sitting dark at the same time is how this turns into a support queue.