[SOLVED] Windows 10 Pro boot error. FIX: I Ended up reinstalling.

eprst · May 22, 2023

Hi

I've got a Windows 10 Pro installation which suddenly fails to boot, safe mode and startup recovery don't help.

SrtTrail.txt says:

Code:

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

Root cause found:
---------------------------
Boot manager failed to find OS loader.

Repair action: File repair
Result: Failed. Error code =  0x57
Time taken = 13188 ms

Repair action: Boot configuration data store repair
Result: Failed. Error code =  0x490
Time taken = 15 ms

chkdsk is not finding any errors or bad blocks, though I suspect this could be something with my ssd/cable, as I had some strange (repairable) disk problems before.

Attempt to use a restore point fails with 0x80070057

Now 2 questions:
1. Is it salvageable?
2. Does it make sense to get a new drive+cable, clone the content (eg via dd from Linux), and then attempt a repair there?

Thanks

xilolee · May 23, 2023

Hi!

NOTE: The following procedure is only valid if you are using UEFI/GPT-based hard drive partitions!!!
You should find an asterisk under the GPT column, when using the diskpart - list disk - command (i.e., the first command after you entered diskpart).
If the disk(s) is not GPT, DON'T PROCEED.

Start your pc and select command prompt.
From the usual blue screen, it should be in troubleshoot, click advanced options, click command prompt, click restart.
The computer will restart (in safe mode with command prompt).
Press enter after each command:

diskpart
list disk
select disk 0

Read More:

If you have only one disk, it's usually disk 0.
If you have more than one disk, choose the one with windows... If you know which is it.
If you don't know it, you will know it after the next two commands.
list partition
list volume

Read More:

Now that you can see the partitions, the volumes and their labels, you should be able to identify if this disk is the windows disk.
If it's not, you will type the command: select disk 1.
Then list again partitions and volumes!
either
select partition [your ESP partition number]
or
select volume [your ESP volume number]

Read More:

Here you must select the ESP partition.
But you can also select the ESP volume, instead.
The ESP is usually the second partition, i.e. partition 2.
Its type is system.
You can compare its size with the volumes, after the "list volume" command.
You will find your ESP volume, maybe with the ESP label.
Its file system, under the column FS, is fat32.
Under the info column, you should find system (again).
assign letter = z
exit
From the (previous) list volume command in diskpart, you should be able to identify the windows volume letter.
In my case, it was D:.
Then, I changed volume with d:

Verify that the selected volume is the windows volume with dir.

Read More:

Change volume: z:

Verify that the selected volume is the ESP volume with dir.

Read More:

Change volume: x:
Now this is the command that should fix your os loader: bcdboot d:\windows /s Z: /f UEFI /v
d:\windows is the location of my windows root.
You MUST use YOUR windows letter!
z: is the ESP partition.

Full example:

Read More:

Code:

X:\windows\system32>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: XILOLEE

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          232 GB  1024 KB        *
  Disk 1    Online          465 GB      0 B        *

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list partition

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery           400 MB  1024 KB
  Partition 2    System             299 MB   401 MB
  Partition 3    Reserved           128 MB   701 MB
  Partition 4    Primary             99 GB   829 MB
  Partition 5    Recovery           531 MB   100 GB
  Partition 6    Primary            132 GB   100 GB

DISKPART> list volume

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     I                       DVD-ROM         0 B  No Media
  Volume 1     C   FREE         NTFS   Partition    400 MB  Healthy    Hidden
  Volume 2     D   WINDOWS      NTFS   Partition     99 GB  Healthy    Boot
  Volume 3     J   RECOVERY     NTFS   Partition    531 MB  Healthy    Hidden
  Volume 4     E   DATA         NTFS   Partition    132 GB  Healthy    Pagefile
  Volume 5         ESP          FAT32  Partition    299 MB  Healthy    System
  Volume 6     F   DATA         NTFS   Partition     75 GB  Healthy    Pagefile
  Volume 7     G   DATA         NTFS   Partition    139 GB  Healthy    Pagefile
  Volume 8     H   DATA         NTFS   Partition    250 GB  Healthy    Pagefile

DISKPART> select partition 2

Partition 2 is now the selected partition.

