It works that way too. I usually create my tools with a shortcut in Utilities, and when I need them, I just click on the shortcut there and everything opens.
@SunLion, hi I have a few questions. 1. As far as I understand correctly, I as a user can add my files to the respective "BAT" or "REG" folders at my own discretion. Does this mean that the files I added in these two folders when using SD10_Renewed_1.59-small_Start.cmd will automatically be added/imported/installed?! I opened the SD10_Renewed_1.59-small_Start.cmd file and inside I saw that it specifically listed exactly which BAT files and which REG files to use. For myself, I have exactly 22 REG files and I'm not sure if in the process of running SD10_Renewed_1.59-small_Start.cmd they will be automatically added. After the SD10_Renewed_1.59-small_Start.cmd process finished, I opened the LOG file and in it I didn't see any of the relevant files I added. So I have doubts that the files I added are not added/not installed/not integrated in the process of using SD10_Renewed_1.59-small_Start.cmd. That's why I'm asking to get a clear answer on what to expect and how to properly understand by meaning. 2. Please clarify: Can CMD files be added to the BAT folder or is this BAT folder only for BAT?! I ask because I have exactly 3 CMD files and I don't know if the correct place for them is to put them in the BAT folder?! And in a sense, here again is the question like the above question whether the files I added will be added/installed/integrated in the process of using SD10_Renewed_1.59-small_Start.cmd. After the SD10_Renewed_1.59-small_Start.cmd process finished, I opened the LOG file and in it I didn't see any of the relevant files I added. I made 2 ISO files, looked in the SD10_Renewed_1.59-small.log, but there is not a single line inside that shows that the 22 REG files I added and several CMD and BAT files located in their respective folders have been added/integrated/installed. From what I can see, I don't think they are integrated/installed. Only @SunLion can give me a straight answer. :} 3. Regarding the file __Add your personal CMD tweaks here.txt - I think there is an error in this file. When this file is opened, the following is written inside as text: Add your personal CMD tweaks here *.reg" - it shouldn't say "*.reg", but maybe *.BAT" and/or "*.CMD"?! 4. After completing the process with SD10_Renewed_1.59_Start.cmd or with SD10_Renewed_1.59-small_Start.cmd, the file "19044.xxxx_EnterpriseS_Renewed.xml" is generated in the DVD folder. What is the functional need of this file?! Opening it up and seeing that it's data on your @SunLion host machine. My questions are - should this file be deleted, what is its functional need, and if it is completely redundant - maybe it is better to remove from the script its generation?! 5. Question about SD10_Renewed_1.59_Start.cmd and SD10_Renewed_1.59-small_Start.cmd regarding these two lines: "[ 1 ] - Run in DEBUG mode (updates are not integrated); [ 2 ] - Run in NORMAL mode (updates are integrated)". My question here is about the verb tense used. The confusion for me comes from what in translation is wrong for me because according to: [ 1 ] - means updates are not integrated; [ 2 ] - means updates ARE ALREADY integrated. In my opinion, future tense should be used for [ 2 ] because the updates WILL be integrated by the script. Last week I was selecting [ 1 ] because I was using the LTSC ISO in my language and option [ 1 ] was selecting it because in translation I understood that my LTSC ISO had no updates and that by selecting [ 1 ] the updates WILL be added when the script is run. I made last week 2 ISO files and I was wondering why the build remained the base one without any updates. And then I used option [ 2 ], which turned out to be correct as a choice, but as a translation I took it to mean that, for example, I have an up-to-date ISO and that no updates will be added. It's just that the script will only remove telemetry without making updates, because it says updates are integrated. Everyone translates it into their native language and it is possible that there are discrepancies in the translation, but for me the future tense should be used in position [ 2 ] because it concerns a process that has not yet been started by the script. @SunLion, I hope you won't take my clarifying questions for pettiness because my goal is to get maximum clarity, because both you (I see you're using pt-BR) and I use a non-English native language and it's possible that clarity in the answers gets lost in translation. I was under the impression that my suggestion from the previous page that you @SunLion implemented on this page met with approval from other users as well (regarding providing a lightweight version - SD10_Renewed_1.59-small.cmd).
Please wait, I will review and respond... Here are the answers. Answer 1: The .bat and .cmd files will be copied to the folder \Bin\OEM\$OEM$\$$\Setup\BAT The .reg files will be copied to the folder \Bin\OEM\$OEM$\$$\Setup\REG They will be executed automatically during RunOnceEx, through the script \Bin\OEM\$OEM$\$$\Setup\RunOnceEx.cmd No windows or anything else will be displayed. You can check your installed system by opening regedit and checking if the command was added or not. Answer 2: As stated above, both the CMD and BAT scripts must be copied to the BAT folder. The log file does not record this. The log file records all the operations of the script that is executed through the SD10_Renewed_1.59-small_Start.cmd script, that is, SD10_Renewed_1.59-small.cmd. To be clear: You must run the SD10_Renewed_1.59-small_Start.cmd file so that the SD10_Renewed_1.59-small.cmd script is executed in trusted mode with PowerRun. That's why the log will only record what was executed by the SD10_Renewed_1.59-small.cmd script. The only way to be sure that the command was applied is, as stated above, open regedit and check if it was applied or not. However, remember that some commands require elevated privileges and may not be applied in this way, but separately, using an additional tool, such as PowerRun, NSudo, or another. Answer 3: Yes, you're right. I forgot to edit the text. But that's correct. The BAT and CMD files should be placed there. Note: I've already corrected the text. Thank you. Answer 4: The file "19044.xxxx_EnterpriseS_Renewed.xml" is an NTLite preset that I use in my builds. I just add it to the DVD folder to remind myself to make those additional modifications. But, if you don't want to use the preset, you can delete the file that is in the \Bin\NTLitePresets folder, and it will not be copied to the DVD folder. Answer 5: I believe the misunderstanding stems from the fact that I use Google Translate, and it's not always perfect. But here's the thing: DEBUG mode should be used for testing, where updates are not integrated, resulting in a shorter testing time. NORMAL mode should be used to actually create your image with all updates integrated. That's all. And yes, the translation might cause some confusion. But if you have any difficulties, feel free to ask, and I'll be happy to answer. Finally, remember that there are two main scripts in the package: 1 - SD10_Renewed_1.59.cmd, which is the complete package with customizations. 2 - SD10_Renewed_1.59-small.cmd, which is the script you are interested in. Both have separate scripts that trigger elevated execution and automatically create the log file. 1.1 - SD10_Renewed_1.59_Start.cmd 2.1 - SD10_Renewed_1.59-small_Start.cmd (this is what you should do) Do not mix these scripts, as they are different.
@SunLion, thanks for the comprehensive answers. I haven't installed the created ISO to test it in practice. Regarding: Unfortunately my REG and my CMD/BAT files, which I added to their correct folders, after the end of the execution of SD10_Renewed_1.59-small_Start.cmd - are not in the folders you specified. Since I keep the DVD folder - I also checked in it: DVD\sources\$OEM$\$$\Setup\BAT and in DVD\sources\$OEM$\$$\Setup\REG. In this folder there is only "HideSearchBoxTaskbar.reg", which is not one of my 22 added files. Then I also checked in: Bin\OEM\$OEM$\$$\Setup\BAT and in Bin\OEM\$OEM$\$$\Setup\REG. In this folder there is only "HideSearchBoxTaskbar.reg", which is not one of my 22 added files. Which means that the REG and BAT/CMD files I added in question were not added by the script, since they are not in the folders you indicate that they should have been transferred to?! This worries me that something is wrong. Can it be checked without a real ISO installation in this case? About: Thanks for this clarification. So I can safely delete the entire "NTLitePresets" folder with absolute confidence. Regarding: Answer 5: I also use Google translate. Therefore I would recommend a slight edit in both scripts: SD10_Renewed_1.59.cmd and SD10_Renewed_1.59-small.cmd to change from "[ 2 ] - Run in NORMAL mode (updates are integrated)" to "[ 2 ] - Run in NORMAL mode (updates will be integrated)".
If the files are copied to the OEM folder then they will show up in the ISO, you don't need to install. [ 1 ] - Run in DEBUG mode (do not integrate updates into image) [ 2 ] - Run in NORMAL mode (integrate updates into image)
You're right, sorry. Since I use the same file and folder structure for both versions, I forgot to add those two codes to copy the files in the small script. Attached is the corrected SMALL script. Replace the previous one with this one. In the Bin\PersonalTweaks\REG folder there are three .reg files that are used in the full version. Please move them to the SRC folder inside the REG folder before copying your files. Test and see if it's copied. To verify, before proceeding when the settings summary is displayed, open the folders and see if the files were copied to the Bin\OEM\$OEM$\$$\Setup\REG or Bin\OEM\$OEM$\$$\Setup\BAT folders, as appropriate. Note: Both versions of the script have been corrected. Replace both.
@SunLion, thanks for the updated "SD10_Renewed_1.59.cmd" and "SD10_Renewed_1.59-small.cmd". Here's what I did: 1. In this Bin\NTLitePresets directory - I deleted the entire "NTLitePresets" folder; 2. In the Bin\PersonalTweaks\BAT directory - I added my few .CMD and few .BAT files to this folder; 3. In the Bin\PersonalTweaks\REG directory - I moved the three available .REG files and I placed them in the "SRC" folder; 4. In the Bin\PersonalTweaks\REG directory - I added my .REG files to this folder; 5. In the Bin\EXTRA\EXTRA directory - I deleted the entire "Office 365 ProPlus - Online Installer 3.3.11" and "Xbox-Installer-Repair_by_Metalwell" folders. 6. In the Tools directory I started PowerRun_x64.exe and I set it to "Allow command line"; 7. In the PersonalTweaks directory I edited the file "Autounattend.xml" - in both places I renamed the username to something else and I changed the time zone for my region; 8. In the ISO directory I placed my xx-xx_windows_10_enterprise_ltsc_2021_x64_dvd_b0887275.iso; 9. I started the file "_PreDownloadAllUpdates_x64.cmd"; 10. I started the file "SD10_Renewed_1.59-small_Start.cmd" and I chose the settings that satisfied me; 11. Then in the same window the lines were written how many of my .CMD, how many of my .BAT and how many of my .REG were copied. The script now indicates exactly what is already very good. Bravo, @SunLion. 12. After an unknown long time waiting - the process is finished; 13. I launched the file "_CreateISO.cmd"; 14. The file "W10_19044.7291_x64_xx-xx.iso" was generated. @SunLion, I checked in the generated ISO file: - sources\$OEM$\$$\Setup\BAT - my files are there; - sources\$OEM$\$$\Setup\REG - my files are there. I decided to burn the generated ISO file to USB. I launched "Win10SetupDisk_3.5_repack.exe" - an error appeared. I decided to try the newer version and launched "Win10+ setup disk v.3.6.exe". But the error is this: @SunLion and @rpo, you understand and can help me solve this error. I burned the generated ISO without any problems using "Rufus v.4.14.2377 final x64 portable.exe". @SunLion, thanks for the provided version "SD10_Renewed_1.59-small.cmd". In these few days I don't have the opportunity to install this ISO and check everything I was looking for in the classic approach of @Wojciech Keller (with original images during Windows installation, at login, at logout, at user change...). @SunLion, I have a suggestion/I have an idea. In my case I used an LTSC ISO file and "W10_19044.7291_x64_xx-xx.iso" was generated. My suggestion is, if you have a convenient option and it's not too complicated, to also write that it's LTSC in the name of the generated ISO. For example: "W10_LTSC_19044_7291_x64_xx-xx.ISO". @SunLion, thanks for your hard work, time and patience.
Good afternoon! Your procedure is correct. Everything is in its place. Congratulations. Regarding the creation of the ISO with LTSC in its name, I will try to adjust that. We must remember that other versions can also be edited. Regarding Win10SetupDisk_3.5_repack.exe, first you must double-click it for the package to be installed. To use the tool (see attached images): Add your USB drive and go to Start Menu\Programs\Utilities. Find the shortcut "Win10SetupDisk" and run it. When the first window opens (Win10SetupDisk_1), click Yes. When the second window opens (Win10SetupDisk_2 and 3), click Source to locate your ISO image to add. When the third window opens (Win10SetupDisk_4), click Create Setup Disk and wait for it to finish. Try it and see if it works. Regarding the $OEM$ folder, it will always be copied to the sources folder. Everything inside that folder will be copied to the appropriate locations within the Windows installation. It's essentially like mounting the image and inserting whatever you want inside. It does the same. Best regards
Concerning the Win10SetupDisk_3.6.cmd version : 1. To avoid staying in the foreground, comment line 11 as : #(New-Object -ComObject shell.application).toggleDesktop() 2. Instead ofusing progress bars and using the original robocopy, replace line 308 as : $Progress = $False
I'll do that! Thank you! Where can I download the Win10SetupDisk_3.6.cmd file? I only have version 3.5 cmd.
@SunLion Win10+ Setup Disk 3.6.zip Win10+ Setup Disk 3.6.cmd with line 11 commented and robocopy instead of progress bars (line 308) Win10+ Setup Disk 3.6.exe To reinstall progress bars : on line 308 replace $False by $True To create the .exe, excecute Make-Cmd (the module ps2exe must be installed)
===================== SD10_Renewed_1.61 ===================== Updated to 1904x.7417 - Updated hfixes_all.txt - Updated Restricted Codecs Dolby - Several adjustments were implemented - The CreateISO script has been adjusted to create the image with the full name, for example, W10_19044.7417_EnterpriseS_x64_pt-BR.iso. In this version, two new scripts were created: 1 - SD10_Custom_1.61.cmd 2 - SD10_Default_1.61.cmd The Custom script allows the user to apply the offered customizations at their discretion. The Default script does not contain any customization options. The folders below are for personal tweaks (in both scripts): - PersonalTweaks\BAT (.bat and .cmd files can be added) - PersonalTweaks\REG (only .reg file can be added) These tweaks will be applied during RunOnceEx In the package that is offered there are no tweaks to these folders. It's up to the user to add their own tweaks (optional) ===================================================================== When choosing the CUSTOM script, please observe the guidelines below: ===================================================================== All options are user-selected. No customization is applied without the user's explicit choice. If the user wants to customize the image, answer YES to both questions below and apply all available tweaks in WPI. If the user does NOT want to customize the image, answer NO to both questions below and do NOT apply the available tweaks in WPI. 1 - Do you want to customize Boot.wim? If the answer is YES, Boot.wim will be customized. 2 - Do you want to Pin the shortcuts to the Taskbar? If the answer is YES, the following shortcuts will be pinned to the Taskbar: Windows Explorer, Show Desktop, and Notepad. 3 - WPI (Windows Post Install) - All other customization tweaks are available through this tool, which allows the user to choose whether or not to apply them. If you don't want to apply any tweaks, just click "Exit" in the bottom right corner. https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/
@SunLion, thanks for the new version 1.61. I notice that compared to version 1.59 there are changed locations of files and folders, the name of the added script is no longer "small", it is now "default". @SunLion, I have a question: The file "W10UI.cmd" is version 10.59b. Is there any specific reason why this version is used, and not the updated version 10.59s? I would be happy if you added version 10.59s.
Yes, the locations of some folders were changed to keep the most frequently used ones in the foreground and the less frequently used ones in one place. I believe this makes it easier to operate. I just forgot to update it. You can download and replace it without any problems. Thanks for reminding me!