================== 23H2_Integrator_10.8 ================== - Updated the 2xH2_Integrator to version 226x1.5768 - Updated UUP\all.txt - Updated UUP\Appx - Add my 22H2Tweaks - Other minor adjustments Please read the README.txt file before doing anything! Good luck! https://forums.mydigitallife.net/threads/slimdown10-–-turn-windows-10-22h2-or-ltsc-2021-into-classic-legacy-windows.86552/page-127#post-1874681
NSudoLC.exe LC = Light Command Line This is a "light" console version. Works only via the command line. No graphical interface. Ideal for scripts (Batch, PowerShell), where you need to run commands/scripts on behalf of TrustedInstaller, SYSTEM, etc. NSudoLG.exe LG = Light GUI This is a version with a graphical interface. Allows you to select from a list which account to run under (TrustedInstaller, SYSTEM, Admin, etc.). Convenient for manually launching applications if you don't want to write commands. Total: NSudoLC.exe — for scripts and automation. NSudoLG.exe — for manual launch with a selection window. The keys for NSudoLC.exe and NSudoLG.exe are the same. The only difference is how they are launched: NSudoLC.exe immediately waits for a command with keys (clean console). NSudoLG.exe will open the GUI, but it still understands the same keys if you pass them via the command line. Example: NSudoLC.exe -U:T -P:E "%~dp0Default.cmd" The same can be done with NSudoLG.exe, but then: NSudoLG.exe -U:T -P:E "%~dp0Default.cmd" But most often NSudoLC.exe is used in automation, because the GUI version sometimes just opens a window instead of silently launching. Here are some examples: :: Getting Admin Rights by Run Script as Trusted Installer with nSudo or MinSudo or PowerRun if /I "%~1" neq "asTrustedInstaller" ( title Run "%~nx0" Script as Trusted Installer... if /I exist "Bin\%arch%\nSudo.exe" ( rem if /I exist "Bin\%arch%\PowerRun.exe" ( rem if /I exist "Bin\%arch%\MinSudo.exe" ( for /f %%# in ('dir /B /A:-D "%~nx0"') do ("%%~dp#Bin\%arch%\nSudo.exe" -U=T -P=E -CurrentDirectory=%%~dp# "%%~f#" "asTrustedInstaller" "nSudo") rem for /f %%# in ('dir /B /A:-D "%~nx0"') do ("%%~dp#Bin\%arch%\PowerRun.exe" /WD:"%%~dp#" "%%~f#" "asTrustedInstaller" "PowerRun") rem for /f %%# in ('dir /B /A:-D "%~nx0"') do ("%%~dp#Bin\%arch%\MinSudo.exe" -U=T -P=E -CurrentDirectory=%%~dp# "%%~f#" "asTrustedInstaller" "MinSudo") ) else ( echo. echo. echo.Run "%~nx0" Script from IntegratorW10 folder. echo. TIMEOUT.exe /T -1 ) exit ) The commented lines are alternative check options for PowerRun or MinSudo. You can uncomment the line if you want to use another utility. This block automatically restarts the script via nSudo / MinSudo / PowerRun. After restarting, the asTrustedInstaller parameter is added to the script so that it understands: (I already have the necessary rights, I can continue working.) Convenient, because you can write the main code below this block, and access will be guaranteed.
@SunLion I enabled search, though not working. Code: =========================================================== 23H2_Integrator_10.8 Configured Options at Sun 08/24/2025, 6:24:33.65 =========================================================== Running in NORMAL mode Creating Default image Disable Store Enable WindowsSearch Disable Windows Defender REMOVE Edge completely Do Not Enable NetFX3 Enable Modern Calculator Do Not Enable MediaPlayer Integrate Dart into WinRE.wim Manual Installation Openshell Integrate 23H2EP Install ClassicPaint by win7games Remove Windows Ease of Access Show ThisPC + Bin + User + ControlPanel + Network Icons on Desktop Apply PersonalTweaks ===========================================================
I will pass. I will be sticking with release of SD10_Renewed_1.30 or 24H2_Integrator_12.7. W10 Pro and W11 23H2 Pro same expiry (Oct 2025). At final, only 24H2 remains.
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.