Forum Discussion
October 2026 Windows Update causing major issues
A missing or corrupt winload.efi right after a servicing reboot usually means the boot files on the EFI System Partition could not be updated cleanly, not that the OS volume is damaged. Some things I would check:
- ESP free space. A small ESP (100 MB) that is nearly full is a classic cause of boot file updates failing halfway. Compare the affected Dells with a few healthy ones of the same model.
- BIOS and Secure Boot state. Compare BIOS version, Secure Boot on or off, and the Secure Boot certificate state between affected and unaffected machines. Boot manager and certificate servicing has been touching this area, and old Dell firmware is where it tends to break. The Secure Boot servicing events (1795, 1796, 1801) in the System log can show whether it started and failed.
- Find the pattern. Group the 50 by model, BIOS version, BitLocker state and the date the update landed. If they share one or two models or an older BIOS, that is your root cause, and the Dell BIOS update you are already pushing is the right fix.
Until you know the cause, hold the update on any Dell model that has not taken it yet, and run it through a small pilot group first. Staged rings are what keep a bad update at 5 machines instead of 50.
Thank you for your response. I'll check the items you've mentioned.
Unfortunately, I work for a financial institution where cyber security is a top priority so there is a little obsession with patching and presenting pristine numbers to stakeholders, so staging and testing updates has not been part of the protocol. Hopefully this changes people's mindset.