Windows Update / MBR Corruption

MS 40 Reputation points
2026-10-19T21:31:30.66+00:00

Windows Updates (most likely the October 2026 or 26H2 update) resulted in MBR corruption after machines were restarted. Attached are Diag logs from one remediated machine. We had to run a series of bootrec commands to repair the MBR on the affected machines. We are trying to understand the root cause. Windows Update Rings for Windows 11 Feature Updates and Quality Updates have been paused until we can determine the root cause and how to avoid this happening to more devices. Any update from MS: known issue. Please let me know if someone can help

Windows for home | Windows 11 | Windows update

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. MS 40 Reputation points
    2026-10-21T19:48:27.7033333+00:00

    Was this answer helpful?

    0 comments
  2. Palanikumar Annamalai 160 Reputation points
    2026-10-20T08:59:41.59+00:00

    I would not assume that the MBR is being corrupted until the boot mode and partition style are confirmed. Most Windows 11 systems use UEFI with GPT, where bootrec /fixmbr only rewrites compatible master boot code; recovery after that command does not prove that an update damaged the MBR.

    On an affected computer, collect this before making another repair:

    
Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,OsBuildNumber,BiosFirmwareType

Get-Disk | Select-Object Number,FriendlyName,PartitionStyle,OperationalStatus,HealthStatus

Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

reagentc /info

    Also preserve:

    • C:\Windows\System32\LogFiles\Srt\SrtTrail.txt
    • Windows Update, Setup and System event logs
    • BitLocker recovery/status information
    • storage-controller and firmware versions
    • the exact update KB and exact recovery commands used

    Compare affected and unaffected devices by model, BIOS/UEFI firmware, storage controller, disk model, encryption state and image source. If all affected systems share one firmware or storage driver, investigate that before treating the Windows update as the root cause.

    Use Windows Recovery Environment Startup Repair first. On a UEFI/GPT device, diagnose the EFI System Partition and BCD store rather than repeatedly writing MBR code. If this affects several production devices, pause that deployment ring while you establish scope, then validate the KB on a representative test ring and check Windows release health for a confirmed safeguard or known issue.

    Do not post raw logs publicly if they contain computer names, usernames or recovery information.

    Official guidance:

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.