step 1- when i press "uup_download_windows" for like this example "19043.1110_x86_pt-pt_multi_399a40db_convert_virtual" it creates an ISO but the build is going to 19041.1110. step 2- and when i use the multi_arch_iso.cmd it changes sometimes the build. i can have 2 iso, 32 and 64 bits with the build 19043.1110 (when the step 1 creats the iso in the proper version) but after joing the 32 and 64 bits sometimes it goes for the build 19041.1110 anyways.. so, somethimes the step 1 doesnt work properly, and when it does and creates the proper build, the Multi Arch ISO does the same and but the wrong build in it..
Can anyone help check the wddm version in the latest 21h2? It can be done by simply typing dxdiag in start menu and check the display tab (like in the following screenshot). Much thanks!
Anybody Using 21H2 EP to update online system . kindly cross check three added p aria diagtrack tel reg keys. plus Some More Lock Screen Tel reg key value & its associated data added . Pl dont ask me for example . Just cross check if you are capable to do so . Thanks & Regards.
Your question is interesting. Windows 10 enablement packages look similar to the service packs of old. Instead of having Windows 10 service pack 1, service pack 2...service pack N, we have Windows 10 19041, 19042, 19043, and 19044. The pattern looks similar to service pack updates, but the base is Windows 10 19041. By 2025, we could have 1904X.4XXX, etc. Who knows?
Thinking about this more, maybe we will see 4 sub-builds per main build. If they want to make a major change beyond what a CU can provide they are going to have to do it through a new build and I can't see us making it to 2025 without changing anything in the core of Windows 10.
I agree. At first, I thought that Windows 11 might be an effort to change the core. But with further experimentation, I learned that you can substitute some Windows 10 components into Windows 11 and it still runs. For example, you can substitute the explorer.exe from Windows 10 into Windows 11, and get some Windows 10 classic taskbar functionality. If Windows 11 is supposed to be a new core, it seems weird that some of these substitutions can be made. Secondly, Windows 11 can use Windows 10 drivers. So I'm unclear about whether Windows 11 is really a new OS.
Its funny you say that because I am literally doing a test right now where I am exporting all of the drivers from a native Windows 11 install after all drivers are updated and then integrating them into a stock windows 10 image to see if it installs without any device manage issues. I am not expecting any even though the graphics drivers are Windows 11 WDDM 3 and I believe the wireless drivers are also Windows 11 only.
Interesting find. Integrating WDDM 3 drivers from a Windows 11 PC into a Windows 10 image and installing on the same PC removed the WDDM 3 drivers and reverted back to the 27 branch. I can force 30 branch back on but the installer itself rejects them.
The original Windows 10 drivers may work better with the "stock windows 10 image." I haven't looked at swapping the drivers back and forth, or which ones migrate and which ones don't. It is a curious study.
Then i would like to see the full UUP>ISO progress. As i've shown, that 19041 instead of 19042 or 3 should be fixed in the late(r)(st) version of the cmd inside the UUP>ISO project folder. The output filename for the mult-arch ISO should be correct but when not, it's just cosmetic and you can name it whatever you want.
Most important thing is which driver is stable and believe me i tested Microsofts integrated drivers vs others manufuctures chipset, wi-fi and etc. is 50/50, depends. You acctually must test by your own. For example i have GTX 1070Ti and the best driver is 451.67 - 09.07.2020. not NVIDIA 477.41 latest or oldest, because of RTX support. (1070Ti doesnt support RTX for instace.) Anyway, let's wait tonight for MSDN ISO's July Update