Quick Answer
Run diskpart to rebuild the BCD or set the partition active — most of the time that clears 0X00000943. If not, check your BIOS boot mode (UEFI vs. Legacy).
Why This Happens
This error pops up when Windows Boot Manager tries to read a boot file from a disk offset that doesn't exist. The start offset is out of range — meaning the pointer in the boot configuration data (BCD) points to a location past the end of the partition or disk. I've seen it on older machines with MBR disks, especially after cloning or resizing partitions. It also shows up when the partition isn't marked active, or when you've switched between UEFI and Legacy BIOS without reinstalling.
The culprit is almost always a mismatch between the partition table and what the boot loader expects. Don't bother with startup repair from the install media — it rarely fixes this one because it doesn't touch the raw offset values.
Fix Steps
Step 1: Boot from Windows Installation Media
You'll need a USB or DVD with Windows setup. Plug it in, boot from it, and choose your language, then click “Repair your computer” at the bottom left.
Go to Troubleshoot > Advanced Options > Command Prompt.
Step 2: Rebuild the BCD with diskpart
In the command prompt, type diskpart and hit Enter. Then:
list disk
select disk 0 (or the correct disk number)
list partition
select partition 1 (the system partition, usually 100-500 MB)
active
assign letter=S
exitNow fix the boot files:
bcdboot C:\Windows /s S: /f ALLReplace C: with your actual Windows drive letter if needed. This rewrites the BCD and boot manager files. Reboot and see if the error is gone.
Step 3: Check Partition Offset with diskpart
If that didn't do it, the partition itself might have a bad offset. Run diskpart again:
select disk 0
select partition 1
detail partitionLook for “Offset” in the output. For MBR disks, it should be 1 MB (1048576 bytes). If it's something crazy like 0 or a huge number, you're in for a partition rebuild — but that's rare.
Alternative Fixes
Change BIOS Boot Mode
If you're on UEFI and the disk is MBR, or vice versa, that triggers this error. Reboot, enter BIOS (usually F2 or DEL), find Boot Mode or UEFI/Legacy setting, and switch it. If you have a UEFI disk, set it to UEFI. If MBR, set to Legacy/CSM. Save and reboot. This works when the error appears right after a BIOS update or hardware change.
Use Easy Recovery Essentials
Skip the Windows tools if they keep failing. Download Easy Recovery Essentials (it's a bootable ISO), burn it to a USB, and run its Automated Repair. It's saved me more times than I can count. Costs $80 but worth it for a business machine.
Manual BCD Edit
For the advanced folks: open the BCD with bootrec /fixboot and bootrec /rebuildbcd from the recovery command prompt. If the BCD is corrupt, these commands clean it up. Do them in order:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcdFollow the prompts to add the Windows installation. This is the manual way, and it's exactly what startup repair should do but doesn't.
Prevention Tips
Stop messing with partition tools like MiniTool or AOMEI unless you know what you're doing. Cloning a disk to a smaller target or resizing beyond the drive's physical end is the #1 cause of this error. Always leave at least 100 MB of unallocated space at the end of the disk.
Also, when you clone a system drive, use the vendor's tool (Samsung Magician, Intel SSD Toolbox, etc.) rather than third-party ones. They handle offset alignment properly.
And if you're switching between Legacy and UEFI, expect this error. Do a clean install if you can't avoid the switch — it's less pain than fighting the boot loader.