Phase1_Initialization_Failure BSOD - BCD, EFI partition issues?

rudolph · Jan 11, 2025

I bought a new computer a month ago with a 500GB SSD. I upgraded the storage by adding a 2TB SSD, then cloned the 500GB SSD to it. And continued to use the 2TB SSD as the main drive for booting Windows.

Everything was fine until I decided to clean up the old 500GB ssd by deleting various Windows and Program Files directories. (I didn't know they were still linked to main SSD os in some way)

That's when I couldn't resume from lock screen anymore and had to force shut down.. afterwards I started getting startup repair boot loop. Tinkered with sfc, BCD (which gave access denied error), formatted EFI fat32 system_drv partition and at the end now having PHASE1_INITIALIZATION_FAILED BSOD.

Things I tried:

I booted from Win11 installation media USB into CMD to use sfc /scannow and DISM offline repair for C: drive but it didn't work due to error 87
Used Hiren's BootCD PE macrium reflex ("Fix Windows Boot Problems") to fix boot issues and EasyBCD
Deleted EFI partition on the 2nd 500GB disk (now unallocated) to prevent OS from using it

But nothing has worked so far..

Edit:
Disk partitions from Hiren's BootCD PE:

rudolph · Jan 11, 2025

I tried running:

Code:

sfc /scannow /offlogfile=c:\scanlog.txt

But the cmd doesn't even work, it just shows sfc help.

After starting the necessary services, it shows:

Code:

X:\Windows\System32>sc config trustedinstaller start= auto
[SC] ChangeServiceConfig SUCCESS

X:\Windows\System32>net start trustedinstaller
The requested service has already been started.
More help is available by typing NET HELPMSG 2182.

X:\Windows\System32>sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Windows Resource Protection could not start the repair service.

and

Code:

PS C:\> Bcdedit /v

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-us
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {0be27235-d048-11ef-b8a7-1091d1dc2aa7}
resumeobject            {0be27234-d048-11ef-b8a7-1091d1dc2aa7}
displayorder            {0be27235-d048-11ef-b8a7-1091d1dc2aa7}
                        {0be27233-d048-11ef-b8a7-1091d1dc2aa7}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30

Windows Boot Loader
-------------------
identifier              {0be27235-d048-11ef-b8a7-1091d1dc2aa7}
device                  partition=D:
path                    \WINDOWS\system32\winload.efi
description             Windows 11
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=D:
systemroot              \WINDOWS
resumeobject            {0be27234-d048-11ef-b8a7-1091d1dc2aa7}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {0be27233-d048-11ef-b8a7-1091d1dc2aa7}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 11
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {0be27232-d048-11ef-b8a7-1091d1dc2aa7}
nx                      OptIn
bootmenupolicy          Standard

DISM:

Code:

X:\Windows\System32>DISM /Image:C:\ /Cleanup-image /Scanhealth
Deployment Image Servicing and Management tool
Version: 10.0.22621.1
Image Version: 10.0.26100.2605
Error: 87
The cleanup-image option is unknown.
For more information, refer to the help by running DISM.exe /?.
The DISM log file can be found at X:\windows\Logs\DISM\dism.log

LOG:

Code:

Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
 Info                  DISM   DISM.EXE:
 Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.22621, Running architecture=amd64, Number of processors=16
 Info                  DISM   DISM.EXE: Dism.exe version: 10.0.22621.1
 Info                  DISM   DISM.EXE: Executing command line: DISM  /Image:C:\ /Cleanup-image /Scanhealth
 Info                  DISM   DISM FFU Provider: PID=364 TID=332 [C:\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
 Info                  DISM   DISM Imaging Provider: PID=364 TID=332 The provider FfuManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
 Info                  DISM   DISM VHD Provider: PID=364 TID=332 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
 Info                  DISM   DISM Imaging Provider: PID=364 TID=332 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
[364.332] [0x80070002] FIOReadFileIntoBuffer:(1456): The system cannot find the file specified.
[364.332] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[364.332] [0xc142011c] WIMGetMountedImageHandle:(2910)
 Info                  DISM   DISM WIM Provider: PID=364 TID=332 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
 Info                  DISM   DISM Imaging Provider: PID=364 TID=332 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
 Info                  DISM   DISM Imaging Provider: PID=364 TID=332 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
[364.332] [0x80070002] FIOReadFileIntoBuffer:(1456): The system cannot find the file specified.
[364.332] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
[364.332] [0xc142011c] WIMGetMountedImageHandle:(2910)
 Info                  DISM   DISM WIM Provider: PID=364 TID=332 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
 Info                  DISM   DISM FFU Provider: PID=364 TID=332 [C:\] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
 Info                  DISM   DISM VHD Provider: PID=364 TID=332 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
 Info                  DISM   DISM Manager: PID=364 TID=332 physical location path: C:\ - CDISMManager::CreateImageSession
 Info                  DISM   DISM Manager: PID=364 TID=332 Event name for current DISM session is Global\__?_Volume{a9bfe1e0-7c1b-4580-bd13-7391f84075ce}__1254322317_65536_778455 - CDISMManager::CheckSessionAndLock
 Info                  DISM   DISM Manager: PID=364 TID=332 Create session event 0x1ec for current DISM session and event name is Global\__?_Volume{a9bfe1e0-7c1b-4580-bd13-7391f84075ce}__1254322317_65536_778455  - CDISMManager::CheckSessionAndLock
 Info                  DISM   DISM Manager: PID=364 TID=332 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
 Info                  DISM   DISM Manager: PID=364 TID=332 Successfully loaded the ImageSession at "X:\windows\TEMP\CB2E99CD-01DE-4088-AE79-0C784049890D" - CDISMManager::LoadRemoteImageSession
 Info                  DISM   DISM Image Session: PID=5616 TID=9864 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
 Info                  DISM   DISM OS Provider: PID=5616 TID=9864 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
 Info                  DISM   DISM OS Provider: PID=5616 TID=9864 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
 Warning               DISM   DISM OS Provider: PID=5616 TID=9864 Failed to bind the offline servicing stack. Make sure that the Windows directory has been set. - CDISMOSServiceManager::get_ServicingStackDirectory(hr:0x8007051a)
 Error                 DISM   DISM OS Provider: PID=5616 TID=9864 "Unable to retrieve servicing stack folder for DLL search path modification." - CDISMOSServiceManager::SetDllSearchPath(hr:0x8007051a)
 Warning               DISM   DISM OS Provider: PID=5616 TID=9864 Unable to set the DLL search path. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
 Info                  DISM   DISM Provider Store: PID=5616 TID=9864 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
 Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
 Info                  DISM   DISM Provider Store: PID=5616 TID=9864 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
 Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
 Info                  DISM   Initialized Panther logging at X:\windows\Logs\DISM\dism.log
 Info                  DISM   DISM Manager: PID=364 TID=332 Image session successfully loaded from location: X:\windows\TEMP\CB2E99CD-01DE-4088-AE79-0C784049890D - CDISMManager::CreateImageSession
 Info                  DISM   DISM OS Provider: PID=5616 TID=9864 Setting SystemPath to C:\ - CDISMOSServiceManager::SetSystemPath
 Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.26100.2605, Image architecture=amd64
 Info                  DISM   DISM.EXE: Image session version: 10.0.26100.1150
 Info                  DISM   DISM Transmog Provider: PID=5616 TID=9864 Current image session is [OFFLINE] - CTransmogManager::GetMode
 Info                  DISM   DISM OS Provider: PID=5616 TID=9864 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory
 Info                  DISM   DISM Transmog Provider: PID=5616 TID=9864 Determined WinDir path = [C:\Windows] - CTransmogManager::GetWinDirPath
 Info                  DISM   DISM Transmog Provider: PID=5616 TID=9864 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
 Info                  DISM   DISM Transmog Provider: PID=5616 TID=9864 Product Type: [WinNT] - CTransmogManager::Initialize
 Info                  DISM   DISM Transmog Provider: PID=5616 TID=9864 Product Type ServerNT : [No] - CTransmogManager::Initialize
 Error                 CSI    00000001@2025/1/11:18:41:35.337 (F) onecore\base\wcp\shim\getversion.cpp(249): Error HRESULT_FROM_WIN32(1306) originated in function Internal_SssGetImageRequiredServicingStackVersion expression: (null)
[gle=0x80004005]
 Error                 CSI    00000002 (F) HRESULT_FROM_WIN32(1306) #2# from Internal_SssGetImageRequiredServicingStackVersionFlags=0 Image={cb=00000010, flags=00000000, pcwszWindir='C:\Windows'}, Version=0.0.0.0, Disposition=0[gle=0x8007051a]
 Error                 CSI    00000003 (F) HRESULT_FROM_WIN32(1306) #1# from SssBindServicingStackParams={cb=00000040, flags=00000004, image={cb=00000010, flags=00000000, pcwszWindir='C:\Windows'}} Cookie=(inner-null), Disp=0[gle=0x8007051a]
 Warning               DISM   DISM OS Provider: PID=5616 TID=9864 Failed to bind the offline servicing stack. Make sure that the Windows directory has been set. - CDISMOSServiceManager::get_ServicingStackDirectory(hr:0x8007051a)
 Error                 DISM   DISM Driver Manager: PID=5616 TID=9864 Failed to get the servicing stack path from the os services provider. - CDriverManager::Initialize(hr:0x8007051a)
 Warning               DISM   DISM Provider Store: PID=5616 TID=9864 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x8007051a)
 Warning               DISM   DISM Provider Store: PID=5616 TID=9864 Failed to load the provider: X:\windows\TEMP\CB2E99CD-01DE-4088-AE79-0C784049890D\DmiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007051a)
 Info                  DISM   DISM Package Manager: PID=5616 TID=9864 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
 Error                 CSI    00000001@2025/1/11:18:41:35.337 (F) onecore\base\wcp\shim\getversion.cpp(249): Error HRESULT_FROM_WIN32(1306) originated in function Internal_SssGetImageRequiredServicingStackVersion expression: (null)
