Close this search box.
Subscribe to our Newsletter!

If you just learned something new want more of that, subscribe to our newsletter.


Getting Bootrec Fixboot Access Denied error? 6 best solutions

Bootrec Fixboot Access Denied

When using the bootrec /fixboot command, Windows users frequently encounter “Access Denied” errors, particularly when attempting to repair the Master Boot Record (MBR) or Boot Configuration Data (BCD). This obstacle, while frustrating, is not insurmountable. This article aims to explain why Bootrec Fixboot Access Denied error occurs and how to resolve it.

Causes for “Bootrec /Fixboot Access Denied”

  • BCD Corruption: The Boot Configuration Data may be corrupted, leading to access issues.
  • Secure Boot: The Secure Boot feature in the BIOS/UEFI settings can sometimes interfere with repair operations.
  • File System Errors: Errors within the file system on the boot partition can prevent successful execution of the bootrec /fixboot command.

Solutions to Fix “Bootrec /Fixboot Access Denied”

If you’ve recently encountered the Bootrec /Fixboot Access Denied error message, try some of the solutions listed below.

Solution 1: Check Secure Boot Configuration

Disabling Secure Boot temporarily might resolve the access denied issue.

Here’s how to check Secure Boot configuration:

  1. Restart your PC and enter BIOS/UEFI settings (usually by pressing F2, F10, Del, or Esc during boot).
  2. Navigate to the Security or Boot tab and locate the Secure Boot option.
  3. Disable Secure Boot, save changes, and exit the BIOS/UEFI.
  4. Try the bootrec /fixboot command again in WinRE.

Solution 2: Rebuild the BCD to fix Bootrec Fixboot Access Denied

If the BCD is corrupted, rebuilding it might solve the problem.

Here’s how to rebuild the BCD:

  1. Boot from Windows installation media and launch Command Prompt from WinRE.
  2. Type bootrec /rebuildbcd and press Enter.
  3. If prompted, type Y to add the installation to the boot list.

Solution 3: Use Diskpart to Prepare the Partition

Sometimes, setting the system partition as active using Diskpart can resolve the issue.

Here’s how to use Diskpart:

    1. Open Command Prompt from WinRE.
    2. Type diskpart and press Enter.
    3. Type list disk and press Enter to display all disks. Bootrec Fixboot Access Denied
    4. Type select disk X (where X is the number of the disk with the Windows installation) and press Enter.
    5. Type list partition and press Enter.
    6. Type select partition Y (where Y is the number of the System partition) and press Enter.
    7. Type active and press Enter to set the partition as active.
    8. Exit Diskpart by typing exit.

Solution 4: Assign a Drive Letter to the EFI Partition

If the EFI partition doesn’t have a drive letter, assigning one can sometimes allow the bootrec /fixboot command to execute successfully.

Here’s how to assign a drive letter:

  1. Access Command Prompt via WinRE and enter diskpart.
  2. Select the disk and partition as described in the previous steps.
  3. Type assign letter=Z (where Z is a free letter) and press Enter.
  4. Exit Diskpart and try the bootrec /fixboot command again.

Solution 5: Manually Copy the Boot Files

If bootrec /fixboot still fails, manually copying the boot files from the Windows directory might work.

Here’s how to manually copy the boot files:

  1. Access Command Prompt from WinRE.
  2. Identify the Windows and EFI partition letters by using diskpart or by browsing through the Command Prompt.
  3. Use the xcopy command to copy the boot files from the Windows directory to the EFI partition.

Finally, if you encounter a Bootrec Fixboot Access Denied error, follow the steps outlined in this article. Understanding the causes and applying the solutions provided will assist you in resolving your system’s boot issues.

It’s all about methodical troubleshooting to get your computer back up and running. Stick to the instructions, and your system will be operational in no time.

Picture of Aleksandar Ognjanovic

Aleksandar Ognjanovic

Managing editor at Mobile Internist. @lemmingspain My fascination with mobile technology, particularly Android and iOS, began years ago and continues today. I'm captivated by the constant evolution in the smartphone industry and its impact on our daily lives, always anticipating the next big innovation. That’s the main reason why I found myself writing instructive content on the subject for users who are not as familiar with all the bells and whistles.
Notify of
Inline Feedbacks
View all comments