Between what? Windows XP was NT 5.x, Vista was 6.0 and Seven was (ironically) 6.1, Win8 was also 6.x but Win10 is now 10.x.
Question. I'm assuming from what I've been reading is that this build has better stability than 1909?
Not really, it's still in testing stage and some things are not available like enabling dotnetfx35 by the "add/remove features" option, MSFT has not yet made the download files available (just one example).
Thanks Enthousiast, good to see ya again I'll hold off until it's released to install it. I'm mainly after the new GPU Scheduling feature which to me is a huge deal.
19041.21.200103-1558.VB_RELEASE_SVC_PROD1_CLIENTPRO_OEMRET_X64FRE_EN-US Iso file size 3.3GB I thought it was gonna be 5GB or more.
Could you explain to us noobs more on this "single index" thing and why uupdump doesn't use it or why .21 is 4,1GB instead? Thanks.
UUP dump uses it, when set. Use Cleanup and resetbase + create install.esd instead of install.wim or only use install.esd will already decrease the size with appox. 33%.
Someone test to play PUBG with this build? Because i read in somewhere that this build has problems with Battleye anti-cheat used in PUBG.
I installed 19041.1 from ISO then proceeded to update to 19041.21 via CU. Everything was running smooth. As soon as I ran Dism.exe /online /Cleanup-Image /StartComponentCleanup I faced the can NO longer boot problem. This can't be FINAL and urgently needs fixing. I believe Windows runs this command itself during maintenance and cleans up after itself. If they don't fix it before signing off there will be a lot of unbootable systems out there.
Oooh I see. But after 1903 and the errors with DISM I avoid this option. Have you done any testing on your machine if it lets you update after using dism to clean up stuff or disk cleanup?
This is what I have done after installing 19041.1 run this cmd as admin Dism /online /Disable-Feature /FeatureName:NetFx3 Afterwards the installation of the update KB4522355 via win update was done, which worked fine with out any problem running smooth. Afterwards I activated the NetFx3 package again with the following command. I still have no problem after restart. Dism /online /Enable-Feature /FeatureName:NetFx3 If you ran Dism.exe /online /Cleanup-Image /StartComponentCleanup I faced the system can NO longer boot up.
Do you mean you can now run DISM /ResetBase with DisableResetBase=0 in the registry after installing the N'th CU and still apply the N+1'th CU? Or do you mean it's safe to leave /ResetBase in your scripts because it's now disabled in the registry anyways?
/StartComponentCleanup is probably what rendered one of my .21 installs un-bootable (but it was self-fixable by shadow copy restore). But running Disk Cleanup in Admin mode (with everything ticked) instead didn't seem to cause any issues.