[gle=0x80004005]
 Error                 CSI    00000002 (F) HRESULT_FROM_WIN32(1306) #2# from Internal_SssGetImageRequiredServicingStackVersionFlags=0 Image={cb=00000010, flags=00000000, pcwszWindir='C:\Windows'}, Version=0.0.0.0, Disposition=0[gle=0x8007051a]
 Error                 CSI    00000003 (F) HRESULT_FROM_WIN32(1306) #1# from SssBindServicingStackParams={cb=00000040, flags=00000004, image={cb=00000010, flags=00000000, pcwszWindir='C:\Windows'}} Cookie=(inner-null), Disp=0[gle=0x8007051a]
 Error                 DISM   DISM Package Manager: PID=5616 TID=9864 Failed to bind to offline servicing stack of C:\Windows from C:\Windows\Temp\931876A9-FCD6-482F-A9CE-EF68EDE47B41\SsShim.dll. - CDISMPackageManager::CreateCbsSession(hr:0x8007051a)
 Error                 DISM   DISM Package Manager: PID=5616 TID=9864 Failed to create CBS session - CDISMPackageManager::RefreshInstanceAndLock(hr:0x8007051a)
 Error                 DISM   DISM Package Manager: PID=5616 TID=9864 Failed doing internal initialization - CDISMPackageManager::Initialize(hr:0x8007051a)
 Warning               DISM   DISM Provider Store: PID=5616 TID=9864 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x8007051a)
 Warning               DISM   DISM Provider Store: PID=5616 TID=9864 Failed to load the provider: X:\windows\TEMP\CB2E99CD-01DE-4088-AE79-0C784049890D\CbsProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007051a)
 Error                 DISM   DISM.EXE: No providers were found that support the command(cleanup-image). HRESULT=80070057
 Info                  DISM   DISM Manager: PID=364 TID=332 Closing session event handle 0x1ec - CDISMManager::CleanupImageSessionEntry
 Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
 Info                  DISM   DISM.EXE:
 Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->

