Phase1_Initialization_Failure BSOD - BCD, EFI partition issues?

When using Command Prompt to fix boot-related issues, it is common to face the “bootrec /fixboot Access is denied” error. There are many possible reasons for this problem to occur on your computer. In this video, i will help you troubleshoot this error.

zbook said:

Looked multiple times for your reply earlier in the day.
It's 2:19 am here so I'm heading to bed.


There were 6 disks.

Which was the new cloned drive?

Which was the drive in which the clone was made from?

What was done to the drive in which the clone was made from?



Report what was done to each partition of each drive.






Disk 0: CT2000T500SSD5

Disk 1: Micron MTFDKCD512QFM-1BD1AABLA

Disk 2 Online 894 GB 862 GB<br>
Disk 3 Online 1907 MB 1792 KB<br>
Disk 4 Online 115 GB 0 B *<br>
Disk 5 Online 14 GB 0 B

Click to expand...

Disk 0 is the new cloned disk (C:/). Disk 1 is the original factory SSD from which the clone was made.
I deleted everything inside Disk 1 since I already transferred all files to Disk 0 after clone.

On Disk 0 after having startup repair boot loop and error code of phase1 i figured based on the internet info that I have issues with boot configuration, so that's when I ran several commands to reformat EFI partition and recreate boot files but without any success.

aubergine said:

Do not use the following commands.

bootrec /fixmbr
bootrec /fixboot x)
bootrec /scanos
bootrec /rebuildbcd

That's all outdated stuff not used on UEFI/GPT based systems.

x) This command has been blocked by Microsoft: "Access is denied" - Windows 10 version 1709 (October 17, 2017) and newer installation media. And Windows 11 installation media.



Try the commands below.

diskpart
list volume (check your EFI system partition number)
select volume # (replace # with the EFI system partition number)
format quick fs=fat32 (optional: format your EFI system partition)
assign letter=z
list volume (check the volume letter of your Windows partition)
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

View attachment 121828

Click to expand...

I formatted the EFI partition on the main C: disk, assigned letter Z, ran command:

bcdboot C:\windows /s Z: /f UEFI

Booted from C: disk, but without any success. The same "Your PC couldn't start properly" screen with error code 0xc0000001

FreeBooter said:

When using Command Prompt to fix boot-related issues, it is common to face the “bootrec /fixboot Access is denied” error. There are many possible reasons for this problem to occur on your computer. In this video, i will help you troubleshoot this error.

Click to expand...

Aubergine above said that this command isn't being used anymore on UEFI ?

I've tried it already before. I tried it again, but now bootsect /nt60 sys doesn't show any partitions at all (previously it did).




Currently backing up all the files and program appdata. I think clean install is the only way at this point since it's impossible to diagnose what is the cause and what problem exactly is occuring.

FreeBooter said:

When using Command Prompt to fix boot-related issues, it is common to face the “bootrec /fixboot Access is denied” error. There are many possible reasons for this problem to occur on your computer. In this video, i will help you troubleshoot this error.

Click to expand...

bootrec /fixboot ===> Access is denied.

It's not an error message, it just means that the command has been blocked. Both with Windows 10 (from version 1709) and Windows 11 installation media.

My new laptop has the same "problem" (image below).

These are some trial and error steps:

a) boot windows RE > Type:

bootsect /nt60 all
shrink querymax
reg query "HKLM\System\CurrentControlSet\Control /v PEFirmwareType"

> post a share link > reboot > post new error message or code


b) perform a new startup repair > post a srttrail.txt


c) boot to BIOS > alternate reboots with IDE and AHCI > post new error messages or codes


d) reset the BIOS (remove and reseat the CMOS battery) > post new error message or code


e) repeat Macrium boot repair