Well, what's the point of clinging to something morally obsolete today (21-23H2). Especially since in the fall MS threatened to roll out 25H2. We need to live today and not drool over what was once, long ago ...
I updated the script again, this time to version 226x1.5771. Fixed the issue with WindowsSearch (not tested yet). see the topic below.
================= 23H2_Integrator_10.8 ================= - Updated the 23H2_Integrator to version 226x1.5771 - Added option to integrate or not with 23H2 Enablement. So you can choose 22621 or 22631 - Updated UUP\all.txt - Updated UUP\Appx - Add my 22H2Tweaks NOTE: If you don't want to apply any or all of the tweaks, simply remove the PersonalTweaks\22H2 folder. Or remove the tweak(s) you don't want to apply - Windows Update is now disabled during installation. Use ToggleWindowsUpdate to enable Windows Update (Utilities) - Other minor adjustments https://forums.mydigitallife.net/th...ic-legacy-windows.86552/page-127#post-1874681
@SunLion Tested new script, search is all good now, still having trouble with modern calc, installs though refuses to open!
I just ran another test with 22621.525.220924-1448.NI_RELEASE_SVC_IM_CLIENTBUSINESS_VOL_X64FRE_PT-BR.ISO, and everything works fine, without errors. See the attached Modern Calculator image. To understand what might be happening to you, I need the log file for review.
Hey SunLion, are you calling the Windows 11 spin of Slimdown10 "23H2_Integrator" because it integrates so many contributions to getting the poop out of Windows 11? I hope I didn't misrepresent your intentions here, and will fix it if I did...
Don't worry about that. There are actually three scripts: 23H2_Integrator for versions 21621/21631 24H2_Integrator for version 26100 The ones above, which deal with Windows 11, are discussed here in this thread, as I didn't want to mix them with the one below. SD10_Renewed, which is exclusive to Windows 10, is discussed in the other thread: https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/
Thank you SunLion for your endless endeavors on this project. It lets us have good choices on different MSFT Windows.
Second test with10.8 again, Ran the finished image in a VM this time not using an unattended answer file, no images available?
I didn't notice any errors in the log file. This type of error occurs when the Autounattend.xml file doesn't correctly indicate the image being processed. In this case, it was my fault, as I attached the Autounattend.xml I was testing with an Education version. This will conflict with another edition during installation. I'm fixing this in the package as well. Below is an Autounattend.xml that applies to all editions. Please try using the attached Autounattend.xml and see if it works. Please let me know if it went well.
===================== 23H2_Integrator_10.9 ===================== - Updated the 2xH2_Integrator to version 226x1.5840 - add autounattend.xml for use with all editions - add option for remove WinRE.wim in Default mode - Added option to integrate or not with 23H2 Enablement. So you can choose 22621 or 22631 - Updated UUP\all.txt - Updated UUP\Appx - Add my 22H2Tweaks NOTE: If you don't want to apply any or all of the tweaks, simply remove the PersonalTweaks\22H2 folder or remove the tweak(s) you don't want to apply - Windows Update is now disabled during installation. Use ToggleWindowsUpdate to enable Windows Update (Utilities) - Other minor adjustments Test with: 22621.525.220924-1448.NI_RELEASE_SVC_IM_CLIENTBUSINESS_VOL_X64FRE_PT-BR.ISO Please read the README.txt file before doing anything! Good luck! https://forums.mydigitallife.net/th...ic-legacy-windows.86552/page-127#post-1874681
Hello, everyone! I didn't really look into this issue before, but then I took a closer look at the code provided by our colleagues and saw that there is basically no difference between “Default” and “Slim.” The only difference is that in the “Default” version, the functions processed by the script are selected manually, while in the ‘Slim’ version, some of these functions are performed automatically. So why not expand the user “Menu” so that the user can flexibly configure the script to work with the functions they need from “Full” to “Lite”? https://forums.mydigitallife.net/threads/slimdown10-–-turn-windows-10-22h2-or-ltsc-2021-into-classic-legacy-windows.86552/page-168#post-1887272
Thank you! I in my scripts and the layout of the tool itself always strive for their usability and transparency for the end user. So that it would be as convenient to use as possible and there would be nothing unnecessary (not clear) for the user on the desktop. That's why I leave open only those folders and files that are really necessary for the unskilled user - everything is extremely simple and clear. But everything I do, I do thanks to what I learned from you Sergey, from SunLion, from comrades from MDL resource. For what all of you thank you very much!
Hi Sainfo! Thank you for your kind words. It's very nice to read that my advice and were useful and helped in your work. You are a great guy for making everything as convenient and understandable as possible for the end user - it's worth a lot! In fact, we all learn from each other, and I also learned a lot from you and other guys from MDL. Therefore, your gratitude is especially valuable to me. I am sure that your tool will turn out even cooler and more in demand! Good luck to you in developing the project, and know - if anything, I am always here, I will help as much as I can.