SIW2 · Jan 11, 2025

do you have another os installed or are you reliant on boot media ?

presumably your hiren boot media is on a usb stick?

glasskuter · Jan 11, 2025

rudolph said:
Everything was fine until I decided to clean up the old 500GB ssd by deleting various Windows and Program Files directories. (I didn't know they were still linked to main SSD os in some way)

Since this laptop is new, I am assuming your drives are nvme. Is that correct?

IMO this has nothing to do with drive letters. From your screenshot, there is no data at all on the 2tb drive which indicates to me you have a clone gone wrong.
There is data on disk 1 (500 gb drive) but bcd has been removed from disk 1.
You also removed data from from the 500gb drive. Since all the original data is no longer intact, the way I see it, this makes the 500 gb drive no longer viable to re-clone.

IMO your only option is to install the 2tb drive in whichever slot the original 500 gb drive was in and clean install. (Most OEM machines have a dedicated NVME slot for the system drive.) Do not connect the second drive yet.

Once windows is installed and working you can put the original drive in the second slot. Hopefully your personal data is intact so it can be copied to the new drive. Sorry to say that all your applications will have to be clean installed.

Report back.

This is the way your disk management should look.

FreeBooter · Jan 11, 2025

Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type the below command into Command Prompt and press the Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.

Code:

Sfc  /Scannow   /OFFBOOTDIR=D:\   /OFFWINDIR=D:\Windows

Please replace partition letter D: with Windows installed partition letter. When the computer boots into Windows Recovery Environment (WinRE) environment, the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assigned any other drive letter, usually D: drive letter is assigned to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be used to find out the drive letter of the Windows installed partition, the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

SIW2 · Jan 11, 2025

the os partition on the 2tb is 1842 gb with 526gb free

You could give this a try. Extract the zip and plonk the BcdBootDiskv32x64.exe on the usb stick. You should be able to browse to the usb stick and run it from hirens when booted.

click bcdboot gui

select the os in the dropdown

click fix os letter

rudolph · Jan 11, 2025

SIW2 said:
try fixing the os letter

do you have another os installed or are you reliant on boot media ?

presumably your hiren boot media is on a usb stick?

No, I only used Win11. Yes, Hiren is on a USB stick. I also have another USB stick with Windows 11 installation media / WinRE where I can access cmd too.

glasskuter said:
Since this laptop is new, I am assuming your drives are nvme. Is that correct?

IMO this has nothing to do with drive letters. From your screenshot, there is no data at all on the 2tb drive which indicates to me you have a clone gone wrong.
There is data on disk 1 (500 gb drive) but bcd has been removed from disk 1.
You also removed data from from the 500gb drive. Since all the original data is no longer intact, the way I see it, this makes the 500 gb drive no longer viable to re-clone.

IMO your only option is to install the 2tb drive in whichever slot the original 500 gb drive was in and clean install. (Most OEM machines have a dedicated NVME slot for the system drive.) Do not connect the second drive yet.

Once windows is installed and working you can put the original drive in the second slot. Hopefully your personal data is intact so it can be copied to the new drive. Sorry to say that all your applications will have to be clean installed.

Report back.

This is the way your disk management should look.
View attachment 121768

Yes, it's nvme. I guess the screenshot is wrong then because there is data on Disk 0 - C: (2TB) and I could browse it and it's still intact. It's why I am still trying to use offline DISM but so far unsuccesfully due to error 87.

I used free tool DiskGenius to clone, btw. I guess it did clone it wrong because instead of having the parameters you have (Boot, Page file,...) in your screenshot I just have "Basic Data Partition". But it still shows as a primary drive and I was using it up until now..

SIW2 · Jan 11, 2025

did you clone or do os migration with diskgenius.

they are not the same

Try fixing the os letter as described in my previous post.

It will only say boot in diskmgmt when you are booted into it, not when viewed from another os or winpe.

zbook · Jan 11, 2025

What did startup repair srttrail.txt report?

When hard reboot is performed is there a safe mode option or error message or code?

Boot to Advanced Startup Options in Windows 10

How to Boot to Advanced Startup Options in Windows 10

www.tenforums.com

Why not backup files and clean install?

Or have Windows backup files and clean install?

What are the status of the important files:
a) there is a backup image?
b) files are backed up to another drive or to the cloud?
c) there are no backup images and files are not backed up?
d) there are no important files and a reset remove files or a clean install can be performed?

