Windows 11 Upgrade - Error 0xC1900101 - 0x20017

Anonymous

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.

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

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:

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:

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%.

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:

Solution:

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
Completely disabled BitLocker, as suspending it didn’t resolve the issue.

0 comments

63 additional answers

Anonymous

2025-03-18T10:48:35+00:00

Hello,

g hub uninstalled, no logitech drivers in the system

Still BSOD:

stop code: driver verifier detected violation

what failed: wdf01000.sys

v2 logs
Was this answer helpful?

0 comments No comments
Anonymous

2025-03-18T02:43:37+00:00
1. Please find alternative hardware for Logitech hardware.
2. Uninstall all Logitech software: (make sure these drivers are uninstalled)
logi_joy_vir_hid Logitech G HUB Virtual HID Device Driver c:\windows\system32\drivers\logi_joy_vir_hid.sys

logi_joy_bus_enum Logitech G HUB Virtual Bus Enumerator Driver c:\windows\system32\drivers\logi_joy_bus_enum.sys
1. Create a new restore point
2. Restart WDV with all customized tests except [ ] 0x00000004 Randomized low resources simulation.
3. If there is no BSOD then turn off WDV and upgrade
4. For any BSOD post a new V2 share link into the newest post.
logi_joy_vir_hid.sys Fri Sep 2 15:38:50 2022 (631269DA)

logi_joy_bus_enum.sys Fri Sep 2 15:38:46 2022 (631269D6)
Was this answer helpful?

0 comments No comments
Anonymous

2025-03-17T10:11:35+00:00

Hello,

There is now such option [ ] (0x00000000) Automatic Checks in the list.

1 verifier settings

2 V2 logs
Was this answer helpful?

0 comments No comments
Anonymous

2025-03-17T00:36:09+00:00

Please use notepad instead of a spread sheet for copy and paste.

List the mouse and keyboard in use information.

Restart WDV > test all non- Microsoft drivers; test no Microsoft drivers > select these groups of customized tests:

Group 1

[ ] (0x00000800) Miscellaneous checks

[ ] (0x00000400) IRP logging

[ ] (0x00000010) I/O verification

Group 2

[ ] (0x02000000) Code integrity checks

[ ] (0x00000000) Automatic Checks

Group 3

[ ] (0x00000008) Pool tracking

[ ] (0x00000100) Security checks

Group 4

All customized tests except [ ] 0x00000004 Randomized low resources simulation.

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

For any BSOD post a new V2 share link into the newest post.
Was this answer helpful?

0 comments No comments