Please boot into Windows.
Post the latest Disk Management screenshot.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I'm currently running Windows 11 Pro 23H2 (22631.6199), and I've had problems updating to 24/25H2. I've tried updating from the windows updater, as well as from the bootable media. I currently get the following error:
0xC1900101 - 0x20017The installation failed in the SAFE_OS phase with an error during BOOT operation.
I've exhausted virtually all solutions that I've found online, including the following:
sfc /scannowDISM /Online /Cleanup-Image /RestoreHealthWhile attempting these, there were a few references to reagentc - disabling and re-enabling it. This is where I noticed a problem, and I believe it's what's blocking the update.
Running reagentc /info shows it as disabled:
Attempting to enable it says that it's successful, but it's still disabled.
I've tried replacing the winre.wim file and the reagent.xml file from the update image (adding them to C:\Windows\System32\Recovery) - and enabling after that does remove the files - but everything still shows as disabled.
I then recalled that I actually cloned my old windows drive to the current SSD its on - and noticed that I had 2 recovery partitions, and 2 system partitions. After a lot of experimenting, I deleted both recovery partitions and recreated a single recovery partition - but that still did not work:
I'm honestly at my wits end with this, and would appreciate any help. Running reagentc /enable is doing something, but I've no idea what windows thinks my recovery partition is, or why it isn't enabling. Any advice or assistance is greatly appreciated.
Please boot into Windows.
Post the latest Disk Management screenshot.
No wonder you were unable to enable WinRE. The problem here is the system is booting from the System Reserved partition instead of the EFI partition.
Please boot into Windows RE using the Windows 11 USB setup disk. We have to fix the boot partitions.
In WinRE Command Prompt, type the following commands:
diskpart
select disk 1
list part
list vol
Exit
Take a photo of the output screen and upload the image(s) here.
Don't quit WinRE yet. Some more commands need to be run.
Hi,
The 0xC1900101 - 0x20017 error is not related to the WinRE issue.
From Upgrade resolution procedures - Windows Client | Microsoft Learn
| 0xC1900101 - 0x20017 | Ensure that all that drivers are updated. Open the Setuperr.log and Setupact.log files in the %windir%\Panther directory, and then locate the problem drivers. For more information, see Windows Vista, Windows 7, Windows Server 2008 R2, Windows 8.1, and Windows 10 setup log file locations. Update or uninstall the problem drivers. | A driver has caused an illegal operation. Windows wasn't able to migrate the driver, resulting in a rollback of the operating system. This is a SafeOS boot failure, typically caused by drivers or non-Microsoft disk encryption software. This can also be caused by a hardware failure. |
|---|
Please share your Farbar scan logs for analysis.- Download Farbar Recovery Scan Tool 64-bit FRST64.exe
FRST64.exe to FRST64English.exe.Note: If Microsoft Edge or Chrome mislabels the Farbar Scanner executable as PUA/malware, choose to keep it by tapping … in the bottom bar, choosing Keep, and then choosing Keep anyway in the dialog that appears. See this screenshot. It's a safe tool used in most antimalware forums.