Windows 11 Update 0xc1900101 Error

Unable to update to Windows 11 Insider Preview 26016.1000 (rs_prerelease) , install error - 0xc1900101
Version 19.2.0 (54821) Technical Preview
 
I tried the update to 26010 Canary on a 2017 iMac and it upgraded flawlessly.
I suppose the problem is on M Apple Processors just like my M1 Pro MacBook where the upgrade results in the well known error 1900101
 
Yeah, it seems that the problem is related with ARM processors. Does Intel processor fail also - I have no such hardware and can't check it.
 
I have now filed reports on MS Feeback Forum for updates 25997, 26020 (both of them) and 26016. I run 4 virtual machines (release, beta, developer and Canary). Every one of them upgrades with no problem with the exception of the Canary builds.
Hardware: Mac Studio M2. 64G of memory, 1 Tbyte SSD, Wi-Fi/Ethernet (one or the other or both) MacOS Sonoma, MacOS Ventura, MacOS Sonoma Beta 14.1, 14.2. 14.3. No problems upgrading everything except Canary after 25992.

I have tried to get around this problem by:
1. Rolling back to Mac Ventura -September release, the then current version of Parallels, and the exact same configuration that worked previously. Failed 1900101 error.
2. Clean install directly from Parallels. Failed 1900101 error
3.Clean install, deleted every program that was or had ever been 32 bit. Deleted everything not necessary to boot to Windows release. Failed 1900101 error
4. Tried loading in Safe mode. Don't bother.
5. All those diagnostics to "Reveal" the problem? DISM, sfc, Chkdsk, BITS troubleshooter, Windows Update troubleshooter? Yeah, another waste of time. Checked the install logs? Colossal waste of time. Useless information.

MS changed something in the Canary build after 25992 that seems to thinjk that every program is a 32 bit program and that it flatly refuses to run 32 bit programs. When my version 25992 reaches EOL, I just won't be able to see what MS is trying to sneak in on us.
 
MarcinB3 said:
Yeah, it seems that the problem is related with ARM processors. Does Intel processor fail also - I have no such hardware and can't check it.
Click to expand...
As a way around my problem with the Canary upgrade, I loaded the upgrade on our only Intel laptop and it loaded with no problem. This seems to be a Mac ARM64 problem. We are a 99% Mac shop with some mission critical apps that only run MS Windows. All of our field people use Mac laptops with Parallels. I've pulled a field laptop (Macbook Pro M1 version) and have had the same problem updating to the current Canary version.
 
One more attempt, one more failure. I created a new Windows 11 installation, used that installation to go to UUPdump.com and created a Canary ISO. Mounted the ISO and went through the "Install Windows 10" (they still call this Windows 10 in-house). The install got about 30% through the install (up to the first reboot) and then errored out with the following message: Oxc1900101 0x200017. The installation failed in the SAFE_OS phase with an error during BOOT operation.
So, back to MS Forum, another problem report.
 
In the mean time ISOs that created from uupdump is not bootable for clean install as a new VM for last 3 canary builds.
 
denethor said:
In the mean time ISOs that created from uupdump is not bootable for clean install as a new VM for last 3 canary builds.
Click to expand...
It will never be bootable as it relies on existing Windows 11 for booting. If you want a clean install, install Windows 11 from Parallels then mount the ISO. Run SETUP as administrator and you will get the same results as everyone else. No go. Just to add a bit more information, I disabled SIP and tried a clean install. Nope. I tried every possible combination of Win11 installs, no go. If you get an working 26016, please let me know.
 
This problem seems to be a Canary 25997 onward problem. The Beta and Developer ARM64 versions install with NO problem. Any Canary version from 25997 onward will not install. I have tried clean installs, creating new VMs, updates in place, reverting to a previous version of both MacOS and Parallels, voodoo and prayer to the software gods.. Nothing will allow an update out of the 25992 version that I am presently running under the latest (and prior) versions of Parallels. I have tried upgrading from ISO's, from VHDX files, from in-place updates, even ISO recovery DVD's. Canary will NOT update on Mac Silicon at present. That doesn't mean I won't stop trying.
 
0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as: The minidump file: $Windows
 
SpaxZ said:
0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as: The minidump file: $Windows
Click to expand...

Thanks SpaxZ. Unfortunately this is something different. As per my first post, setupdiag founds nothing wrong in the setup log files which can be found in: C:$WINDOWS.~BT\Sources\Panther\ after setup.

Indications for BSD or other types of crashes should be found in setup logs. To my eyes there is no BSD during the setup process. Setup rolls back with the first restart and logs no reasons for it. Anyways I checked the minidump folder nothing there.
 
SpaxZ said:
0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as: The minidump file: $Windows
Click to expand...
You might have missed the posts above where I have tried fresh out of the box, direct from Microsoft installs, safe mode installs, roll-backs to previous versions of both MacOS and Parallels and both, SUCCESSFUL installs of updates to both the Beta and Developer version of the software. You might also have missed the posts on the MS Insiderl forums declaring this a problem with the Canary builds going back to update version 25997 and MS's generic response that this is a "Driver error" or an attached device or wrong phase of the mooon.
Thanks for the response, so far I've tried every possible combination with no luck.
 
AlessandroL7 said:
Same issue with 26020.1000.
Click to expand...
Yep. 26020 fails as well. Has anyone stopped to consider that it may be a MacOS error? What version of MacOS is everyone with the problem running? I'm running Sonoma version 14.3 Beta (23D5043d). Every update since 25995 has not installed and given a 1900101 error but it also happened in Ventura. I tested in both Ventura and Sonoma but nothing prior to that. This may well be a Parallels problem instead but I tested with a prior version of Parallels with the same results. The update does work on Intel machines however with absolutely NO problem. This is really frustrating and not hearing anything from Parallels doesn't make it any better.
 
You must log in or register to reply here.
Back
Top