I've examined your posts and your observations are interesting. The shared mistakes between MVS and UUP ISOs combined with identical file comparisons have lead you to believe that there is very little difference between the MVS and UUP ISOs. That would would lead me to think that converted ESDs and Techbench ISOs might be better?
my observations might totally miss the mark, does not change anything iso's released by microsoft remain the preferred install media for the simple fact that you can check beforehand for corruption via known hashes other than that, it makes little difference if you use mvs / techbench / mct / esd2iso / uupdump - all source files come from microsoft better? guess that would be using sfv diff files to update mvs iso's from one release to another, with minimal download size and processing, and verifiable hashes the only inconvenient is watching for the right language svf to be made available by the fine folks here at mdl then, to each one's needs. - no secret I'm a fan of the mct (in-place) upgrade-repair route and then do updates online. whenever I get a call about helping with broken lcu updates in 10, or nagging with 7, I just direct people to download the mediacreationtool.bat script, rename it auto mediacreationtool.bat and the just run it and sit back until windows is back at desktop. usually successful (quite many people went the posready route for updates convenience, and mct don't like that, but I've already made an workaround) - specific editions mix and integrated updates? early releases? any past-release specific-build? uup-dump all the way - wim editing? mvs / techbench - gargantuan all-in-one project? esd2iso and similar scripts
It is preview which means "optional" under the old terminology and not the recommended release. Anything released outside of the second Tuesday of the month schedule (with very few exceptions) is not recommended for regular use.
i just installed KB5000802 on windows 10 20H2 , is it safe now to install this? as i heard earlier it was buggy.
Actually, there's literally no such thing as "not recommended for regular use." when these updates are in fact fully tested, and supported by Microsoft. They're not Insider Preview updates, and they're simply for you (not Microsoft) to test these changes more earlier which will then roll into the next Patch Tuesday update, and are completely optional. Whatever you get from Patch Tuesday, are more or less the exact same changes coming from those "Preview" updates. I get it that the word "Preview" is slightly misleading here for some people, but I'm not one of those people here that are responsible for what marketing names Microsoft should choose.
They are optional for a reason. Like the .NET Framework updates released outside of the patch Tuesday.
If one examines the Windows 10 Pro Index for all the 19042.631 ISOs, the Directory Number and File Number is exactly the same for every 19042.631 ISO. Media Creation Tool (MCT), Techbench, Windows ISO Downloader, ESD > ISO, and Microsoft Visual Studio (MVS) ISOs all have the following structure for Windows 10 Pro: Directories=24132 Files=96477 Since the version and build are the same (19042.631), the edition (Windows 10 Pro) is the same, and the architecture (x64) is the same, I think it's safe to say that these are all very similar ISOs. ISO size (in bytes) may vary and SHA256 hash may vary, but the ISO structure is the same. UUP ISOs were not included in this study because they are custom, homebrew, a waste of my time. Spoiler: Comparisons Media Creation Tool (MCT) = Techbench = Windows ISO Downloader v19042.631 Windows Pro Structure: Directories : 24132 Files : 96477 ISO Size=6,221,846,528 Bytes SHA256=6c6856405dbc7674eda21bc5f7094f5a18af5c9bacc67ed111e8f53f02e7d13d Microsoft Visual Studio (MVS) v19042.631 Windows Pro Structure: Directories : 24132 Files : 96477 ISO Size=6,015,029,248 Bytes SHA256=fe029f3d94ffc3550312bfac48eaa01a87946a0792f8e34196a6252065e2c5fb ESD>ISO v19042.631 Windows Pro Structure: Directories : 24132 Files : 96477 ISO Size=Varies depending on conversion tools (ESD>ISO, NTLite, DISM++, etc.) SHA256=Varies
All of those are the same, why comparing them, only content of ESD and ISO differs at the available SKUs. UUP is the one to investigate and to be compared to all others, it contains less fod's then the others and has a self constructed boot.wim. The ISO of the ESD>ISO conversion is considered homebrew too, same as with UUP>ISO.
dear @Enthousiast : does this build have any serious irregularities to be concerned about? (for an average user) How this build is faring here with MDL members?
For me, UUP dump is worth the time, because of the ease of use. As for the time taken, I just leave it unattended for an hour or so The thing I like most about UUP dump is its ability to add virtual editions.
Must say your win7 activation script tool is working like a charm on latest intel machines for offline permanent activation. UEFi with GPT disk layout & CSM enabled machines .Great Job brother n Thanks a lot.
because you don't even know what telemetry is if you think all telemetry is just "constant spying" ... you wouldn't be spreading misleading information here otherwise. That was never how telemetry worked and that was never the purpose. You can go ahead and file an EU GDPR complaint about what's being collected in Windows 10 or other products. You know what? You won't go anywhere with that. When Microsoft says that the telemetry is "anonymous and includes no personal identifiable information." they really do mean it. This is something that you don't clearly understand. Everything that's being collected can be viewed in the Diagnostic Data Viewer application. It's the same data that's being sent back to Data Analysts at Microsoft, the people that are responsible for viewing such data and working with Software Engineers and Program Managers to solve issues. It has nothing to do with ignorance, I'm one of the few people here, as a developer, that utilizes telemetry to improve applications. Turning that off prevents us from making any enhancements or changes. Do you want a broken application or OS when there's no crash logs being sent? Did you know that games also submit crash logs to so the developers can fix whatever issue that crashed the game? If you think that an idiot in the r/privacy subreddit (who has no idea how to use Fiddler properly which was originally written by someone here at MS) is smarter than me, then that's on you. It's the reason why I don't engage with r/privacy people that much because all they think about is: Calculator is "bloatware", "Start Menu is "bloatware", Trackpad driver is "bloatware", Camera is "bloatware", etc. Telemetry and bloatware are two words that have lost its meaning overtime, all just because people use it in the wrong context as possible. Just wait till you find out that Windows 8(.1), 7 and older OSes, including LTS(B|C) also have telemetry. Now, what you're going to do? I'm also not sure how you think that Microsoft from decades ago is still the same today, when it's actually not. If all you care about is complete 100% privacy, then you're better off cutting your ethernet cable rather than arguing with someone who in fact uses telemetry to do what I've stated above. You're already losing half of your privacy by being online.