KB5127648 boot failures: reported, not confirmed, worth a pilot ring per model

Call: Deploy with care. This is reported, not confirmed. I count 6 independent first-hand reports, and Microsoft hasn’t put it on release health as of Oct 24. Don’t hold the exploited Shell fix across the whole estate over this. Do pilot by hardware model.

Symptoms: At the finalizing reboot, affected machines show:

0xc000000d before the kernel loads, or “winload.efi missing or contains errors”
an Automatic Repair loop
a BitLocker recovery prompt

One organization saw it without full-disk encryption.

Who’s reporting it:

A Tech Community admin with about 50 Dells.
An admin who also names HP and Lenovo.
An MSP with two OptiPlex 7010 customers.
An AWS-hosted organization.
A Dell Community poster.
An r/sysadmin admin with a ~5,000-device fleet where a few Dell and Dynabook Tecra A60-M machines failed. It’s a small fraction, which is the usual shape of a firmware interaction.

A separate r/sysadmin thread reports sleep hangs and failed or rolled-back installs, and one commenter blames an Intel Modern Standby driver. That’s a different symptom, so it isn’t counted above.

Workarounds from the community, not from Microsoft:

From WinRE, run DISM with /revertpendingactions against the offline image, rebuild the boot files with bcdboot, and pause updates.
Or uninstall the update from WinRE.
Update BIOS and firmware before reapplying it.
Check ESP free space and Secure Boot events 1795/1796/1801.
Before any of that, make sure your recovery keys are in AD or Entra.

Sources: Tech Community thread, Dell Community, r/sysadmin 1xdcuys, r/sysadmin 1xasn7m, pcmasterinsider.