Solved Update to 24h2 fails with error OXC1900101 incompatible or outdated driver

I have tried to update from 23h2 to 24h2 twice with the error OXC1900101 which indicates there is a driver issue. Looking at Device Manager (see image attachment) there is nothing noted with the typical exclamation sign. Any ideas or solutions?

Might open Device Manager [right-click Start button] then under View click Show hidden devices, see what shows up there.

Please run the V2 log collector and post a share link.

Sir_George said:

error OXC1900101

Click to expand...

I have a faint recollection of receiving an error like this when upgrading to Windows 11 from Windows Ten. I think the fix was increasing the size of my Recovery Partition. I can’t exactly remember.

Thanks to all who replied. I found the solution by doing a little more research. It appears that disconnecting the USB attached storage devices was necessary to complete the update. I will mark this as solved.

We are glad to hear your issue has been resolved, thank you for letting us know that all is now well!

Sir_George said:

OXC1900101 which indicates there is a driver issue.......Looking at Device Manager (see image attachment) there is nothing noted with the typical exclamation sign.

Click to expand...

You really can not go by device manager. Keep in mind that the upgrade will fail when it sees an incompatible driver. This does not necessarliy mean that the incompatible driver is being used by an active device. It can be an old version of a driver left behind when a new one is installed. This is common with graphics drivers and wireless drives that do not cleanly uninstall. It can also be a driver associated with an uninstalled device.

Per Microsoft, when an upgrade fails, a logfile is created in one of multiple places dependent on the point of the failure. This is why @zbook has asked you for your logfiles. If you are confidant that you can analyze the probem for yourself here is the location of the files.

• If no error message occurs, the following log files are created when an upgrade fails during installation before the computer restarts for the second time. You have to look at these logs to get an idea of what's causing the failure.
  
• C:\$Windows.~BT\Sources\panther\setupact.log
• C:\$Windows.~BT\Sources\panther\miglog.xml
• C:\Windows\setupapi.log
• 
  
• [Windows 10:] C:\Windows\Logs\MoSetup\BlueBox.log
• C:\Windows\inf\setupapi.app.log
• C:\Windows\inf\setupapi.dev.log
• C:\Windows\panther\PreGatherPnPList.log
• C:\Windows\panther\PostApplyPnPList.log
• C:\Windows\memory.dmp
• The following log files are created when an upgrade fails, and then you restore the desktop:
  C:\$Windows.~BT\Sources\panther\setupact.log
• C:\$Windows.~BT\Sources\panther\miglog.xml
• C:\$Windows.~BT\sources\panther\setupapi\setupapi.dev.log
• C:\$Windows.~BT\sources\panther\setupapi\setupapi.app.log
• C:\Windows\memory.dmp
• The following log files are created when an upgrade fails, and the installation rollback is initiated:
  C:\$Windows.~BT\Sources\Rollback\setupact.log
• C:\$Windows.~BT\Sources\Rollback\setupact.err

My upgrade rolled back so I found my particular error in the last 2 logs. My error was associated with the migration of my user account. After days of trying to upgrade, I cut my losses, clean installed, and got on with my life.

If logfiles do not direct you to what caused your error, I advice anyone to not waste his time. 24H2 can have you chasing your tail. Either stay where you are or make an image of your system, Bite the bullet, and clean install.

Sir_George said:

Thanks to all who replied. I found the solution by doing a little more research. It appears that disconnecting the USB attached storage devices was necessary to complete the update. I will mark this as solved.

Click to expand...

Western Digital drives? Windows finds a fault with the older WSES driver bundled with those drives.

garlin said:

Western Digital drives? Windows finds a fault with the older WSES driver bundled with those drives.

Click to expand...

That was the problem! I had encountered this issue in the past but forgot about it. I remember removing the drivers back then, but they were reinstalled, probably because I bought a new WD drive. Thanks for your post.