Windows 10 unable to boot in random moments

Hello good people, back in 2020 I assembled my socket am4 pc.
Since then (and I changed all the pc components but still using the socket am4 machine) I had random boot failures.
I thought it was because when I installed the os I wanted my raid 1 configuration (other than the nvme ssd) to be visible during the installation (which is not if I do not install any amd supplemental drivers).

Some days ago I received a new nvme ssd, I installed it and switched the older one to the slower m2 slot.
Installed windows 10 ltsc and then I was doing back and fort to move the stuff from the old nvme to the new one, when suddenly the old ssd didn't want to boot anymore, despite it was working fine a minute before, when this doesn't work and I am able to boot into RE environment the only visible drive is the raid1 (despite the winre is in the ssd).

The current version of windows 10 malfunctioning is: 22H2 build 19045.4170.

To fix the issue i'm trying to do an inplace reinstallation which always fails due to the winre partition being unavailable (according to the setup). I followed multiple guides and even if I give the command: ReAgentC /Enable I receive a successful message, it keeps being disable when I give the command ReAgentC /info:

Code:

Informazioni di configurazione per Ambiente ripristino Windows
e la reimpostazione del sistema:

    Stato Ambiente ripristino Windows:      Disabled
    Percorso Ambiente ripristino Windows:
    Identificatore dati di configurazione di avvio (BCD): 00000000-0000-0000-0000-000000000000
    Percorso immagine di ripristino:
    Indice immagine di ripristino:          0
    Percorso immagine personalizzata:
    Indice immagine personalizzata:         0

REAGENTC.EXE: operazione riuscita.

That's the situation of the first hard drive according to diskpart:

Code:

  Volume ###  Let. Etichetta    Fs     Tipo        Dim.     Stato      Info
  ---------   ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     E                       DVD-ROM         0 b  Nessun su
  Volume 1     C   Windows 10   NTFS   Partizione   952 Gb  Integro    Sistema
  Volume 2                      FAT32  Partizione   100 Mb  Integro    Nascosto
  Volume 3         Windows RE   NTFS   Partizione  1001 Mb  Integro    Nascosto
  Volume 4     D                NTFS   Partizione  7451 Gb  Integro
  Volume 5     G   ESD-USB      FAT32  Rimovibile    29 Gb  Integro

list par:

Code:

DISKPART> list par

  Partizione ###   Tipo              Dim.     Offset
  ---------------  ----------------  -------  -------
  Partizione 1    Sistema            100 Mb  1088 Kb
  Partizione 2    Riservato           16 Mb   102 Mb
  Partizione 3    Primario           952 Gb   118 Mb
  Partizione 4    Ripristino        1001 Mb   952 Gb

That's a screen of disk management:
Imgur: The magic of the Internet

When I try to do the inplace reinstall it ends with the error: 0xC1900101 – 0x20017, Installation failed in SAFE_OS phase with an error during BOOT operation.

I'm sorry but i'm unsure of what logs so I used the Upgrade_failure_info.bat.
The compressed file is over 60mb! I shared it on my google drive: Upgrade_failure_logs_2024-03-30_19-02-27.zip - Google Drive

Thank you in advance for any help.

Berton said:

There can be issues with booting to a RAID configuration, I did it several years ago. My motherboard BIOS had a setting for AHCI/RAID [yes, combined] or Legacy. I chose AHCI/RAID and installed good. I did not pay attention to having a second HDD connected to the board and Windows automatically installed as RAID 1. Later on I removed the second drive and broke the process, required reinstall Windows. Late last year I was given a Dell Precision XEON CPU with 2 x 500GB drives, one was bad, removed the bad one and same thing, had to change to AHCI with only one drive connected and install Win10, it is now my main Win10 machine.

