Installation Error - 0xc19001 101 when trying to update to Windows 11, version 25H2 from version 24H2

I receive Installation Error - 0xc19001 101 when trying to update to Windows 11, version 25H2 from version 24H2. Have uninstalled third-party antivirus and firewall, disconnected all non-essential hardware and tried again, no luck?

Hello @flyfishbum and welcome to ElevenForum.

Go here and scroll down and download and use the "Enablement Package".
Takes 3 seconds and a reboot.






Here's some other things that you may find useful...

Welcome to the forum. Please complete the system specifications section of your forum profile so we can know what hardware you are dealing with.

An upgrade error that begins with 0xC1900101 is usually a driver error.
You would need to look at the failure logs to see the exact cause of your failure. Depending on where in the upgrade the failure occurs, the log can be in multiple places.

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

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

If you are unable to read the logfiles, copy them to a folder, zip the folder, upload the zipped folder to any cloud provider and post a SHARE link here to the zipped folder.

If logfiles do not direct you to what caused the error, I advise anyone to not waste his time. Either stay where you are or Bite the bullet, back up your data, and do a clean install. 25h2 can have you chasing your tail for days.

Some Microsoft tips for dealing with 0xC1900101:

Please perform the following steps:





1) Add WMIC:

DISM /Online /Add-Capability /CapabilityName:WMIC~~~~






2) Run Tuneup plus > post a share link








3) Run the V2 log collector > post a share link





4) Run upgrade_failure_info.bat > post a share link

Same. Are you using the ISO from UUP? I ran setupdiag and found nothing. I believe it's a UUP creation issue. I'm currently creating a much older ISO to test. I will post the results.

To be clear I unplugged all peripherals, uninstalled all antivirus/antispyware programs and still ended up with the same error. In desperation to actually see if it was my system I downloaded the ISO straight from Microsoft. It worked with everything I removed installed.

As a side note upgrading via the *.msu file works. So for now if I ever need to do a in place upgrade I'll use the Microsoft ISO and then use the *.msu to upgrade to the latest version.

This is the version I downloaded:

Welp 26200.8313 works just fine with everything plugged in and even with Norton installed. As I stated, setupdiag.exe shows nothing but it is giving the generic rollback error code with 26200.8737.
So it might be painful but I'm going to go though all of the recent UUP releases to see where this issue started.
So 26200.8313 was released April 17th and that's good. Pressing on.

And I've rolled back to 26200.8737. Now to test the next release after 26200.8313. This might be a WinRe issue.