This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 40%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMK%3C/text%3E%3C/svg%3E)
Windows 11 Pro 23H2 cannot be upgraded to Windows 11 25H2.
The upgrade consistently fails with:
0xC1900101-0x40017
"The installation failed in the SECOND_BOOT phase with an error during BOOT operation."
The installation reaches approximately 75%, reboots, attempts to start the new version and then rolls back to Windows 11 23H2.
The same failure occurs:
Troubleshooting already performed:
Removed for testing:
The error remained unchanged.
Storage configuration:
Logs reviewed:
Notable findings:
Has anyone seen this exact upgrade failure or identified the root cause of 0xC1900101-0x40017 during SECOND_BOOT?Windows 11 Pro 23H2 cannot be upgraded to Windows 11 25H2.
The upgrade consistently fails with:
0xC1900101-0x40017
"The installation failed in the SECOND_BOOT phase with an error during BOOT operation."
The installation reaches approximately 75%, reboots, attempts to start the new version and then rolls back to Windows 11 23H2.
The same failure occurs:
Troubleshooting already performed:
Removed for testing:
The error remained unchanged.
Storage configuration:
Logs reviewed:
Notable findings:
Has anyone seen this exact upgrade failure or identified the root cause of 0xC1900101-0x40017 during SECOND_BOOT? <PII removed>
Winsock catalog appears clean and contains only standard Microsoft providers. Driver Store contains several third-party driver packages, including Creative Sound Blaster drivers (2020 and 2022), Realtek audio packages (2021 and 2026), Intel Bluetooth packages from multiple years, Logitech drivers, Honor phone drivers, and TAP-Windows Provider V9 (OpenVPN) driver package from 2019. Please advise which packages are relevant to investigate for 0xC1900101-0x40017 SECOND_BOOT rollback. drivers.txt
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 72%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECL%3C/text%3E%3C/svg%3E)
Hello Mario Kermiet,
Sorry but the 2 attachments you sent cannot be found, can you please send them again?
I'm waiting for your reply.
Hello Mario Kermiet,
Thanks for replying.
It will take a while to check all of this. I'll see what I can find. I'll keep you updated.
Answer accepted by question author
Hello Mario Kermiet,
Welcome to Microsoft Q&A forum.
Before we proceed further, I'd like to do a few simple tests to better understand the situation.
I'm waiting for your reply.
Please run the fixlist below.
Fixlist.txt to the same folder as FRST64English.exe.NOTE: The fixlist.txt script was written specifically for this user and for use on that particular machine. It is not recommended to run it on another machine, and don't run the same fixlist.txt more than once.
The fixlist removes some old drivers, runs a drivers assessment, and refreshes the compatibility assessment.
The fix has been completed successfully. FixLog.txt is attached.
Please let me know if you would like me to attempt the Windows 11 25H2 upgrade now, or if you would like to review the FixLog first.Fixlog.txt
It ran fine. Please upgrade to 25H2 now.
Hello,
Great news – the upgrade to Windows 11 25H2 completed successfully and the system is now running version 25H2 without any issues.
Thank you very much for your patience and for taking the time to analyze the logs, review the FRST reports, and create the custom fixlist. After many failed upgrade attempts and days of troubleshooting, your fix finally resolved the problem.
I really appreciate the effort you put into investigating this issue and guiding me through the process. Your help was invaluable.
Thank you again for your excellent support.
Best regards,
Mario Kermiet
Hi Mario,
You're most welcome!
If all is resolved, feel free to mark the answer for this thread. Otherwise, please let me know if there's anything else I can help you with.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 19%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EW%3C/text%3E%3C/svg%3E)
I think it's better to diagnose the errors occurring during the upgrade using the SetupDiag tool. Download the latest version of SetupDiag from this site: https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag
By default, the tool is saved in your Downloads folder.
Now, open a PowerShell as Administrator again. Enter and run the following commands one by one:
cd %USERPROFILE%\Downloads
SetupDiag.exe
The diagnostic results will be saved in the same folder where the SetupDiag tool is located. Upload the result log to OneDrive, share it, and include the sharing link in your reply. This will allow us to see which errors occurred during the upgrade.
You can, of course, also examine the log yourself. When SetupDiag indicates that there were multiple failures, the last failure in the log file is typically the fatal error, not the first one.
I ran SetupDiag. The result is attached. SetupDiag did not identify a specific blocking driver. Driver migration and driver application completed successfully. The rollback occurs after "Ensure suspended services are stopped" during Post First Boot. Could you please review the attached SetupDiag results and identify which additional log or component should be inspected next?SetupDiag_21-jún-2026.log
Can you share the Farbar logs?
Please see my post https://learn.microsoft.com/en-us/answers/c/2705885
I removed oem7.inf, oem52.inf and oem53.inf as instructed. The upgrade still fails at 75% with the same error 0xC1900101-0x40017 during SECOND_BOOT. In the new setupact.log I noticed:
Could these entries indicate the actual root cause?
Please share your Farbar scan logs for analysis.
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.
Hello,
I have attached the requested FRST logs (FRST.txt and Addition.txt).
One clarification regarding Check Point Endpoint Connect VPN:
The software was still installed on the system during the last upgrade attempt, but it was not running or actively connected when I performed the Windows 11 25H2 upgrade. The upgrade still failed at approximately 75% with error 0xC1900101-0x40017 and rolled back to 23H2.
I also previously tested the upgrade after removing ESET Security and several other applications, but the result was the same.
Please let me know if you identify any suspicious drivers, filters, services, or other components in the FRST logs.
Thank you.
Please backup the registry using Acelogix Regbak.
Let me know once done.
The In-Place-Upgrade is being blocked by several drivers. Please run the following commands one by one in a PowerShell (run as administrator):
pnputil /delete-driver oem7.inf -f
pnputil /delete-driver oem52.inf -f
pnputil /delete-driver oem53.inf -f
By referring to your list of drivers you can see which drivers are being deleted.
Restart your computer after deleting the drivers and try the upgrade again.
