Hello. What benefits does Slimdown11 offer me if I'm already using the LTSC version? The LTSC version is already more or less free of unnecessary bloat.
This is a fair question. You are right — LTSC is already much cleaner than Home or Pro. It has fewer apps, no Store, no Cortana, and less extra software. But a debloater (generally) can still help in some ways: · Privacy: It can turn off telemetry, feedback, ads, and tracking tasks that are still in LTSC. · Background services: It can disable scheduled tasks and services you do not need. This may save RAM, CPU, and disk usage. · Extra apps: LTSC has fewer apps, but it may still include some like Edge, Media Player, or old components. A debloater can remove them if you want. · Optional features: It can remove Windows features you never use, like Internet Explorer or old PowerShell versions. Be careful with this. · Cleaner Start menu and search: It can disable web search, Bing results, tips, and suggestions. · More control: It can apply many privacy and performance settings at once. · Consistency: If you set up many PCs, it can make them all the same. But if LTSC already works well for you, you may not need a debloater. It is optional. Always review what the script changes. Make a restore point or backup first. Do not remove things you might need later. Have an ice day. Cheers
I'm excited about it too, it almost makes Windows 11 IoT LTSC bearable for me, I added it to The FOSS Windows De-Bloat/-De-Poop Sliminator Repo -- hope you: decide on a license for it GNU, MIT whatever you like so no one's toes get stepped on, host it on GitHub and/or make a thread just for this! You have more than enough going on here that's unique, does with other projects can't, don't or won't that this should be stand-alone now to get it more attention and focus! Thank you sainfo for your hard work here!
Thank you very much for your kind words! This is my latest project in .cmd and PowerShell. My next tool for working with images will be written in C++. I’m currently working intensively on this. When I’ve achieved a positive result, I’ll of course share it with my fellow users on this site.
Not kind, just honest -- this is an amazing amount of work, especially that you appear to have addressed language issues that challenge cleaning up Windows. Very impressive!
The tool is designed to work with W10 or W11 ISO images in any localisation. If you are using Windows 11, use build 26100.1742 in any locale; if you are using a Windows 10 ISO, the graphical menu will automatically switch from Windows 11 to Windows 10. The final DVD distribution or ISO image will be in the same language as the source ISO image used.
error and close the program...I disable the AV...I let the default settings. Spoiler ========================================================== WimDirector 5.2.0 (Modular Architecture) ========================================================== [*] wimlib: C:\Users\RAYMAN95\Desktop\WimDirector_5.2.0\Data\Tools\amd64\wimlib.exe [*] oscdimg: C:\Users\RAYMAN95\Desktop\WimDirector_5.2.0\Data\Tools\amd64\oscdimg.exe [*] Checking and flushing old build outputs... ---------------------------------------------------------- [sub_Detector] Analyzing input staging target... [Target] ISO Container: 26100.1742.240906-0558.GE_RELEASE_SVC_PROD1_CLIENT_X64FRE_EN-US_FR-FR.iso [Airlock] Extracting bootable ISO container contents... [Airlock] Original ISO deleted: 26100.1742.240906-0558.GE_RELEASE_SVC_PROD1_CLIENT_X64FRE_EN-US_FR-FR.iso [PASS] Staging source target evaluation sequence finalized successfully. ---------------------------------------------------------- [*] Launching advanced deployment configurator matrix... [*] Exporting selected index metadata layer to deployment storage pool... [PASS] install.wim exported: 4107,45 MB ---------------------------------------------------------- [sub_Boot] Initializing out-of-box boot.wim total rebuild sequence... [*] Extracting setup wizard layout (Index 2) directly to workspace... Applying image 2 ("Microsoft Windows Setup (amd64)") from "C:\Users\RAYMAN95\Desktop\WimDirector_5.2.0\Data\Temp\boot.wim" to directory "C:\Users\RAYMAN95\Desktop\WimDirector_5.2.0\Data\Temp\BootMount" Creating files: 25242 of 25242 (100%) done Extracting file data: 1241 MiB of 1241 MiB (100%) done Applying metadata to files: 25242 of 25242 (100%) done Done applying WIM image. [*] Executing architectural debloat sequence... [TakeOwn] Resetting security maps for protected directory: SysWOW64 ![PIPELINE CRITICAL CRASH]: Erreur : Syntaxe incorrecte. La valeur « y » n'est pas autorisée pour l'option « /d ». To finish, press Enter...:
The tool is designed to work with ISO images conforming to the 26100.1742 standard, regardless of localisation. Using the tool is extremely simple: extract the archive to any partition, place the ISO image in the root directory alongside the Runme.cmd file, place the latest cumulative update in the UUP folder, run Runme.cmd as an Administrator, select the functions you require from the graphical menu, click Start – and wait for the script to finish... Note: the tool does not care which host your ISO image is on or which localisation it is, so if you are using Windows 10, you should use the cumulative update for that version. The script will automatically switch the menu from Windows 11 to Windows 10.
it seems that my updates caused this..i download update 26100.9177 from uupdump and put in the folder... iso compiled now.. but not the time to flash..
Is this project the best way to create an iso that is user selected debloated and ready to do an in-place upgrade or is there a better script?