For testing purposes only, please remove MicrosoftWindows.Client.CBS [line 3049] from the code below, save and run again.
Authoritative sources (I just read it yesterday, I won’t look for them now, take my word for it) think differently. They claim that only the first versions - clean ones - should be taken as a blank. That is, in our case this is version 26100.1 en-US. Personally, I trust their opinion and therefore, basically, I work only with the original source (26100.1). Result: I never have any problems at all with the resulting assembly, and I wish the same for you!
I agree, but it is also necessary to try everything possible. Using source 26100.2605 might just require a little tweaking of the script, which is worth a try.
Of course it's up to you, you're free to do as you wish. My personal opinion is that it is not worth it. You should realize that the script itself has nothing to do with the workpiece number. In other words: it does not care what you give it 26100.1 or 26100.2605. But 2605 has already had a bunch of updates applied to it and you can't claim that they are all problem-free. But if you use the original source, 26100.1, as a starting point, you get a more stable result. IMHO But you, of course, do as you see fit, it's your right.
I have tested your suggestion against ISO sources: 26100.1.240331-1435.ge_release_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso Although the script runs successfully, the result is still the same, asking for drivers at the beginning of the setup.
ok, i have tested the source iso: SW_DVD9_Win_Pro_11_24H2.2_64BIT_Eng_Intl_Pro_Ent_EDU_N_MLF_X23-92021.ISO [10.0.26100.2605]. unfortunately, the result remains the same. The ISO still asks for the driver at the beginning of setup.
Yes, I did the same and the error persists... I believe the problem is not the version, but some setting in the Bios. I'm researching...
Damn, you're like little children! Look, leave this boot.wim file alone. You don’t need to carry out any actions on it, especially completely unnecessary actions, and you will be happy!
Exactly! I just ran several tests and it was confirmed that the problem is in the boot.wim edition. I modified the script by removing these boot.wim editions. If anyone else wants to test it, just put the script in the same folder as 24H2_Integrator_7.8.7 and run 24H2_Integrator_8.0_Start.cmd as administrator. password: mdl2025
The SKUs that exist in the CONSUMER version also exist in BUSINESS, with the exception of Home. BUSINESS has Enterprise, which is not present in CONSUMER. Additionally, we would have one more choice in the script, in addition to having one more ISO in the folder.
Please see the thread above, with the new corrected script. https://forums.mydigitallife.net/th...ic-legacy-windows.86552/page-113#post-1870289 The problem was caused by editing the boot.wim. This was removed from the script and in my tests it is now working...
Thank you so much, @SunLion! You've done it! All the settings are back to normal, and everything is working like a dream!
In the case of Windows 11, I discovered something interesting. Tested on Ventoy and confirmed... I'm finishing a new adjustment, this time to improve the cleaning of install.wim, which didn't work very well... I especially ask @sainfo to do the tests, please. I created two cleaning modes, one with nsudo and another with takeown... I'm still finishing... I'll publish it soon... Here are the scripts for testing: password: mdl2025