dir command compare numbers as strings when it sort files hence, 9 28 is bigger than 1 023 hence, 19043.928 file is listed after 19043.1023 file hence, W10UI set iso version as 19043.928 Code: >set updtver=19043.1023 & set vermajor=19043 >set updtver=19043.985 & set vermajor=19043 the fix is just one letter, to sort files by date Code: dir /on -> dir /od
The MCT downloads ESD files to create ISOs locally, so they will never be the same twice (the downloaded ESD files can be verified). MVS and Techbench ISOs are created by MSFT and centrally distributed, checksums can be verified.
If you want to play with 21H2 (19044.1023) Dism /Online /Add-package:C:\Windows\servicing\Packages\microsoft-windows-product-data-21h2-ekb-package~31bf3856ad364e35~amd64~~10.0.19041.1023.mum Dism /Online /Add-package:C:\Windows\servicing\Packages\microsoft-windows-product-data-21h2-ekb-package~31bf3856ad364e35~amd64~de-DE~10.0.19041.1023.mum Dism /Online /Add-package:C:\Windows\servicing\Packages\microsoft-windows-product-data-21h2-ekb-wrapper-package~31bf3856ad364e35~amd64~~10.0.19041.1023.mum Dism /Online /Add-package:C:\Windows\servicing\Packages\microsoft-windows-product-data-21h2-ekb-wrapper-package~31bf3856ad364e35~amd64~de-DE~10.0.19041.1023.mum Dism /Online /Add-package:C:\Windows\servicing\Packages\microsoft-windows-updatetargeting-clientos-21h2-ekb-package~31bf3856ad364e35~amd64~~10.0.19041.1023.mum Dism /Online /Add-package:C:\Windows\servicing\Packages\microsoft-windows-updatetargeting-clientos-21h2-ekb-package~31bf3856ad364e35~amd64~de-DE~10.0.19041.1023.mum Dism /Online /Add-package:C:\Windows\servicing\Packages\microsoft-windows-updatetargeting-clientos-21h2-ekb-wrapper-package~31bf3856ad364e35~amd64~~10.0.19041.1023.mum Dism /Online /Add-package:C:\Windows\servicing\Packages\microsoft-windows-updatetargeting-clientos-21h2-ekb-wrapper-package~31bf3856ad364e35~amd64~de-DE~10.0.19041.1023.mum Note: For systems with a different installed language, the de-DE must be replaced with e.g. en-US. If additional updates appear in the meantime, the 1023 must be replaced with the new build number. Actually, it's weird. Microsoft is tinkering with a new version with big changes and then only the Windows 10 21H2 19044 comes out. Could one now ask whether the big changes will come with the 22H1, or Microsoft will keep the numbering now. I have NOT tried this & don't know just what is unlocked ? Works only if the KB5003214 is also installed Looks like there will be an Enablement Package for 19044 which is missing ?
Well now some questions on Windows 10 21H2 is suppose to be a big Update ? So what is 19044 + Enablement Package ? 19044 is still based on 19041 ? Another Enablement Package ? Is this still "Sun Valley" ? Has the Big Update been pushed to 22H1 ? We know Microsoft is already working on 22H1. Looks like KB5003214 (.1023) will be the base for 21H2 ? Feel free to give your thoughts.
With MSFT, anything is possible, but releasing 19044 with an EP to business customers, and then a completely new version to consumers, with a new base number, is unlikely. Historically, the beta channel is for beta-test insiders that are consumers. The release-preview channel is for beta-test insiders that are business clients. Feedback from the beta channel, and release-preview channel, to the development team, has driven development for the same version of windows (19041) for many months. I don't see evidence that this paradigm is going to change and that business customers are going to get one version of Windows 10 and consumers are going to get a different version. It's possible, but I don't think it is likely.
I received a offer in WU for 21H1 today. I passed on it though until more bugs are worked out by others.
Can anyone give me a hand with a problem I'm having building a 19043.1023 image? I get an error while it is building the image... Deployment Image Servicing and Management tool Version: 10.0.21382.1 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1023.1.17 [===========================69.0%======== ] Error: 1726 The remote procedure call failed. An error occurred closing a servicing component in the image. Wait a few minutes and try running the command again. The DISM log file can be found at C:\Windows\Logs\DISM\DismLCU.log Anyone have any ideas what to try and do about it?