========================= 2xH2_Creator_15.7 ========================= Updated to 26x00.8116 - Add Get-Features and Get-Packages at the end - Added code to identify the image version at the end (26x00.xxxx) - The _CreateISO.cmd script has been corrected to create the image with the name, for example: W11_26100.8116_x64_pt-BR.iso - Updated all.txt - Other minor adjustments https://forums.mydigitallife.net/th...to-classic-legacy-windows.90039/#post-1872013 Enjoy
Hello, I’d like to ask you a question—perhaps a silly one: in your script, you constantly use the “Disable Windows Search” function. My question is: why? Isn’t it convenient to work without search? Or is this done so you can use an alternative search engine? In that case, what’s wrong with the standard search?
The search of the new system is not just about file search, but also includes updates, ad recommendations, and online searches, which are very resource intensive.
After applying the script, creating an ISO and installing Windows, when is needed to repeat all these? Is Windows Update enabled and can undo changes done by the script?
Hmm, so maybe it makes sense not to disable Search entirely, but just to turn off the features that put such a strain on the your system: updates, ad recommendations, and online search? P.S. Apparently, all this applies to PCs from the early 2000s, because, for example, on my system, Search doesn’t put any load on the system at all, according to the tests I’ve run.
Disabling it is recommended, as it will not affect other functionalities. This is especially true in a general way for users of all knowledge/experience levels.
There's no way to undo the changes you made to create the ISO, unless you redo the process with new settings. Here I create a new image with each new update, so I always have an up-to-date ISO. But that's up to you. Windows Update is enabled for normal operation. You can disable it by running the ToggleWindowsUpdate utility.
========================= 26H1_Creator_1.6 ========================= Updated to 28000.1764 - updated all.txt for version 1764 https://forums.mydigitallife.net/th...to-classic-legacy-windows.90039/#post-1872013
Sometimes there are several updates released in a month, do you create a new image with each of them? But, it's not necessary to install again and again Windows, but just use Windows update?
Yes, you can simply update through Windows Update and everything will be fine. What I said is that I create a new image whenever new updates are released just to have a more recent ISO as a backup for any eventual needs. But you don't need to do this frequently.
Thank you very much for both your appreciated reply and work! However, I'd like to know something else... Comparing what I've been used to for a few years now, I've created an ISO of W10 Iot LTSC 2021 that meets my needs, running "Slimdown10_v2_02" and then, if I want to reinstall, I simply extract the contents of the ISO file that results at the end of the process to a "setup" folder on another partition and run the "setup.exe" file existing in the folder root. With the above, I can reinstall Windows 10 or do an in-place upgrade, and I like it that way. Unfortunately, I still haven't figured out what to do to complete the process started by the "2xH2_Creator_15.7_Start.cmd" script. Furthermore, I didn't manage to read your valuable advice in the instructions about the preferability of using "2xH2_Creator_15.7_Start_Nsudo.cmd" rather than "2xH2_Creator_15.7_Start.cmd" when using Windows 11 ISO. Anyway, let one thing be clear: the above is not and is not intended to be a "criticism" of any kind, but simply to express my slight frustration at not knowing what to do. So I would kindly like to know what to do. Thank you again.
Try the attached modified script and see if it works as you want. The Reduce Sources code has been removed. Therefore, nothing is removed from the sources folder.