How to fix Bootrec /fixboot Access is denied during to fix Boot Configuration Data

How to fix Bootrec /fixboot Access is denied during to fix Boot Configuration Data
Hi guys, here I showed up on this video how to fix bootrec /fixboot access is denied, during to fix boot configuration data. Bootrec /fixboot access denied appears when a user attempts to fix Error Code 0xc0000225. This is not a common issue that occurs on a regular basis. Usually, users run the bootrec /fixboot command in order to write a new boot sector to the system partition. In case, If you have encountered an error during to fix boot configuration data then this video is for you.

----------------------------------------------------------------------------------------------------------

Of course, let us know your opinion.
Please Like, Comment we need your support.
And guys please don't forget to Subscribe our channel ASA Technical.
Thank you.

[germartinez]

it doest work, but you can do this

open systemadvanced options as admin console

>cmd prompt

then,

>type bootsect/nt60 sys

this will actually update your target volumes with BOOTMGR Compatible boot code)

then try

>bootrec/fixboot

>bootrec/fixmbr

now definitely works with this fix. in build 1709

[carstenschmidt]

I ran into the "bootrec /fixboot access denied" issue after trying to install openSUSE Leap 42.3 next to Win 10 on my notebook. Neither the suggested solution in this video nor anything else that I was able to find within ~5 hours research solved the problem.
The solution was as follows:
When looking at the partition table using parted from my SUSE rescue system, I realized the "pmbr_boot" flag was turned on which didn't make much sense as my notebook was set to UEFI boot. Switching this off (issuing "disk_set pmbr_boot off" in parted) immediately solved the issue and I was able to boot into Windows (not even need to run bootrec).
Hope sharing this might be of use for anyone else

[surojitjana]

I'm still having the problem
Bootrec \fixboot
Access is denied

[ARCADBLOOD]

V:\efi\microsoft\boot>bootrec /fixboot
Acces deined
-.-

[mafirus]

I had this problem for a couple of days. My solution was to perform a clean Windows Install:
1. Mount a Windows image on an Usb/DVD via MediaCreationTool.exe.
Plug the USB and boot from it.
Go to repair > Advanced Options > Command prompt
Enter to Diskpart:
-diskpart.
Inside of Diskpart type the following:
-list Disk
-sel disk 0 (depends on wich disks listed, just select the disk where you want to install windows)
-clean
-create partition primary
-select partition 1
-active
-FORMAT FS=FAT32 Quick (if it doesnt work with Quick you can also type it without Quick)
-ASSIGN
-exit
Basically this way we performed a full clean to our hdd.
Now we can proceed to a clean Windows Install:
-Boot from USB media drive.
-Proceed with the clean installation.
In the case that you need to convert your drive from UEFI to GPT due to an error during the installation, you can follow these steps:

[moemedimartin]

What doesn’t make sense is that you have assigned new letter from C: to V:

Then why still using it again.
bcdboot c:\windows /L en-us /s v: /f

It doesn’t work...????

[mathfromzero_]

thanks for this tutorial. manage to recover boot error on HP Laptop..

[V.Z.]

7:28 ... completed all steps: >bootrec /fixboot
Access is denied.

How to get around this?

[cezarmiranda]

This video makes no sense. The volume you rename as V: was your C:... So how is bcdboot supposed to copy files from C: to V: when there is no C: anymore?

[filosweet]

Still same after v:\efi\microsoft\boot>bootrec /fixboot access is denied.

[rhabarbarums]

Do not run the "bootsect" command (e.g. "bootsect /nt60 sys").

The "bootrec /fixboot" command can no longer be used for boot repair, because the command always shows "Access is denied". Microsoft has prevented the use of the "bootrec /fixboot" command on both GPT and MBR disks.

Windows 10 version 1703 (April 5, 2017) and earlier installation media.
- bootrec /fixboot -> "The operation completed successfully"

Windows 11 and Windows 10 version 1709 (October 17, 2017) and newer installation media.
- bootrec /fixboot -> "Access is denied"



