Does anyone have the psf files for 21382.1000 and 21390.1000 in all three archs? (x86, x64 and arm64) I aim to use these files for experimental purposes i got no idea why they are excluded on uupdump, thats why i have to ask, otherwise i would've gotten them myself =/
I created a clean install.wim by installing in audit mode with Hyper-V, updating, generalizing, then capturing the image and creating an ISO. It works well.
This one should work fine with type="PA30" files. Tested OK with 21382.1000 and 21390.1010. @abbodi1406 Edit: recompiled .NET 2.0 version
How disappointing. MS is simply incapable of creating a new OS. Icons, colour schemes, desktop backgrounds and maybe a new mouse cursor are basically all they can do when talking about major OS advancements since 2006. ...Windows Vista, MS's most successful OS ever. They still have it underneath Windows 11! God that's so sad to think.
LOL I bet there's still NT 3.1 code somewhere in there. Thing is... One of the major features Windows has and the reason why businesses love it is it's backward compatibility. They can't just remove legacy components like that without major breakages. Actually... Windows 11 has already broke Intel's Chipset INF Utility -- it won't install under 11... Just gives you an unknown error. They are slowly removing legacy code, but I think that will take several years
nothing of value was lost then, all it did was show fancy names in device manager it didnt include actual drivers
It is. If you install some packages manually.. (there is a tutorial somewhere...) You unlock 21H2 branding and build bumps up to 19044.
But Windows 10 is on its final 4 years of support... So I don't expect any major updates for it anymore.