How to Fix Bootrec Fixboot Access Denied in Windows 10 and 11

If you are staring at a bootrec fixboot access denied error in the Windows Recovery Environment, your PC will not boot and the standard repair command refuses to run. The good news is that the error is almost always a permissions problem with the EFI or system partition, not a dead drive, and it can be fixed from the same Command Prompt with a few extra steps.

This guide covers the most reliable fixes in order: assigning a drive letter to the EFI partition, rebuilding the boot files with bcdboot, and the legacy BIOS fallback. Work through them from the top, and stop as soon as Windows boots again.

Why Bootrec /Fixboot Says “Access Is Denied”

The bootrec /fixboot command writes a new boot sector to the system partition. On modern UEFI systems, that partition is the small FAT32 EFI System Partition (ESP), usually 100 to 500 MB. If the EFI partition has no drive letter, if you are using older installation media, or if the disk uses a legacy MBR layout instead of GPT, Windows blocks the write and reports “Access is denied.” The fix is to give the command a path it can write to, or to rebuild the boot files with a tool that does not need /fixboot to succeed first.

bootrec fixboot access denied fix in Windows Recovery Environment

Before You Start: Open Command Prompt in WinRE

Boot from Windows installation media (USB or DVD), choose your language, then click Repair your computer > Troubleshoot > Advanced options > Command Prompt. If your PC fails to start twice in a row, Windows may open the Recovery Environment on its own.

One warning before you type anything: drive letters inside WinRE are often different from normal Windows. The drive you know as C: may show up as D: or E: here. Always confirm with diskpart and dir before you run a command against a letter.

Method 1: Assign a Letter to the EFI Partition, Then Run Fixboot

This is the fix that works most often on UEFI systems, because it solves the actual cause: bootrec cannot reach an EFI partition that has no drive letter.

1. In Command Prompt, type diskpart and press Enter.
2. Type list disk, then select disk 0 (use the number of the disk Windows is installed on).
3. Type list volume and look for the EFI partition: it is small (around 100 to 500 MB) and formatted as FAT32. Note its volume number.
4. Type select volume X (replace X with the EFI volume number), then assign letter=V:. Use any free letter.
5. Type exit to leave diskpart.
6. Now repair the boot files on that partition:
cd /d V:\EFI\Microsoft\Boot\
bootrec /fixboot
bcdboot C:\Windows /s V: /f UEFI
(Replace C: with your actual Windows drive letter in WinRE, and V: with the letter you assigned.)
7. Restart the PC and remove the installation media.

The bcdboot command copies fresh boot files from your Windows folder to the EFI partition, so even if /fixboot still complains, the rebuilt files often get Windows booting again.

Method 2: Skip Fixboot Entirely and Use Bcdboot

If bootrec /fixboot keeps returning “Access is denied” after Method 1, skip it. bcdboot writes its own boot files and does not require /fixboot to succeed first.

1. From Command Prompt in WinRE, run diskpart, list vol, and confirm the FAT32 EFI volume (UEFI) or the active NTFS system volume (BIOS).
2. Assign it a letter, for example assign letter=S:, then exit.
3. Run bcdboot C:\Windows /s S: /f ALL (again, adjust C: to your real Windows drive letter in WinRE).
4. Restart and test.

Use /f UEFI on a GPT disk and /f BIOS on an MBR disk. The /f ALL switch covers both, which is handy when you are not sure which layout the disk uses.

Method 3: Legacy BIOS and MBR Disks (Bootsect)

On older PCs with legacy BIOS and an MBR disk, the “Access is denied” message sometimes clears after refreshing the master boot code. From Command Prompt in WinRE, run:

bootsect /nt60 SYS
bootrec /fixboot
bootrec /fixmbr
bootrec /scanos
bootrec /rebuildbcd

/fixmbr rewrites the master boot record, /fixboot writes a new boot sector, /scanos lists Windows installations, and /rebuildbcd adds them back to the boot store. None of these touch your personal files.

Method 4: Rebuild the BCD When No Windows Installation Is Found

If bootrec /rebuildbcd reports “Total identified Windows installations: 0,” the boot store is missing or too corrupt to read. Back it up and rebuild it from scratch:

bcdedit /export C:\bcdbackup
attrib c:\boot\bcd -s -h -r
ren c:\boot\bcd bcd.old
bootrec /rebuildbcd

When the scan finds your installation, type Y to add it, then restart.

If It Still Says Access Denied

Try these in order. First, use current installation media: the error is a known quirk of some older Windows 10 install images, and a freshly created USB from the Media Creation Tool avoids it. Second, disable Fast Boot and Secure Boot in the BIOS/UEFI settings, run the repair, then re-enable them afterwards. Third, confirm the firmware mode matches your commands: /f UEFI on an MBR disk (or /f BIOS on a GPT disk) will fail, so check the layout in msinfo32 or diskpart first.

As a last resort only, the EFI partition can be reformatted to FAT32 and rebuilt with bcdboot. Do not do this casually: formatting the EFI partition destroys the existing boot files, so back up the BCD store first with bcdedit /export and only proceed if every method above has failed.

Frequently Asked Questions

Does bootrec /fixboot access denied mean my hard drive is dead?
No. In most cases it means the EFI or system partition is unreachable or has no drive letter, or the installation media is at fault. Your files are usually untouched, and the fixes above repair the boot files without touching personal data.

Why does bootrec /fixboot fail on UEFI but work on older PCs?
UEFI systems boot from the FAT32 EFI System Partition, which often has no drive letter assigned in WinRE, so the write is blocked. Legacy BIOS systems boot from the MBR, where /fixboot writes directly. That is why the diskpart letter assignment fixes most UEFI cases.

Can I just use bcdboot instead of bootrec /fixboot?
Yes. bcdboot copies fresh boot files to the system partition and does not depend on /fixboot succeeding. Many repairs succeed with bcdboot alone after assigning the EFI partition a letter.

Will these commands delete my files?
No. bootrec, bcdboot, and bootsect repair boot records and boot files only. They do not format the Windows partition or touch your documents, photos, or installed apps.

Sources:

Microsoft Q&A — Bootrec Access Denied: https://learn.microsoft.com/en-us/answers/questions/4157880/bootrec-access-denied
Microsoft Q&A — 0xc0000098 / bootrec access denied: https://learn.microsoft.com/en-us/answers/questions/3919521/i-get-the-blue-screen-with-0xc0000098-error
Web Asha — Windows Repair Commands: SFC, DISM, CHKDSK, Bootrec: https://www.webasha.com/blog/what-are-the-essential-windows-repair-commands-learn-how-to-fix-windows-errors-using-cmd

Check the Content

Axee Davies

Axee Davies is the founder of AxeeTech, publishing gaming guides, codes, and Windows how-tos since March 2013. A tech enthusiast for 13+ years — starting with smartphones and Android rooting — he now runs a site that puts out a new guide every day for Roblox players, traders, and Windows users. More about AxeeTech

axeetech.com