DISKPART> assign letter = z

DiskPart successfully assigned the drive letter or mount point.

DISKPART> exit

Leaving DiskPart...

X:\windows\system32>d:

D:\>dir
 Volume in drive D is WINDOWS
 Volume Serial Number is DDB1-9240

 Directory of D:\

09/06/2020  00:53            32,768 attuale
19/09/2018  08:26    <DIR>          boot
07/12/2019  11:14    <DIR>          PerfLogs
30/04/2023  20:01    <DIR>          Program Files
28/04/2023  21:35    <DIR>          Program Files (x86)
16/03/2023  00:09    <DIR>          Users
21/05/2023  08:19    <DIR>          Windows
               1 File(s)         32,768 bytes
               6 Dir(s)  74,754,617,344 bytes free

D:\>z:

Z:\>dir
 Volume in drive Z is ESP
 Volume Serial Number is AEBA-DEE0

 Directory of Z:\

11/11/2017  19:13    <DIR>          EFI
18/01/2018  03:25    <DIR>          Temp
               0 File(s)              0 bytes
               2 Dir(s)     285,255,680 bytes free

Z:\>x:

x:\windows\system32>bcdboot d:\windows /s Z: /f UEFI /v

eprst · May 27, 2023

bcdboot complained about corrupted Windows/Boot/EFI/bootmgfw.efi, so I copied it from X:, after this bcdboot succeeded. But normal windows boot then kept complaining about corrupted Boot/winload.efi and System32/ntoskrnl.exe, so I copied them too.
Now boot fails with error 0xc000007b.
Booting from installation media and attempting a recovery simply reboots again.
I tried running offline sfc, but it says there's a pending system repair.
I then tried dism /image:c:\ /revertpendingactions, but it fails with error 1812. Attempt to do an image repair with dism fails with the same error code.
Any other ideas?
Thanks

xilolee · May 27, 2023

And what does strtrail.txt show this time?

eprst · May 27, 2023

Last session:

Code:

---------------------------
---------------------------
Session details
---------------------------
System Disk = \Device\Harddisk1
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 = 94 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 = 46 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 63 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 =  0x714
Time taken = 1047 ms

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

xilolee · May 27, 2023

Are you using a Windows installation media downloaded in these last days for the recovery steps?

eprst · May 27, 2023

I tried to use freshly downloaded Windows 10 Pro MSDN ISO, written to usb drive with WoeUSB

xilolee · May 29, 2023

Did you try a repair install?

eprst · May 29, 2023

Yes, it refuses to do that from USB, says I have to boot windows normally and run setup from there. Or is there some other way?

xilolee · May 29, 2023

eprst said:
Yes, it refuses to do that from USB, says I have to boot windows normally and run setup from there. Or is there some other way?

Yeah, I forgot that works when windows still works somewhat...

xilolee · May 29, 2023

Give your PC a Fresh Start - Microsoft Support

By the way, don't you have another PC where you can connect that drive and then copy the data?

eprst · May 29, 2023

I have plenty of ways to copy the data, I was just hoping there's a way to fix that instance so I won't have to reinstall/reconfigure everything. Looks like will have to bite the bullet

xilolee · May 29, 2023

Then you could try the fresh start, that is quite similar to a repair install.
Read the notes and save what they tell won't be saved.

eprst · May 29, 2023

I'm sorry, but it looks like it requires a working windows?
To reset your PC, go to [B]Start [/B] > [B]Settings [/B] > [B]Update & Security...[/B]

xilolee · May 29, 2023

It should be reachable from the Windows 10 advanced startup options: troubleshoot, reset.

eprst · Jun 7, 2023

Ended up reinstalling.. thanks for your help! topic can be closed.

[SOLVED] Windows 10 Pro boot error. FIX: I Ended up reinstalling.

eprst

Well-known member

xilolee

Moderator

eprst

Well-known member

xilolee

Moderator

eprst

Well-known member

xilolee

Moderator

eprst

Well-known member

xilolee

Moderator

eprst

Well-known member

xilolee

Moderator

xilolee

Moderator

eprst

Well-known member

xilolee

Moderator

eprst

Well-known member

xilolee

Moderator

eprst

Well-known member