The safest Windows 11 repair path is to start in Windows Recovery Environment (WinRE), run Startup Repair, then inspect the disk and rebuild the UEFI boot files with bcdboot. The message from bootrec /fixboot means WinRE could not write the expected boot-sector data; it does not, by itself, mean Windows must be reinstalled.
What “bootrec /fixboot access is denied” means
bootrec /fixboot is an offline boot-repair command. It is run before normal Windows starts, usually from Command Prompt in WinRE. “Access is denied” indicates that the recovery environment could not successfully write the boot data it expected to reach. Commonly, the machine is using UEFI firmware with a separate FAT32 EFI/System partition, and the partition or its boot-file path has not been correctly identified in the recovery session.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The error is a symptom, not a diagnosis. The underlying problem may be missing or damaged boot files, an incorrect BCD path, a recovery-session drive letter that differs from normal Windows, or a storage and controller issue that prevents the boot volume from being read. The repair process below checks those conditions in a controlled order.
What you need before making changes
- A Windows 11 installation USB or other Windows installation media. Booting from it provides WinRE when the copy on the internal drive cannot start.
- Time to identify the correct volumes. WinRE can assign different letters than the normal Windows session, so never assume that the Windows partition is
C:. - Your BitLocker recovery key if the device is encrypted. Startup Repair and offline access can require recovery information before they can examine the protected volume.
- A backup destination, when possible. Export the BCD before rebuilding it, and avoid changing partitions until important files are protected.
Disconnecting nonessential USB storage, docks and external drives can make the disk list easier to read. Leave the Windows installation media connected until all recovery work is complete.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Repair the boot process in the recommended order
1. Enter WinRE from installation media
- Insert the Windows 11 installation media and start the computer from it. Use the firmware boot menu if the computer normally starts from the internal drive.
- At the Windows Setup screen, choose Next.
- Select Repair your computer, then choose Troubleshoot.
- Open Advanced options. This menu contains Startup Repair and Command Prompt.
If the internal recovery environment is still available, it may also offer the same tools. Installation media is the dependable route when the internal recovery files are missing or the machine repeatedly returns to the boot error.
2. Run Startup Repair first
Choose Advanced options > Startup Repair and let Windows examine the installation. Startup Repair is designed to correct many startup problems, including missing or damaged system files, a corrupted BCD, a damaged MBR, incompatible drivers and certain registry errors. It may restart the computer more than once.
When the process finishes, remove the USB temporarily and try a normal boot. If Windows starts, do not run additional boot commands simply because /fixboot previously failed. If Startup Repair reports that it could not repair the PC, return to Advanced options and open Command Prompt.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →3. Check which disk and volumes WinRE can see
At Command Prompt, start DiskPart and list the disks and volumes:
diskpart
list disk
list vol
exitConfirm that the disk containing Windows is present. In Microsoft’s UEFI example, the operating-system volume is formatted as NTFS and the SYSTEM volume is formatted as FAT32. A marker in the GPT column of list disk indicates the GPT layout used by that example. The FAT32 SYSTEM/EFI volume is the small partition that stores UEFI boot files; it is not the large NTFS Windows volume.
Read the volume labels, sizes and file systems together. A drive letter shown in this session is temporary and may not match the letter Windows normally uses. If the expected disk is absent, stop before changing BCD data: a cable, storage-controller setting, firmware mode or hardware problem may be preventing WinRE from accessing it.
4. Identify the Windows volume and verify its letter
Use the letters displayed by list vol as candidates, then verify each one by checking for the Windows directory. For example:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstalldir D:WindowsReplace D: with each candidate letter. The correct volume contains the Windows directory and the expected system folders. Do not choose a volume solely because it is labeled “Windows” or because it has the familiar letter C:.
Write down the verified operating-system letter. You will substitute it for <OSDrive> in the BCDBoot command later.
5. Identify and, if necessary, temporarily letter the FAT32 SYSTEM volume
From the list vol output, locate the FAT32 volume used for UEFI boot files. If it already has a letter, record it as the SYSTEM drive. If it has no letter, you can assign a temporary one without formatting the partition:
diskpart
list vol
select volume <SYSTEM-volume-number>
assign letter=R
exitReplace <SYSTEM-volume-number> with the number you actually identified. Choose a letter that is not already in use. The assignment is only to make the partition addressable during this recovery session. Do not select an NTFS data volume by mistake.
Recommended Free Tools
6. Inspect and back up the BCD
At Command Prompt, display the current boot configuration:
bcdeditOn a UEFI installation, check the {bootmgr} entry. Microsoft’s documented path is EFIMicrosoftBootbootmgfw.efi. A different path, a missing entry or an inaccessible device points to a BCD or boot-file problem rather than a reason to format the disk.
Export the BCD before changing it. Microsoft gives this example:
bcdedit /export C:tempbcdbackupThe destination must be writable in the current WinRE session. If the shown path is unavailable, use a writable folder on a verified volume or an external backup location, while retaining the exported file until the computer boots normally.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
7. Rebuild the boot files with BCDBoot
BCDBoot is Microsoft’s documented utility for recreating missing or damaged boot files from the Windows directory. Use the verified Windows and SYSTEM letters in this pattern:
bcdboot <OSDrive>:windows /s <SYSTEMdrive>: /f ALLFor example, if dir D:Windows confirmed the operating-system volume and the FAT32 SYSTEM partition is R:, run:
bcdboot D:windows /s R: /f ALLThe /f ALL option tells BCDBoot to create boot files for both UEFI and legacy firmware types. The command must use the letters from the current WinRE session, not letters remembered from normal Windows. A successful command reports that the boot files were created.
If BCDBoot reports that it cannot copy files, recheck the Windows directory with dir, confirm that the target is the FAT32 SYSTEM volume, and review the BCD export. Do not respond by formatting the partition. Formatting is destructive and is not required by the inspection, backup and rebuild procedure described here.
8. Restart and test
- Close Command Prompt and choose the option to continue to Windows, or restart from the WinRE menu.
- Remove the installation USB when the firmware begins the next boot, unless you need it again.
- Allow the computer to boot once without interrupting it. The first successful start may take longer while Windows completes recovery work.
- If BitLocker prompts for recovery information, enter the key associated with that device.
If Windows starts, confirm that the normal system drive and files are available before deleting the BCD backup. Keep the backup until you are satisfied that several restarts work.
If Windows still will not start
Review the volume and BCD assumptions
Return to WinRE and repeat diskpart, list disk and list vol. A changed drive letter is common after a restart into a different recovery session. Verify the Windows directory again, confirm that the disk has the expected GPT marker for a UEFI layout, and make sure the SYSTEM volume is the FAT32 partition rather than a recovery or data volume.
Run bcdedit again and check whether {bootmgr} points to EFIMicrosoftBootbootmgfw.efi. If the entry refers to a letter or path that does not exist on the identified SYSTEM volume, export the current BCD and rerun BCDBoot with the corrected letters.
Check that boot files are present
With the SYSTEM volume letter assigned, inspect the expected folders using commands such as:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →dir R:EFIMicrosoftBootReplace R: with the letter you assigned. The exact contents can vary, but the purpose is to establish whether the Microsoft boot directory exists on the FAT32 volume. If the folder is absent or unreadable, verify the target selection and rerun BCDBoot rather than copying files from an unrelated computer.
Consider storage and firmware settings
Microsoft lists storage or controller problems among possible causes of inaccessible-boot failures. If the disk disappears from list disk, appears intermittently, or cannot be read consistently, boot-file rebuilding will not solve the underlying access problem. Check the firmware storage mode and boot order against the configuration used before the failure, and consult the computer or motherboard documentation before changing a controller mode. An unexpected switch between UEFI and legacy/CSM modes can make a valid installation appear unbootable.
Read the Startup Repair log
Startup Repair records diagnostic information in WinRE. If the automated attempt failed, use the log to determine whether it identified damaged boot files, a BCD problem or a storage error. Treat the log as evidence to guide the next check; it does not replace verifying the actual disk and volume layout.
Use installation media when the internal recovery environment is unavailable
A damaged internal recovery partition can prevent the normal Troubleshoot menu from loading. Booting from Windows 11 installation media provides the same WinRE tools independently of that partition. If the installation media cannot see the internal disk, resolve disk detection or firmware issues before attempting more BCD changes.
Free tools Windows power users keep installed
One-click scans. No signup required.
UEFI/GPT and legacy BIOS/MBR: choose the right path
| Characteristic | UEFI/GPT example | Legacy BIOS/MBR consideration |
|---|---|---|
| Disk indicator | list disk shows a GPT marker in Microsoft’s example. |
The GPT marker is not present. |
| System partition | A FAT32 SYSTEM/EFI volume holds UEFI boot files. | The boot arrangement differs and may not use a FAT32 EFI volume. |
| BCD boot-manager path | EFIMicrosoftBootbootmgfw.efi is the path to verify for {bootmgr}. |
Do not assume the UEFI path applies; first establish the firmware mode and volume layout. |
| BCDBoot example | bcdboot D:windows /s R: /f ALL, with letters replaced by those found in WinRE. |
Use the same identification-first approach, but do not select an EFI volume that does not belong to the installation. |
The command shown with /f ALL is useful when the firmware mode needs to support both styles, but it cannot compensate for selecting the wrong system partition or an unreadable disk.
Common mistakes that make the error worse
- Assuming
C:is Windows. WinRE frequently assigns another letter. Confirm withdir <letter>:Windows. - Choosing a partition by size alone. The EFI/System volume is identified by its FAT32 file system and role, not by a guessed size.
- Running BCDBoot against the FAT32 volume as the source. The source must be the Windows directory on the NTFS operating-system volume; the FAT32 volume is the destination for boot files.
- Skipping the BCD export. Exporting first gives you a recoverable copy before offline changes.
- Formatting the EFI/System partition as a first response. Formatting destroys data and is not part of the documented inspection-and-rebuild workflow.
- Changing firmware storage mode casually. A controller-mode change can make an otherwise readable Windows installation inaccessible.
- Repeating
/fixbootwithout checking the layout. The access-denied message will remain if the actual issue is an incorrect volume, missing boot files or a storage problem.
When a reinstall is and is not justified
A failed /fixboot command alone is not evidence that Windows must be reinstalled. Startup Repair, volume identification, BCD backup and BCDBoot can address missing or damaged boot files without replacing the operating system. Reinstallation becomes a separate decision only after you have confirmed that the Windows volume and storage are readable, the firmware configuration is appropriate, boot files have been rebuilt, and other recovery options cannot restore startup. Protect personal data first, because reinstalling can alter or remove existing files depending on the chosen method.
Quick Recap
A concise decision checklist
- Boot Windows installation media and choose Repair your computer > Troubleshoot > Advanced options.
- Run Startup Repair once.
- If it fails, open Command Prompt and run
diskpart,list disk,list vol, thenexit. - Confirm the Windows volume with
dir <letter>:Windows. - Identify the FAT32 SYSTEM/EFI volume and assign it a temporary letter only if needed.
- Run
bcdeditand export a backup before changes. - Run
bcdboot <OSDrive>:windows /s <SYSTEMdrive>: /f ALLwith the verified letters. - Restart, test Windows, and investigate disk detection, firmware mode or the Startup Repair log if the failure continues.
As an optional shortcut after trying the manual steps, Outbyte PC Repair can address more than 100 common Windows issues, including broken system elements and shared DLL problems, while also offering system-load tweaks, cleanup, vulnerability checks and an app-crash log. It runs on Windows 11, 10, 8 and 7; its free trial is offered by category for at least two days before a paid subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
