Windows 11 Upgrade - Error 0xC1900101 - 0x20017

Anonymous
2025-03-11T12:19:08+00:00

Hi, I can't upgrade my win 11 from 23H2 to 24H2

Here is panther and rollback logs.

I've tried setupdiag, cleanboot, driver update, unplugging all external hardware, sfc, chkdsk, dism. Nothing helped.

Windows for home | Windows 11 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2025-03-25T21:40:06+00:00

Hello,

I'll try to describe everything from scratch:

Note: I have a system drive running on an NVMe disk and a data drive configured as RAID 1. Additionally, BitLocker is enabled on my system disk.

First Issue:

During an in-place upgrade, the installation proceeds through the initial checks and starts the upgrade process. At this point, I see the following screen:

Image

Once the process reaches 95%, the PC reboots but fails to start. After several failed attempts, the system rolls back the upgrade, and upon reboot, Windows displays an error message:

Image

Solution:

As suggested by Ramesh, I completely disabled the SATA controller (or you can switch it to AHCI mode) since it wasn’t required for my Windows installation. This allowed the upgrade process to proceed further.

Second Issue:

After completing the first phase, the PC reboots at 95% (as mentioned earlier) and continues installing the update up to 30%.

Image

  • After the second reboot, the installation reaches 100%.
  • However, on the final reboot, a BSOD with the error "INACCESSIBLE_BOOT_DEVICE" appears.
  • After several failed attempts, Windows rolls back the installation and upon reboot, Windows displays an error message: Image

Solution:

  1. Deleted RAID drivers (though I don’t believe this was the cause of the issue, just noting it for reference):
    • rccfg.inf
    • rcraid.inf
    • rcbottom.inf
  2. Completely disabled BitLocker, as suspending it didn’t resolve the issue.

Was this answer helpful?

0 comments

63 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-03-12T22:49:25+00:00

    I beleive I disabled the verifier in safe mode, so there is nothing right now:

    Verifier Flags: 0x00000000

    Standard Flags: 

    [ ] 0x00000001 Special pool. 

[ ] 0x00000002 Force IRQL checking. 

[ ] 0x00000008 Pool tracking. 

[ ] 0x00000010 I/O verification. 

[ ] 0x00000020 Deadlock detection. 

[ ] 0x00000080 DMA checking. 

[ ] 0x00000100 Security checks. 

[ ] 0x00000800 Miscellaneous checks. 

[ ] 0x00020000 DDI compliance checking.

    Additional Flags: 

    [ ] 0x00000004 Randomized low resources simulation. 

[ ] 0x00000200 Force pending I/O requests. 

[ ] 0x00000400 IRP logging. 

[ ] 0x00002000 Invariant MDL checking for stack. 

[ ] 0x00004000 Invariant MDL checking for driver. 

[ ] 0x00008000 Power framework delay fuzzing. 

[ ] 0x00010000 Port/miniport interface checking. 

[ ] 0x00040000 Systematic low resources simulation. 

[ ] 0x00080000 DDI compliance checking (additional). 

[ ] 0x00200000 NDIS/WIFI verification. 

[ ] 0x00800000 Kernel synchronization delay fuzzing. 

[ ] 0x01000000 VM switch verification. 

[ ] 0x02000000 Code integrity checks. 

[X] Indicates flag is enabled.

    Boot Mode: 

    Persistent

    Rules: 

    All rules are using default settings

    Verified Drivers: 

    None

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-12T22:20:11+00:00

    Please post a querysettings share link.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-03-12T18:14:06+00:00

    1 tuneup log

    2 upgrade failure log

    3 . I've switched wdv with standard settings and selected All drivers. BSOD on a login screen

    4 v2 updated logs

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-03-12T13:58:01+00:00

    The computer has had many BSODs since Jan 2025.

    There were also hangs / freezes.

    1. Please post share links for Tuneup plus and upgrade failure info
    2. Read this link on Windows Driver Verifier (WDV):

    Enable and Disable Driver Verifier in Windows 10

    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

    1. Create a new restore point

    https://www.elevenforum.com/t/create-system-restore-point-in-windows-11.3602/

    1. Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

    verifier /reset

    verifier /bootmode resetonbootfail

    https://www.elevenforum.com/t/boot-to-advanced-startup-winre-in-windows-11.425/

    1. Plan to run the tool with various customized test settings.

    a) Test all non-Microsoft drivers

    b) Test no Microsoft drivers

    c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial

    1. Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

    verifier /querysettings

    Post a share link.

    Customized tests will then be posted for the next run of WDV.

    WDV can run continuously during the testing.

    For any BSOD post a new V2 share link into the newest post.

    Windows 11 Pro

    Version: 10.0.22631

    Chkdsk:

    Correcting errors in the Volume Bitmap.

    Windows has made corrections to the file system.

    Event[17491]

    Log Name: System

    Source: Microsoft-Windows-WER-SystemErrorReporting

    Date: 2025-03-04T10:09:38.2080000Z

    Event ID: 1001

    Task: N/A

    Level: Error

    Opcode: Info

    Keyword: N/A

    User: S-1-5-18

    User Name: NT AUTHORITY\SYSTEM

    Computer: Dare-PC

    Description:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8013f71c340, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\030425-13890-01.dmp. Report Id: 0cffbb04-7771-4fd1-8a54-38b6ab45d51d.

    Event[4094]

    Log Name: System

    Source: Microsoft-Windows-WER-SystemErrorReporting

    Date: 2025-02-17T21:57:57.5500000Z

    Event ID: 1001

    Task: N/A

    Level: Error

    Opcode: Info

    Keyword: N/A

    User: S-1-5-18

    User Name: NT AUTHORITY\SYSTEM

    Computer: Dare-PC

    Description:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffe70ae0fbf120, 0xffffa006fd9077b8, 0xffffe70af6933010). A dump was saved in: C:\Windows\Minidump\021725-17250-01.dmp. Report Id: 29227b73-1391-4849-a958-bb6ed119e

    Event[1257]

    Log Name: System

    Source: Microsoft-Windows-WER-SystemErrorReporting

    Date: 2025-02-13T07:20:32.9680000Z

    Event ID: 1001

    Task: N/A

    Level: Error

    Opcode: Info

    Keyword: N/A

    User: S-1-5-18

    User Name: NT AUTHORITY\SYSTEM

    Computer: Dare-PC

    Description:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007a (0x0000000000000020, 0xffffffffc000000e, 0xffffe706f491d6f0, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\021325-15671-01.dmp. Report Id: 4a369f5b-0631-4948-a317-f9da38956d7a.

    Event[5064]

    Log Name: System

    Source: volmgr

    Date: 2025-02-19T16:05:13.3190000Z

    Event ID: 161

    Task: N/A

    Level: Error

    Opcode: N/A

    Keyword: Classic,

    User: N/A

    User Name: N/A

    Computer: Dare-PC

    Description:

    Dump file creation failed due to error during dump creation.

    Was this answer helpful?

    0 comments