New
#21
OK...just trying to make sure I had an ISO available. I guess I could TRY Ventoy to see what happens as well.
OK...just trying to make sure I had an ISO available. I guess I could TRY Ventoy to see what happens as well.
I'd recommend Ventoy as an excellent tool. I'd also recommend turning to uupdump.net to check out known/current builds. Thus for example, here's what showing at the top of the list for Windows 10 20H2, all the way up to build 19042.789:
It's a great place to go looking at history in the making, and what's already happened for all major Windows 10 version.
Hope you find it helpful.
--Ed--
UUPdump.net will build you a custom ISO that slipstreams all applicalbe CUs and other updates into install.wim so that, once installed, you are completely up-to-date. It's a rather nice piece of work, actually, but takes a while to get put together. I just did it late last week and it took over an hour to build the ISO for 19042.792 (plain-vanilla ISOs usually take less than 10 minutes on my production PC thanks to ample CPU cycles, fast SSD storage, and an Internet connection that varies from 400-800 Mbps on an average weekday).
HTH,
--Ed--
If I read MPSAN's intention correctly, he just wants a reasonably current ISO for when his "Big Day" comes. Any fairly current ISO of the same base version will do, just letting it check for updates during the in-place update. Does not have to be right up to the minute, or even close. I've used ISOs from MS that were close to 6 months old with no problem. An in-place on my machine, with update checking and keeping everything, runs about 25 minutes.
Thank You ALL for your help. I believe I will just burn my 10.0.19041 631 to a DL dvd and just call it good from there. I think I may try VENTOY at some point but for now all seems OK and I do not need the latest slipstreamed version that will go out of date in a matter of weeks anyway.
One last question I hope. I used MediaCreationTool20H2.exe and went thru the steps to get the ISO. No problem, but when I check the Version I get an ISO with 10.0.19041 631 an NOT 20H2 19042.662 so why is it still not giving me 20H2?
2004 (19041) and 20H2 (19042) share a common set of system files and cumulative updates. 2004 contains all the 20H2 features, but they are dormant. A small enablement package turns on the dormant features and bumps the major build number up by 1 to 19042. The ISO includes the 2004 system files and the enablement package, so although it says its 19041, if you use it to do a clean install or a repair install you will have 19042 20H2 installed.
This enablement package was also delivered by Windows Update to update 2004 machines to 20H2, it installed like a cumulative update and could be uninstalled like one too. When installed by the 20H2 ISO it cannot be unistalled.