This reminds me a lot of the case of the new Edge, some blogs and people on Twitter began using names that combined the words Chromium and Edge when referring to the new browser, but Microsoft never used any of those names to refer to the new browser, instead, they did use the words "new Edge" several times, so IMHO that was a much more appropriate name than those other (awful) names.
I'm still stuck on build 19037. I'm having the same trouble installing this build that I did when I tried to install 19041. My system goes through the initial install but on the final restart it updates to 90% and stalls. Sometimes after a long time it will roll itself back. If not I have to manually shutdown and restart. Microsoft has not responded to any of my posts on the feedback hub. I am not the only one there with this issue that pops up every few builds. I deleted the contents of the windows softwaredistribution download folder, and ran DISM and SFC tools, redownloaded 19041 and tried again. It stalled at 90% and then rolled itself back to 19037. I tried a third time and it stalled at 90% for 12 hours. I had to reboot and revert back to 19037 manually. There has to be something simple that MS guys are missing, as this issue seems to reoccur every other build for many of us. Also a lot of times it uninstalls NVIDIA drivers. The install log says "Windows failed to install the following update with error 0xc1900101". Any help would be appreciated, as I am now having the same problem with 19536
Make clean install. There is no problem with that. BTW, I noticed that the word "install" has the word "stall" in it.
Try to uninstall the ide/sata chipset driver, so the generic windows driver is used and next try to upgrade.
Nope you're not alone. In the past I was able to progress to 19025 too and because I did a rollback now I'm stuck on 19018. The new releases just reboot after installing updates phase. I'll try what @Enthousiast said since everything else seems to fail. Even disconnecting everything that can be disconnected from the PC so I'm tending to think nvidia or chipset drivers
Strange anomaly, I'm running 041.1 and 536.1000 dual booting off the same disk to see the differences Both say windows is about 14.4 GB but size on disk is about 3.5 GB less on 536 Nothing is showing as compressed and the installation is the same for both Doesn't seem to affect anything just wondering why the difference?
This. I too wanna know what's the diff between 19041.1 & this 19536.1000 build? IS this v19536.1000 build is from the 2004 branch or 2009 branch?
It doesn't belong to any of those branches, the fast ring builds now belong to a "new" branch that Microsoft calls "Active Development", more information about these changes here.
A lot (in fact, most) of the files in \Windows\System32 are hard linked to the main SxS (Side-by-Side) repository, which is in \Windows\winsxs. As a result, many tools will show a wrong size, as they count hardlinked files two times, when in fact they do only exist once.