Windows Update Install error - 0xc1900101

That was my previous experience attempting to use the VHDX to create an updated version. Frankly, that was what I expected to happen this time. For some reason (and as we use a fixed configuration, there were no changes), it worked. I wish I could tell you exactly why but unfortunately, I have no clue. The only advice I can offer is to persevere and one day, for no apparent reason, it'll work. I hope this offers a bit of encouragement if nothing else.
I am running the latest update to Parallels Desktop on a Mac Studio M2 with 64Gb of memory and a 1Tb SDD with the latest MacOS beta update.
I chose to install manually and fiddled with a few settings like choosing more memory and processors, turned off sharing and some more things...
Not sure which did it, but the install went forward.
had to manually install the parallels tools but it is up and running....
 
Why don't you publish those "further instructions" here so that everyone who is unable to update in-place 26042 Canary versions can try the instructions. That may lead to a solution to the problem much quicker.
I have managed to successfully update from 26040 to 26058 by setting the CPU & Memory in the VMs hardware configuration from automatic to manual with 4 CPUs and 4GB memory.
 
I have managed to successfully update from 26040 to 26058 by setting the CPU & Memory in the VMs hardware configuration from automatic to manual with 4 CPUs and 4GB memory.
As our default configuration for Win 11 under Parallels, I have been using 4 CPU and 16 GB of memory all the way thorough the strangeness of recent Canary updates. From 25997 to 26040 it didn't make any difference. From 26040 to 26052 it didn't work now matter what configuration was used. From 26052 to 26058 it once again would not do an in place update, thus the complete from scratch install using the VHDX.

I have managed to successfully update from 26040 to 26058 by setting the CPU & Memory in the VMs hardware configuration from automatic to manual with 4 CPUs and 4GB memory.
That's close to our default configuration. We use 4 CPU's (I think the exact term for that really should be CORE, but what do I know? :-) ) and 16 GB.
 
Amazing! I started the Canary update to 26063 and after 15 minutes of sitting at 64%, I decided to go to uupdump.net and create an ISO of the update. Opened the ISO update, clicked on Start (run as administrator), clicked on Install and found something else to do for about 20 minutes. As hard as it is to believe, it installed and is working. I guess I really should try from Windows Update but I ran out of patience previously so I'm just going with the created ISO.
 
Reset Windows Update Components
  • Open Command Prompt as Administrator and run these commands:
    cmd
    net stop wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    ren C:\Windows\System32\catroot2 catroot2.old
    net start wuauserv
    net start cryptSvc
    net start bits
    net start msiserver



By Ajay Raj
-------------------------------------
My Friendly SIte : Herbal Supplements Manufacturer in India | Nutraceutical Manufacturers in Chennai
 
Back
Top