The full instructions are provided over here. The PowerShell based solution is attached (see first mentioned link above). Difference between WZT "old solution" and this: - PowerShell based and does work on Linux and macOS (needs PowerShell Core installed) - Does work on Android (the user agent string was added for this) - WZT original solution required to interfere with the website (open debug menu, add X), later he provided an userscript which needs a user script add-on/extension installed (this is here not required since it works without anything) To address Enthusiast's concern/statement: - Yes, the script fetches the latest ISO (not ESD) which is, as he pointed out due to the fact that the website follows MS own lifecycle guidance. There is nothing I can do here. It's just how it is. MS calls 1909 only a "service pack" (enablement package), so you get it anyway via Windows Update offered as "KB" (however, the correct term is more Service Pack-Style Update). - No, the title does not say "latest" ESD. - MCT does not work on Linux/Android, that's the whole point of providing a PowerShell "solution". Feedback: If someone has "useful" feedback, please provide it and I will change the script otherwise I see pedantic comments as "trolling". And no, I did not reported his posts, dunno why Enthusiast comments got removed - and I don't care. Just my two cents on this. Take the script and provided instructions "as is" or leave it but please do not piss me or (others) off with pedantic troll comments, otherwise no one likes to provide some script for MDL anymore. It's simply not helpful to be a "smart ass" without providing anything useful. Thanks....
A 3 year old techbench hack from wzor, iirc, published first on MDL by @bodmas .. MDL Techbench dump by @whatever127 offers all Techbench 8.1/10/IP ISOs.
Not really. Code: Name: Win10_1909.iso Size: 4939528192 bytes (4710 MiB) CRC32: FDC7C49B CRC64: 30753D77FBE1BC83 SHA256: 9846DFBDD7C39EB8D025E0F28E180C6F4084ECF87ECD11805CD19C205F7A3B4E SHA1: 344CA92459C23663D5F857C72A7C030F85F19BE8 BLAKE2sp: 5AF5F48B5CBAB8BAC7B474B6EEB9F6A66DA8FC1C7D73404DB44AF791C1F4233F = 18362.30 (is not 1909). Code: Package Identity : Package_for_KB4497727~31bf3856ad364e35~amd64~~18362.30.1.0 State : Installed Release Type : Security Update Install Time : 4/1/2019 11:03 PM Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.30.1.2 State : Installed Release Type : Update Install Time : 4/1/2019 11:05 PM
It works, you can't blame the script for MS decision to "hide" the 1909 ISO. If you want other stuff then use the adguard mirror, that's the whole point why it was created in the first place. WZT also did not provide a PowerShell script at the time btw.
Windows 10 1909 [ID: 1429] Windows 10 1909 Home China [ID: 1430] Windows 10 Education 1909 [ID: 1431] Content: https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-345#post-1559501
Yeah, I'm well aware of FIDO, but FIDO requires IE for Invoke-WebRequest. A workaround as he mentioned in his readme.md file is not possible on Linux/Mac/OS nor Android since IE or the registry key exist on those systems. So my solution is still the best. However, I saw he hard codes (pre-defines) the Windows builds in his script via $WindowsVersions. That is maybe something I could add to enforce that a user gets a selection on what to download. Yes, Rufus, IE and other dependencies. Again my script is better in a sense that it's designed for all systems and not only "Windows only". I do not say that Fido is bad but it's a different approach. If you need optional (external tools) like Rufus (see FAQ), then this is off-topic because those tools can already download Windows 10 ISOs. The point is that you do not need external tools.