I tried to make a build with a SunLion tool based on 26100.1742 with Windows11.0-KB5054156-x64.msu and Windows11.0-KB5054148-x64.msu updates, supposedly promising to be 25H2. But in fact, it turned out to be Windows 11 IoT 24H2 LTSC [26200.5510] x64 RU without any special changes. Judging by the update size of 3.8 Gb, I hoped that it would be something completely new, but in fact - everything is the same!
I believe that to change to 25H2 they should release a new enablement See here: https://forums.mydigitallife.net/threads/windows-11-hotfix-repository.83741/page-144#post-1874226
I see, well I wasn't interested in this topic at all, and then I see an update for 26100.1742 to get 26200.xxx. Judging by the size of the update of 3.8 GB, I hoped that it would be a completely new OS. But it turned out that it was the same modified ten from 2009. It is not clear what they updated there with such a huge, in size, update?!
It is not entirely clear who the question is for and what you meant by the question about drivers? Personally, I have no problems with drivers. With the OS installed, I use a script to create an archive of all drivers installed in the system in a folder on the "D" partition, and after installing the newly installed OS, I use another script to install them all at once. It's fast and very convenient, in my opinion. Spoiler Backup of system drivers 1. Create a Drivers folder on disk "D" Code: C:\Users\Alex>D: D:\>cd D: md D:\Drivers 2. Create a backup of drivers in the Drivers folder on disk "D" Code: dism /online /export-driver /destination:D:\Drivers 3. After that, a copy of your system drivers will appear on disk D. After reinstalling the system, enter the following in the command line as an administrator: Code: pnputil.exe /add-driver D:\Drivers\*.inf /subdirs /install 4. As a result, within a few minutes you will receive a system with working drivers for your machine.
By the way, if you place this .cmd file, in your case, in the $OEM$\$$\Setup\BAT\ folder, then the process of installing previously saved drivers can be made automatic. That is, they will be installed during the OS installation from the previously saved Drivers folder. Spoiler Code: @echo off for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do (if exist "%%i:\Drivers" set "Drivers=%%i:\Drivers") pnputil.exe /add-driver "%Drivers%\*.inf" /subdirs /install exit /b But there is one BUT: earlier, on versions 23H2 and earlier versions of 24H2 I successfully used this script and it worked without any issues. But on the latest versions of 24H2 for some reason it does not want to work - the installation process hangs at the place where this script is being processed. Why, I do not know and do not understand. Since you have much more experience in scripts than I do, perhaps you see the reason for this installation hang on the latest versions of 24H2 in this code?
I'll try to create an automatic installer and make it available for you to test. My logic would be to unzip the script to a folder in C:\ and the script would be executed from there, removing everything at the end. A few experiments here work well. Let's see... I need you to tell me the path to the Drivers folder in your case, please.
Okay, so it is indicated both in my description and in the script itself. The path can be any, but in my case it is: D:\Drivers\
I looked, everything worked for me personally. But in essence, in the end, the same .cmd file was used that I used. Only I used it in external mode, and in your version it is used in semi-automatic mode. In your case, the result was the same, but a more complex approach to it, as for me.
Sadly, a trend that is never going to reverse direction, or even slow down. Worse Microsoft has made it clear that more integration, dependency, and less user configuration is intentional; Windows Next will likely be a built on immutable encrypted blob files you can't open or edit if Microsoft's Marketing Weenies have their way (as they have so far) -- it's not a terrible idea to be ready ready for an outcome like this with some alternative operating system... To get an idea of just how bloated Windows 11 is at over 100 million lines of code now (and just take a look at your 'slimmed' install size it's not that much smaller or that much less ridiculous than the defeat) -- even some of the most aggressive slimming projects like Tiny10, Micro11 and their more accessible counterparts like Slimdown10, and Revision have still have may times the bloat of a just an operating system that doesn't have the user hostile malware, spyware, adware, and toiletware. ReactOS -- both it's install media and installation max out at only 130Mb which includes all the self-hosting tools and source code for building and modifying the OS, a slimmed install is less than 90Mb. If you're not familiar with the project; ReactOS it's a FOSS Windows NT kernel compatible OS, that's ultimate design goal is to be Windows compatible with drivers, applications, utilities and games, I posted a little blurb about the latest update here. Sadly Linux distros are getting grotesquely bloated too; you have to go looking for a lightweight distro. Fortunately there are a lot of them -- some that are very popular and good like DietPi, Bodhi Linux, Puppy, Slax, TinyCore -- all, are typically less than 1/10 of Windows 11 install, have no malware, spyware*, telemetry and in many cases run Windows applications and games under emulation better and faster than Windows because they don't have the bloat and scamware overhead.. IMHO Microsoft jumped the shark with Windows 11, even if you 'slim' it and remove applications like Edge -- there are still tens of thousands of files that can't be removed because of kayfabe dependencies, massive registry files that are always loaded in memory with tons of useless data the OS and applications you chose will never use, plus all the user hostel crap you can't remove but can only block. If you contemplate where Microsoft and the governments of the five eyes countries want this to go (and it will go), this is not a happy ending for the User, and tools like Slimdown10 and ReviOS will continue to be less and less effective. If Windows games and applications on Windows, is a 'have to' thing -- Obi Wan SunLion and Windows 10 LTSC IoT are our only hope, and even that will end somewhere from 2027 to 2032 depending on what you'll put up with... Microsoft and five eyes governments intend to take you to a very dark place -- they've literally promised to... Intellige quid agatur Понять, что происходит * Even the Linux kernel has five yes back doors, to totally GTFO you'd have to use a different kernel, like GNU/Hurd on Debian, that so far, doesn't allow any of this crap...
Well, why, for example, Windiwd 11 G is practically devoid of all the terrible things you wrote about above. The only problem, personally for me, is that it is not localized in ru-RU. Or rather, it is localized without difficulty, but after localization it does not work. If I found a way to localize it in the language I need and it would not disrupt the operation of this OS, then personally I would not want to use another version of Windows.