rudolph · Jan 11, 2025

FreeBooter said:
Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type the below command into Command Prompt and press the Enter key.

The following command scans integrity of all protected Windows system files and repairs files with problems when possible.

Code:

Sfc /Scannow /OFFBOOTDIR=D:\ /OFFWINDIR=D:\Windows

Please replace partition letter D: with Windows installed partition letter. When the computer boots into Windows Recovery Environment (WinRE) environment, the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assigned any other drive letter, usually D: drive letter is assigned to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be used to find out the drive letter of the Windows installed partition, the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

I ran from Win11 installation media USB cmd: "Sfc /Scannow /OFFBOOTDIR=C:\ /OFFWINDIR=C:\Windows"
But I got this error:
"Windows resource protection could not perform the requested operation"
and - "Windows resource protection could not start the repair service".

Then I started the service net start trustedinstaller, ran sfc again and got the same error. During boot up from boot device "Windows Boot Manager (CT2000T500SSD5)" it shows error code 0xc0000001

SIW2 said:
the os partition on the 2tb is 1842 gb with 526gb free

You could give this a try. Extract the zip and plonk the BcdBootDiskv32x64.exe on the usb stick. You should be able to browse to the usb stick and run it from hirens when booted.

click bcdboot gui

View attachment 121769

select the os in the dropdown