Thank you for the asnwer.
Do you mean that the raid settings can give issue on boot phase? Because I'm pretty sure I can't have the mixed setting raid\ahci.
That being said I'm not booting to RAID 1, which I just use as a storage.
I can say that in the new installation the raid wasn't visible until I installed the chipset driver. I can say for sure that intel raid wasn't so problematic (the raid is also not visible on linux, I tried gparted).

I have absolutely no idea what your intention is, what you did and your problem description is horrible.
On Home Computers the Raid possibilities are very limited. Professional Workstations have a separate RAID Controller with the option to configure the arrays.
Now you are on the best way to ruin your NVRAM. bcdedit /enum firmware allows you to delete dublicate entries.

Pentagon said:

I have absolutely no idea what your intention is, what you did and your problem description is horrible.
On Home Computers the Raid possibilities are very limited. Professional Workstations have a separate RAID Controller with the option to configure the arrays.
Now you are on the best way to ruin your NVRAM. bcdedit /enum firmware allows you to delete dublicate entries.

The information about raid were given because I thought the forced driver installation was the "main issue". I won't delete my raid1 and use third applications, as much as people can think is better... That being said, I've been able to rebuild bcd with bcdedit, now I'm down to two boot devices (which still doesn't make any sense to me?).
That's the output of bcdedit /enum firmware:

Code:

Boot Manager per firmware
---------------------
identificatore          {fwbootmgr}
displayorder            {4a713f9e-ef2f-11ee-b80c-833d98dc321f}
                        {bootmgr}
timeout                 1

Windows Boot Manager
--------------------
identificatore          {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager
locale                  it-IT
default                 {default}
displayorder            {default}
timeout                 30

Applicazione firmware (101fffff)
-------------------------------
identificatore          {4a713f9e-ef2f-11ee-b80c-833d98dc321f}
device                  partition=C:
path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description             Windows Boot Manager

Then, according to my first post, I'd like to sanitize the windows installation, being able to boot both m2 drives (old installation or new installation, different ssds), while now the old installation refuse to boot when the other ssd is installed , I pasted a link of log files of the failed inplace reinstall on my first post, other than reagentc unable to properly enable despite command output gives success.

That's the actual log of the volumes on the current installation:

Code:

DISKPART> sel disk 0

Il disco attualmente selezionato è il disco 0.


DISKPART> list vol

  Volume ###  Let. Etichetta    Fs     Tipo        Dim.     Stato      Info
  ---------   ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     E                       DVD-ROM         0 b  Nessun su
  Volume 1     C   Windows 10   NTFS   Partizione   952 Gb  Integro    Sistema
  Volume 2         EFI          FAT32  Partizione   100 Mb  Integro    Nascosto
  Volume 3         Windows RE   NTFS   Partizione  1001 Mb  Integro    Nascosto
  Volume 4     D                NTFS   Partizione  7451 Gb  Integro

Apparently windows still use c: instead of the efi partition in boot manager.
Thanks.

bcdedit /delete {4a713f9e-ef2f-11ee-b80c-833d98dc321f} /cleanup

reboot
bcdboot X:\Windows
replace X by the right letter after reboot

Pentagon said:

bcdedit /delete {4a713f9e-ef2f-11ee-b80c-833d98dc321f} /cleanup

reboot
bcdboot X:\Windows
replace X by the right letter after reboot

Done, here is the output of bcdedit /enum firmware:

Code:

C:\windows\system32>bcdedit /enum firmware

Boot Manager per firmware
---------------------
identificatore          {fwbootmgr}
displayorder            {bootmgr}
                        {43b11d56-ef2c-11ee-ab49-806e6f6e6963}
timeout                 1

Windows Boot Manager
--------------------
identificatore          {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
resumeobject            {4a713fa3-ef2f-11ee-b80c-833d98dc321f}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Applicazione firmware (101fffff)
-------------------------------
identificatore          {43b11d56-ef2c-11ee-ab49-806e6f6e6963}
device                  partition=C:
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager

C:\windows\system32>

Still 2 voices are visible:
Imgur: The magic of the Internet