Microsoft doing weird things again.. some images are missing in the updated business ESD, at least in the en-us one. EDIT: scratch that, downloaded the wrong ESD file EDIT2: @abbodi1406 the business categories are wrong in the list (x64/x86/ARM64) -andy-
Nobody who is currently on 19043 will... but there are still many on 19042.xxx who still not got the 21H1 EP offered by WU.
well my dad's Toshiba laptop that was running Win10 home 19041.xxx instead of 19042.xxx got offered the 21H1 EP from WU a few weeks ago maybe downgrade to 2004 build 19041.x perhaps
@abbodi1406 I am getting this error "5version:~5 was unexpected at this time." I actually downloaded the latest ISO from microsoft techbench site which contains an install.wim by default. I first converted the install.wim to install.esd using your wim<>esd tool which worked flawlessly. Now when I try to convert the created .esd to ISO I am getting the above error. What to do?
esd-decrypter convert full ESD (contain boot.wim and install.wim) to ISO, not install.esd to ISO use any ISO program to add install.esd to techbench ISO (and delete install.wim) or extract the ISO, replace install.wim with install.esd, then use cdimage to create new ISO Code: cdimage.exe -bootdata:2#p0,e,b"ISOFOLDER\boot\etfsboot.com"#pEF,e,b"ISOFOLDER\efi\Microsoft\boot\efisys.bin" -o -m -u2 -udfver102 -lDVD ISOFOLDER Updated.iso
I just wanted to say that everything works perfectly! I'm finally using 21H1 and got everything up and running butter smooth. Feels great having a proper ISO with just Enterprise also, although I have to admit that it took a couple of tries before I got everything just as I wanted it post installation wise mainly because I was unsure of what new drivers my machine wanted since 1909. A big relief that every piece of software works accordingly.
That's a great job! Though it looks like using the universal MediaCreationTool.bat wrapper would have fitted your needs better as it's a matter of just downloading the script and run it, then select 21H1 (1507-21H1 supported) and then Auto Setup for unattended upgrade keeping files and drivers and with a few troubleshooting options to prevent some known issues (usually it's straight back to upgraded desktop). Keep it in mind for the unavoidable next time
Haha, I noticed it was bad so I did not update mct.bat with it just yet Too bad nobody leeking products.xml / cab anymore, lately all these are just brute-force upgrade links by the adguard folks
@abbodi1406 About uup/esd/Techbench/MVS(MSDN)/VLSC。 If I want integrate LPs/Fods/Updates from RTM image which one is better?
@abbodi1406 Another question is: Which ESD should I use. For the Pro/Edu (N) edition, Which Should I choose, Retail or Volume?
Doesn't really matter, the entered activation key, hwid tool, kms tool should enter the proper key to activate on both. Only scenario i am not sure about is using pro/edu volume on systems with a msdm, dunno if it's picked up by the install without manually entering the key (like needed with pro VL and already established hwid).
Easier to use volume distributions as they do not require entering a key during installation. Other than that, should be the same thing.