View attachment 121770

click fix os letter

View attachment 121771

Did that. Showed that "The operation completed succesfully" and "C:\Windows os letter C: set to 444D4....."
After shut down and booting up from 2TB C: drive, boot device: "Windows Boot Manager (CT2000T500SSD5)" still getting the same BSOD - PHASE1_INITIALIZATION_FAILED.

SIW2 said:
did you clone or do os migration with diskgenius.

they are not the same

Try fixing the os letter as described in my previous post.

View attachment 121774

It will only say boot in diskmgmt when you are booted into it, not when viewed from another os or winpe.

I don't remember anymore. Most likely I just cloned the entire drive possibly and didn't migrate the OS..

zbook said:
What did startup repair srttrail.txt report?

When hard reboot is performed is there a safe mode option or error message or code?

Boot to Advanced Startup Options in Windows 10

How to Boot to Advanced Startup Options in Windows 10

www.tenforums.com

Why not backup files and clean install?

Or have Windows backup files and clean install?

What are the status of the important files:
a) there is a backup image?
b) files are backed up to another drive or to the cloud?
c) there are no backup images and files are not backed up?
d) there are no important files and a reset remove files or a clean install can be performed?

No, I can't enter safe mode at all when booting from C:\ drive, it shows PHASE1_INITIALIZATION_FAILED, only can access UEFI/BIOS or recovery options menu from USB stick Win11 media.
Here is the srttrail.txt contents:

Code:

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎1/‎2/‎2025 3:36:28 PM (GMT)
Number of repair attempts: 20

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 0

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 125 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 47 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 32 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Check for installed LCU
Result: Completed successfully. Error code =  0x51a
Time taken = 1047 ms

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 203 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 1250 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 204 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Root cause found:
---------------------------
Startup Repair has tried several times but still cannot determine the cause of the problem.

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 187 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 1250 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 16 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 188 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Root cause found:
---------------------------
Startup Repair has tried several times but still cannot determine the cause of the problem.

Backing up important programs, their config data, AppData and transferring files and setting it all up as it was takes A LOT of time and effort...

glasskuter · Jan 11, 2025

I stand corrected on my post #4. I was looking at the wrong drive in disk management. Sorry for my mistake. Do as @SIW2 suggested. It can easily be done without any 3rd party software. Boot from windows install usb drive instead and use bootrec tool to build bcd. It takes entering only 3 commands.
Make sure the 2tb drive is in the same nvme slot that was used from the factory. Disconnect the 500gb drive until you have a bootable windows.

Use method #3 here https://www.ventoy.net/en/experience_rebuildBCD.html

aubergine · Jan 11, 2025

glasskuter said:
Use method #3 here Ventoy

Instead of the BOOTREC /REBUILDBCD command, use the BCDBOOT C:\WINDOWS command.

How to use BCDBOOT to recreate the EFI system partition files. Post #17

MBR Windows 10 > to UEFI only computer - Windows 10 Help Forums

Hi everyone, I've tried diff approaches but can't find the solution. Source computer: my daily driver, has both UEFI and legacy compatibility. Because of personal preference I installed Windows 10 Pro in legacy / MBR mode using one single partition, becau

www.tenforums.com

SIW2 · Jan 11, 2025

did you delete the documents and settings link from the source disk ?

zbook · Jan 11, 2025

rudolph said:
Things I tried:

Used Hiren's BootCD PE macrium reflex ("Fix Windows Boot Problems") to fix boot issues and EasyBCD

But nothing has worked so far..

What were the error messages or codes?

Boot to Windows Recovery Environment (RE) and type:

Code:

bcdedit /enum
bcdedit | find "osdevice"

Code:

