We don't need those domains, as they cannot be verified as safe. The only safe domain that everyone here knows to create a windows iso, is from uupdump.net.
Let me see if I got all of these right... 1) The iso made by the mct includes one specific esd file and nothing is added to it. 2) There is no prompt asking for w11 on the the animation and the screenshot below, although the update in question was installed. Why is that?
Does somebody have a download link for the fr-fr_windows_10_consumer_editions_version_22h2_updated_nov_2022_x64_dvd_8daa9789.iso file please ? Thank you very much in advance.
Yes, nothing is added, the ESD contains a certain build and it is converted to ISO. Why do you think there should be win 11 offered after the OOBE update was installed? It actually mentions win 11 on WU update but the VM is not compatible, so without certain patching methods it will never be offered for installation. In the past MSFT provided the upgrade to the newer major build during OOBE but that was when the initially installed build had reached EOL.
First of all, sorry for not replying earlier but the last couple of days on my end have been hard. The forementioned update applies to w10 from 20h1 to 22h2. I hope that this bit answers the "why" part. The bigger concern from that "why" for me is that a lot of average/below everage users (with compatible hw that is) will see the prompt and will probably percieve it as a "10+1 offer" from ms, so they will upgrade to w11. And the fact that the update is available for versions that are eol since ~1 year ago (20h1) and thus no update since then, means that ms is also targeting the users who (for any reason) are (un)intentionally at those versions. About that last underlined part, ~1 year ago I saw a system that could not be past 20h1 with any means (even the in place upgrade from the iso failed for some reason). I saw that system again recently (~2 months) ago and it was somehow at 21h2! I do not "think" it should be offered, ms thinks so with that update. Imho, they searching for new users to test w11. Also, I assume that the upgrade to w11 was not offered during oobe on your installation is probably due too the vm's incompatibility, e.g. no tpm support. Last but not least, please consider that the oobe screen does not come up on new installations only, it comes up after major upgrades too... or whenever windows feels like it. p.s. If I had a modern pc, I would test it on a vm myself and with ANY configuration possible. Unfortunately, I can't, that's why I asked.
Having an issue going from x64 LTSC .1288 to .2311, rebasing, disabling all features (except DotNET), and then re-basing again. DISM Component Store becomes corrupt. It becomes corrupt after after rebasing second time (after disabling features). Is December update supposed to come out tomorrow?