You don't need the "bootrec /fixboot" and "bootrec /rebuildbcd" commands if you use the BCDBOOT command.

If the system partition has been corrupted, you can use BCDBOOT to recreate the system partition files. BCDBOOT copies the boot files from the Windows partition to the system partition and creates the Boot Configuration Data (BCD) store in the same partition.

On a GPT disk, BCDBOOT copies the boot files to the EFI system partition. On an MBR disk, BCDBOOT copies the boot files to the active partition on the primary disk (either an active System Reserved partition or an active Windows partition).



Tutorial: How to use the BCDBOOT command on a GPT disk.
- Windows 10/11 is installed in UEFI/GPT mode.

- Unlike an MBR disk, a GPT disk does not have an active partition.
- The EFI system partition has a FAT32 file system.
- The EFI system partition and the Windows partition are not always on the same disk.
- The EFI system partition does not have a volume letter assigned by default, but you can temporarily assign a letter using diskpart.

BCDBOOT <source> [/s <volume letter> [/f <firmware type>]]

You can skip the format command if you don't want to format the EFI system partition.

diskpart
list volume
select volume # (where # is the number of the EFI system partition)
format quick fs=fat32 (you can skip this command)
assign letter=z
list volume
exit

bcdboot x:\windows /s z: /f uefi

- replace "x" with the volume letter of the Windows partition
- z: is your EFI system partition you assigned above

BCDBOOT copies the boot files from the Windows partition to the EFI system partition and creates the Boot Configuration Data (BCD) store in the same partition.

[MohamedMohamed-yxbo]

Hi, I followed all the steps you mentioned here but still says 'Access is denied', also when I input the the cmd as, V:\>md \efi\microsoft\boot, as soon I received, A subdirectory or file \efi\microsoft\boot already exists, could you solve this or what could be the reason of this?

[milanmondal]

Excellent and very informative. Works for novices

[thatguy]

Literally have no idea what your saying

[jvon]

I've followed so many videos now, that I believe my lap top is just done. ACCESS DENIED. I feel like Gandalf is guarding entry into my computer.

[hellcat]

Anyone else notice that he edited the video to have it show the operation completed successfully at 7:51? You can tell it's an edit because the monitor bobs with the pressure of his hands on the desk, but the text doesn't move and there's a graphical inconsistency on the left side of that line of text in the surrounding program window where the black border turns white for the height of that line. The font and position of text in relation to the other text in the line above is also inconsistent with the previous command lines. He's a faker guys.

[vaitri]

Hi I am in trouble as I have done this to my company laptop 🤪
Well so here is the wall I am facing...
A. Assigned letter V to my system reserved partition in Diskpart.
B. Then commands and error as follows-
1. X:\windows\system32>V:
V:\>
2. V:\>md \efi\microsoft\boot\
A subdirectory or file \efi\microsoft\boot\ already exists.
3. V:\>cd /d v:\efi\microsoft\boot\
V:\efi\microsoft\boot\
4. V:\efi\microsoft\boot>bootrec /fixboot
Access denied.


I don’t know what is wrong here.
A little history-
I had a dual boot, win 10 and Manjaro arch Linux. Since windows was very slow so tried Manjaro alongside for a while. Later yesterday I used G Parted in Manjaro to increase the size of windows C drive and doubled it. There was no loss of data anywhere as I once restarted it and used windows for a while. And this time deleted the Manjaro partition because windows became better after giving it 201 GBs.
To my worst nightmare, this time when I restarted I got stuck at Grub Rescue. And then started following your videos. Somehow got out of grub rescue but stuck at boot configuration error and all attempts result in Access denied.

[googleuser]

This only applies if you have an EFI boot record some people still have a Legacy BIOS and then this will not work

[leosoldado]

CANNOT READ INSTRUCTIONS BECAUSE TOO SMALL. I am watching this on my phone since my 2-in1 Windows device does not boot into windows.

[livr]

When I type MD \efi\Microsoft\boot\ it says a undertheme or a data with the name "\efi\microsoft\boot\ already exist