Windows 11 23H2 → 25H2 upgrade fails with 0xC1900101-0x40017 during SECOND_BOOT

Mario Kermiet 20 Reputation points
2026-06-17T17:02:23.7833333+00:00

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:

  • through Windows Update
  • through the official Microsoft 25H2 ISO using setup.exe and "Keep personal files and apps"

Troubleshooting already performed:

  • SFC completed successfully
  • DISM RestoreHealth completed successfully
  • UEFI enabled
  • Secure Boot enabled
  • No unknown devices in Device Manager

Removed for testing:

  • ESET
  • Check Point Endpoint Security VPN
  • Creative Sound Blaster software
  • MSI Center

The error remained unchanged.

Storage configuration:

  • System drive contains EFI, Windows and Recovery partitions on the same SSD
  • Additional SSDs are present but not used for booting
  • No Intel Rapid Storage Technology (RST) installed

Logs reviewed:

  • Panther logs
  • Rollback logs
  • setupact.log
  • setuperr.log
  • WinSetupMon.log
  • diagwrn.xml
  • MigLog.xml

Notable findings:

  • Winsock migration related warnings
  • Monitoring driver installation failures (0x80070005)
  • Multiple migration/rollback warnings
  • No specific third-party driver identified as the cause

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:

  • through Windows Update
  • through the official Microsoft 25H2 ISO using setup.exe and "Keep personal files and apps"

Troubleshooting already performed:

  • SFC completed successfully
  • DISM RestoreHealth completed successfully
  • UEFI enabled
  • Secure Boot enabled
  • No unknown devices in Device Manager

Removed for testing:

  • ESET
  • Check Point Endpoint Security VPN
  • Creative Sound Blaster software
  • MSI Center

The error remained unchanged.

Storage configuration:

  • System drive contains EFI, Windows and Recovery partitions on the same SSD
  • Additional SSDs are present but not used for booting
  • No Intel Rapid Storage Technology (RST) installed

Logs reviewed:

  • Panther logs
  • Rollback logs
  • setupact.log
  • setuperr.log
  • WinSetupMon.log
  • diagwrn.xml
  • MigLog.xml

Notable findings:

  • Winsock migration related warnings
  • Monitoring driver installation failures (0x80070005)
  • Multiple migration/rollback warnings
  • No specific third-party driver identified as the cause

Has anyone seen this exact upgrade failure or identified the root cause of 0xC1900101-0x40017 during SECOND_BOOT? <PII removed>

Windows for home | Windows 11 | Windows update

Answer accepted by question author
Carl-L 22,665 Reputation points Microsoft External Staff Moderator
2026-06-18T07:14:36.65+00:00

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.

  • Type "PowerShell" in the search bar and select "Run as administrator"
  • Type netsh winsock show catalog > winsock.txt and press Enter.
  • Type pnputil /enum-drivers > drivers.txt and press Enter.
  • Read the files and let me know the if there are any leftover non-Microsoft drivers.

I'm waiting for your reply.

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

5 additional answers

Sort by: Newest
  1. WK123456 11,305 Reputation points
    2026-06-20T15:19:57.5633333+00:00

    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.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.