diskpart
lis dis
lis vol
sel dis 0
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par
sel dis 1
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par

rudolph · Jan 12, 2025

I managed to run DISM from win11 installation media USB by mounting it on C drive, only then I could run cleanup-image and restorehealth without error 87.

Code:

mkdir c:\offline
dism.exe /mount-wim /wimfile:f:\sources\install.esd /index:1 /mountdir:c:\offline

Now the /cleanup-image and /restorehealth didn't show error 87 for me anymore.

Code:

DISM.exe /image:c:\offline /cleanup-image /restorehealth

Shows that repair was successful, but still doesn't boot.

glasskuter said:
I stand corrected on my post #4. I was looking at the wrong drive in disk management. Sorry for my mistake. Do as @SIW2 suggested. It can easily be done without any 3rd party software. Boot from windows install usb drive instead and use bootrec tool to build bcd. It takes entering only 3 commands.
Make sure the 2tb drive is in the same nvme slot that was used from the factory. Disconnect the 500gb drive until you have a bootable windows.

Use method #3 here Ventoy

I disassembled my laptop and checked. The newly installed 2TB SSD was in the slot where the original factory SSD was installed.
I disconnected the 500GB SSD and booted into USB Win11 installation media cmd

Ran these commands:

BOOTREC /SCANOS - Found Windows installations in "[1] C:\offline\Windows"
BOOTREC /FIXMBR - "The operation completed successfully"
BOOTREC /FIXBOOT - "Access is denied."
BOOTREC /REBUILDBCD - Found 1 installations: Added "[1] C:\offline\Windows" to boot list -> "The system cannot ind the path specified"

aubergine said:
BCDBOOT C:\WINDOWS

Shows "Boot files successfully created". But the same BSOD still persists: "PHASE1_INITIALIZATION_FAILED"

rudolph · Jan 12, 2025

zbook said:
What were the error messages or codes?

Boot to Windows Recovery Environment (RE) and type:

Code:

bcdedit /enum bcdedit | find "osdevice"

Code:

diskpart lis dis lis vol sel dis 0 det dis lis par sel par 1 det par sel par 2 det par sel par 3 det par sel par 4 det par sel dis 1 det dis lis par sel par 1 det par sel par 2 det par sel par 3 det par sel par 4 det par

Code:

X:\Windows\System32>bcdedit /enum

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
resumeobject            {9d11f283-d10b-11ef-a9ed-aa4b34428ac5}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 11
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {9d11f283-d10b-11ef-a9ed-aa4b34428ac5}
nx                      OptIn
bootmenupolicy          Standard

Code:

X:\Windows\System32>bcdedit | find "osdevice"

osdevice                partition=C:

DISKPART commands:

Code:

X:\Windows\System32>diskpart
Microsoft DiskPart version 10.0.22621.1
Copyright (C) Microsoft Corporation.
On computer: HBCD_PE

DISKPART> lis dis

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online         1863 GB    18 GB        *
  Disk 1    Online          476 GB   260 MB        *
  Disk 2    Online          894 GB   862 GB
  Disk 3    Online         1907 MB  1792 KB
  Disk 4    Online          115 GB      0 B        *
  Disk 5    Online           14 GB      0 B

DISKPART> lis vol

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C   Windows-SSD  NTFS   Partition   1842 GB  Healthy
  Volume 1         SYSTEM_DRV   FAT32  Partition    260 MB  Healthy    Hidden
  Volume 2         WINRE_DRV    NTFS   Partition   2000 MB  Healthy    Hidden
  Volume 3     D   SSD2         NTFS   Partition    474 GB  Healthy
  Volume 4         WINRE_DRV    NTFS   Partition   2000 MB  Healthy    Hidden
  Volume 5     E   ESD-USB      FAT32  Partition     32 GB  Healthy
  Volume 6     F   SANDISK      FAT32  Removable   1906 MB  Healthy
  Volume 7     Y   HBCD_PE_X64  FAT32  Removable    115 GB  Healthy
  Volume 8     H   ESD-USB      FAT32  Removable     14 GB  Healthy

DISKPART> sel dis 0
Disk 0 is now the selected disk.
DISKPART> det dis

