Need help upgrading to Windows 11 pro 24H2 form 23H2 0xc1900101 error

Before a clean install:

These are steps that were not yet done that may be useful for troubleshooting the upgrade failure:

(These scripts can collect data that were not in Farbar and other used scripts)

(event viewer, dumps, hardware specifications, power and error reports, dxdiag, etc.)

1. Run the V2 log collector and post a share link into this thread:

BSOD - Posting Instructions | Windows 11 Forum (elevenforum.com)

2. Run: upgrade_failure_info > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/353454d1638278360-batch-files-use-bsod-debugging-upgrade_failure_info.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Batch files for use in BSOD debugging - Windows 10 Help Forums

3. Run Tuneup plus > post a share link

https://www.tenforums.com/attachmen...-files-use-bsod-debugging-tuneup_plus_log.bat

Batch files for use in BSOD debugging - Page 2 - Windows 10 Forums

Batch files for use in BSOD debugging - Windows 10 Forums

4. Run the Bitdefender uninstall tool :

How to Uninstall Your Bitdefender Security Solution on Windows

How to Uninstall Your Bitdefender Security Solution on Windows

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

6. Create a new restore point

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

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

8. 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 Ten Forums tutorial

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

10. Check Hyper-V settings:
11. Check Sandbox settings:

Enable or Disable Windows Sandbox in Windows 11 | Windows 11 Forum

12. Uninstall oem8.inf and check filter drivers:

Administrative command prompt:

pnputil /delete-driver oem8.inf /uninstall /force

fltmc

Post a share link.

2025-04-30 14:42:10, Error SP Failed to remove INF oem8.inf, Err = 0x3[gle=0x00000003]

Task: {0D481F27-E63D-4E7F-9F73-A7EF21881664} - System32\Tasks\Bitdefender Agent WatchDog_65D6944A0EF74FDAB96E31112AD39864 => C:\Program Files\Bitdefender Agent\27.0.1.290\WatchDog.exe -> C:\Program Files\Bitdefender Agent\27.0.1.290\repair

2025-04-30 14:59:35, Info MIG Processing Registry: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Bitdefender Agent WatchDog_65D6944A0EF74FDAB96E31112AD39864

Hi Lewis,

Sorry to hear that. It might be a clean install time then. The only drivers we didn't touch are the Google Drive (which adds a file system driver), Logitech G-Hub, and the chipset drivers, including ETDSMBus.inf. For further troubleshooting, it is recommended to create an OS image backup. Some options include Hasleo, AOMEI Backupper, EaseUS, or Macrium Reflect (not free of charge.)

Edit:

Uninstall Logitech G-Hub as well.

• logi_joy_bus.sys
• logi_joy_xlc.sys
• logi_joy_xlcore.sys

Ramesh,

The in place update failed again.

FRST.7z, Addition.7z and SetupLogs posted at https://gofile.io/d/O7jTDb.

They are listed 4/30/2025

Screen shot of failed message-

Thanks,

Lew

Thanks!

It’s running now. I’ll share the logs when finished

Thanks!!