Hello! Thank you all for the work you put into this. I've relied on you for many years and it's amazing what you come up with! But I can't figure this out today. Easy questions for you! I need a regular Win 10 Enterprise iso, and the LTSC. I found this files.rg-adguard.net/file/8487fa0a-c0be-ff2d-18d1-a2bac61c9ed5?lang=en-us and if you search the hashes you can find torrents. (1) But that file is gigantic and probably breaks on FAT32 USB. It includes useless versions. The old iso I used is the: 18363.592.200109-2016.19H2_RELEASE_SVC_REFRESH_CLIENTENTERPRISE_VOL_X64FRE_EN-US.ISO Which is simple x64, en_us, enterprise, 19H2. (2) How do I get such an iso again? Is the 'right way' this thread: forums.mydigitallife.net/threads/windows-10-esd-repository.59082/ and then using this tool forums.mydigitallife.net/threads/windows-10-esd-repository.59082/#post-992731 ? (3) There I found 19044.1288.211006-0501.21h2_release_svc_refresh 19044.1165.210806-1742.21h2_release_svc_refresh What is the difference between the two? (4) I tried this github.com/AveYo/MediaCreationTool.bat but that didn't work at all, it stayed at 0%. (And I think it'd only get the big one from (1) anyway.) (5) This does not have the enterprise at all: tb.rg-adguard.net/public.php It's often referred to here but it doesn't seem to have it. ------ (6) Is it correct that there is only 1 LTSC iso? I went here forums.mydigitallife.net/threads/discussion-windows-10-enterprise-iot-enterprise-n-ltsc-2021.84509/ and found opendirectory.luzea.de/microsoft/my-visual-studio/8165-windows-10-enterprise-ltsc-2021/ . So in order to get the latest, 'right' LTSC, I use the opendirectory.luzea.de/microsoft/my-visual-studio/8165-windows-10-enterprise-ltsc-2021/en-us_windows_10_enterprise_ltsc_2021_x64_dvd_d289cf96.iso ? (7) Why is this file so big again? It should only be 1 version, right? Thank you all!! Hopefully this thread helps other people who are looking for the same! I'm not permitted to post links so I had to make them non-clickable.
Ok i found it from the link https://forums.mydigitallife.net/th...chbench-msft-iso-uup-svf-esd-office-vl.72165/
That's the LTSC, the one I referenced is the simple enterprise. And that's the one I already found and posted. I would like to know if there is only this one and that's it, or if there is something to know about like with the 'normal'. What about the ESD way I linked? Is this how you get them normally today? Ah, thank you! I haven't seen this anywhere else, the others only have 1 for the 'February refresh'. Every site uses different codes/syntax and there is no official microsoft list I can find. Never knew, thanks. Also my other question, why is the LTSC iso bigger than the big enterprise with multiple editions?
All LTS releases are guaranteed to fit on FAT32. All MCT ESD releases are also guaranteed to fit on FAT32. Should note that the ESD repository thread also lists ESD refreshes that were meant for windows update only, not MCT, hence some of them will not fit FAT32. edit: @random, there's only one LTSC 2021, and most likely won't ever be a refresh of it and you can trust the hashes published in the various threads here, or pay yourself for a subscription at microsoft to get download links and hashes
That is a converted one index ISO, not officially MVS released. You are comparing modified/locally converted UUP/ESD>ISO ISOs with officially released ISOs. And you're comparing different builds with different updates pre-integrated, when comparing then compare the same build ISOs.
Thank you both very much @Enthousiast @BAU! It is a bit clearer now. So I should wait for the February ESD to be posted if I want another current single iso? Or use the bigger official one with the multi editions. The ESD files come directly from microsoft so no need to verify, and the big isos have hashes all over. I'm barely even alive and now the rich started another war so not happening. Actually right now I'm wasting time with PCs when I don't know how long I'll even be alive, but let's hope for the best. Again thank you very much for your efforts, it is appreciated! Without you normal people could not even use windows at all. Way too expensive + you need the enterprise to reduce spying abuse.
ESD's get refreshed only when absolutely necessary. I would not expect any refresh (except later this year when Microsoft might enforce some enrollment policies on 10 as well). It's designed to have a stable base, that gets updated on-the-fly when you need it when you use MCT. Official monthly refreshed media is always gonna be "bloated". And hard to get without a subscription (hence the mirrors and sfv repositories at MDL). Why don't you use uupdump, it offers refreshed media builder script for any edition (except LTSC), can build single edition iso from the get-go, and all sources are coming from microsoft servers.
I'm well aware, that was not the question. Why would you think I don't know the arch? Point is he clicked 'latest' and got contradicting build numbers. His numbers are not 19044.1566. I'm administrating many systems on very tight constraints and the more space I can save the better. Also, every admin should know exactly what he's doing. Windows 'style' seems to be very laissez-faire. Obviously I should know the differences. I tried all the docs, but I cannot possibly navigate the hell that is the microsoft website. Not sure why you imply I'm that stupid, but again, I'm well aware of the arch. I specifically asked for the difference in build numbers, and the phrase 'preview', suggesting a beta. In the tutorial there's a regular non-preview. Unlike Linux where you can look a lot of things up in detail (not always of course), all the Windows backend details are reverse-engineered by helpful niche-nerds like you guys on MDL. And it constantly changes. Now Microsoft even killed the LTSC's 10 years and only does 5. I'm sorry I don't do this every day. I put effort into selecting correct methods and then use the isos for years to come! Edit: I did it with the feature update and the .1566 build as per microsoft website. It's downloading now and I'll just use that because the alarm is sounding and looks like the capitalist pigs are going to hurt us. But I like to say that it's just natural to be curious about what your software does. I always want to know what something does before I run it, and I at least skim the batch magic too. I don't understand people who just pick the next best option without understanding why.. Edit2: >Because those are the safe bet, more complete, close to an iso refresh, while the Cumulative Update entries are what gets used by Windows Update (so not needing boot files update). You don't need to reply to this, but just to show you what I mean: - Safe bet, why? How can one setup be more reliable than the other? (= important to decide) - Being used by win update sounds positive. Do boot files mean the efi? Again, the implications matter. Windows is extremely intransparent and complex, that's why I always go find the 'standard' solution. The business iso I referenced is the 'standard', but I was interested in learning how the single ones are made. There are update tools on MDL that download literal update files only, so please understand why I expected the UUP to be about.. updates again. I used the update tools a long time ago already, to download first and then hand out on USB offline. But thank you for your help and the creators of all the tools! I'm sure next time there will be a thousand changes again haha It really is greatly appreciated. When you have to use windows, first step is always MDL.
You asked for it (the ELI5). You also did not do the same as in the video provided. And obviously that video is gonna be outdated in a month or two, are you expecting Enthousiast to recreate it every time, can't you just assume it's the same result, only newer. 1526 is the latest public, above it are release previews that you should never ever make an iso out of them, but stick to installing them via windows update so you can easily revert them. 2nd part: Why? Because I said so. Or probably because of personal experience, not pulled out of my arse. uupdump is obviously not a microsoft service. It's a "hack" to get public windows update uup format links for every build and language, stuff it in a database, and get it to us the users in a easy to interrogate front-end. But those uup files are processed by Windows update in it's own way, not like standard setup, they don't need to include the setup files that are usually on iso media (and on esd's). So the wonderful people behind this project have made their own link dumpers and a conversion script that closely generate an iso with the setup files taken from the recovery that thankfully come with the uup files, and from specific "DynamicUpdates for sources" updates. This is the whole story. There's no shady aspect at all. Sorry if I sounded a bit on edge - it's because I am, obedient drunk retards are shooting from tanks near Chernobyl.