CT2000T500SSD5
Disk ID: {4A14B768-BA34-11EF-AF2E-1091D1DC2AA3}
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0600)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C   Windows-SSD  NTFS   Partition   1842 GB  Healthy
  Volume 1         SYSTEM_DRV   FAT32  Partition    260 MB  Healthy    Hidden
  Volume 2         WINRE_DRV    NTFS   Partition   2000 MB  Healthy    Hidden

DISKPART> lis par

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    System             260 MB  1024 KB
  Partition 2    Reserved            16 MB   261 MB
  Partition 3    Recovery          2000 MB   277 MB
  Partition 4    Primary           1842 GB  2277 MB

DISKPART> sel par 1
Partition 1 is now the selected partition.

DISKPART> det par

Partition 1
Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden  : Yes
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 1048576

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 1         SYSTEM_DRV   FAT32  Partition    260 MB  Healthy    Hidden

DISKPART> sel par 2
Partition 2 is now the selected partition.

DISKPART> det par

Partition 2
Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden  : Yes
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 273678336

There is no volume associated with this partition.

DISKPART> sel par 3
Partition 3 is now the selected partition.

DISKPART> det par

Partition 3
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : Yes
Required: Yes
Attrib  : 0X8000000000000001
Offset in Bytes: 290455552

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 2         WINRE_DRV    NTFS   Partition   2000 MB  Healthy    Hidden

DISKPART> sel par 4
Partition 4 is now the selected partition.

DISKPART> det par

Partition 4
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 2387607552

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 0     C   Windows-SSD  NTFS   Partition   1842 GB  Healthy

DISKPART> sel dis 1
Disk 1 is now the selected disk.

DISKPART> det dis

Micron MTFDKCD512QFM-1BD1AABLA
Disk ID: {5AABCC47-2EA4-4594-9FD0-484B1A8AE2E5}
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1A00)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 3     D   SSD2         NTFS   Partition    474 GB  Healthy
  Volume 4         WINRE_DRV    NTFS   Partition   2000 MB  Healthy    Hidden

DISKPART> lis par

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Reserved            16 MB   261 MB
  Partition 2    Primary            474 GB   277 MB
  Partition 3    Recovery          2000 MB   474 GB

DISKPART> sel par 1
Partition 1 is now the selected partition.

DISKPART> det par

Partition 1
Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden  : Yes
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 273678336

There is no volume associated with this partition.

DISKPART> sel par 2
Partition 2 is now the selected partition.

DISKPART> det par

Partition 2
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 290455552

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3     D   SSD2         NTFS   Partition    474 GB  Healthy

DISKPART> sel par 3
Partition 3 is now the selected partition.

DISKPART> det par

Partition 3
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : Yes
Required: Yes
Attrib  : 0X8000000000000001
Offset in Bytes: 510012686336

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 4         WINRE_DRV    NTFS   Partition   2000 MB  Healthy    Hidden

DISKPART> sel par 4

The specified partition is not valid.
Please select a valid partition.

There is no partition selected.

DISKPART> det par

There is no partition selected.
Please select a partition and try again.

zbook · Jan 12, 2025

How come this was skipped: bcdedit | find "osdevice"

rudolph · Jan 12, 2025

zbook said:
How come this was skipped: bcdedit | find "osdevice"

I edited it. But showed basically C: drive:

Code:

X:\Windows\System32>bcdedit | find "osdevice"

osdevice                partition=C:

zbook · Jan 12, 2025

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

aubergine · Jan 12, 2025

rudolph said:
Ran these commands:

BOOTREC /SCANOS - Found Windows installations in "[1] C:\offline\Windows"

BOOTREC /FIXMBR - "The operation completed successfully"

BOOTREC /FIXBOOT - "Access is denied."

BOOTREC /REBUILDBCD - Found 1 installations: Added "[1] C:\offline\Windows" to boot list -> "The system cannot ind the path specified"

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.

rudolph said:
Shows "Boot files successfully created". But the same BSOD still persists: "PHASE1_INITIALIZATION_FAILED"

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

Phase1_Initialization_Failure BSOD - BCD, EFI partition issues?

New member

My Computer

New member

My Computer

Well-known member

My Computers

aka Mama Glass

My Computers

Well-known member

My Computer

Well-known member

Attachments

My Computers

New member

My Computer

Well-known member

My Computers

Well-known member

My Computer

New member

My Computer

aka Mama Glass

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

New member

My Computer

New member

My Computer

Well-known member

My Computer

New member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Similar threads