Run the latest script and i got this super strange error just after the update integration: Error: 52 You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name. I went and changed computer name from WINDOWS10 to ZZZ, rebooted, no error now...
Just got a minor question regarding the programs in FILES/Addons. Can I delete the ones that I don't need before creating an ISO, or are some of them needed by the script? Personally I don't need the following ones and would remove them before installation if possible: PinStore/PinStoreToTaskBar (don't use store) 7 Zip Desktop OK NoArrow ShutdownRestartW71011f_repack Oh and is it possible to directly change the wallpaper? I've replaced the wallpaper in the Reshack folder. Every single picture I saw with that wallpaper I've overwritten with my personal wallpaper, but its still using the standard one, once installed
Yes, you can remove the .EXE apps you don't want to install from the FILES\Addons folder. The script will copy all existing .exe addons from there. Reshack is not configured to change the wallpaper. You can simply replace the img0.jpg image in the path below: C:\Users\SunLion\AppData\Local\Microsoft\Windows\Themes\OEMTheme\DesktopBackground\img0.jpg Or You can edit the FILES\Addons\Install\Install\OEMTheme19044.exe file to change the image. It's an SFX file created with WinRAR. - Extract the files to the OEMTheme19044 folder and you will see two files: DeskThemeInstall.cmd and OEMTheme.deskthemepack - Make a copy of the OEMTheme.deskthemepack file and rename it to OEMTheme.cab - Extract the contents of the OEMTheme.cab file to the OEMTheme folder. Inside you will see the DesktopBackground folder and the OEMTheme.theme file. - Now you must open the DesktopBackground folder and you will see the image img0.jpg. - Replace this image with the one you want to add, keeping the same name, that is, img0.jpg in 1920x1080 or 1920x1200 format. - After that, you must compress the DesktopBackground folder and the OEMTheme.theme file in CAB format (here I use CabMaker). - Now you must rename this new OEMTheme.cab file as OEMTheme.deskthemepack. - Finally, replace the OEMTheme.deskthemepack file inside the SFX with the existing one. - Place this new OEMTheme19044.exe file in the FILES\Addons\Install\Install folder, replacing the existing file. Done! You can use your new theme.
Took a look at the newest version. Your work is totally appreciated SunLion! But imho the settings and callers are way too clustered, even with the fact that wee need at least 3 levels. - Inside WIM directly in script - called from autounattended - called from RunComplete - called from RunOnce - imported/set via reg from RunComplete/RunOnce - imported/set via AutoIt/sfx exes from RunComplete/RunOnce - imported/set from Autostart Makes it also hard for you to keep track of the different locations and a few things seem to be setup multiple times And not to mention that all the effort you spent on "First" and "Install" in DVD root is wasted if people only deploy the wim. Thats why i have suggested using the Setup\Scripts Folder in %dpmount for everything some time ago. Additional notes: - MAS is called with /HWID flag which doesnt work if your setting up an offline machine - if you are customizing RunOnceEx with more stuff, you might run in a race condition between shutdown of RunOnceEx.cmd and shutdown Win10x64.cmd in Autostart
I had deleted the folder so i tried to recreate the settings i had before so i could provide you with the LOG file. Renamed the PC back to WINDOWS10 selected all the same options and .... no error.... I guess some stupid windows thing was corrupted or something and the action of renaming the PC just fixed it. Long story short, my windows installation probably was fked, script is working fine.
Hi, I have a question. Is it no longer possible to integrate the drivers? I can't find the option in SD10_Renewed_1.52.cmd, or was that option removed? I don't remember which was the last version I used where it was possible.
My fault. It was possible in the original script. I thought it would be possible in this too. It's great that you can implement it.
I agree it is messy & not easy to follow, IMHO as far as slimming down it should be limited to the wim only.
Sorry for not replying sooner. Your post was on the day I had two surgeries and was a bit out of it. As you said, I agree that we should rethink some things. Although I also consider it very difficult to write code that serves multiple purposes at the same time. Could you resend your suggestion about setup\scripts in mount? I intend to start making some modifications. Let's see if it works. Best regards
For anyone interested, I've edited, expanded with eleven new (and old) finds and posted my Very Light Weight Low Drag Applications post to the Software sub-forum for people looking for low drag and/or portable software alternatives for a cleaner, more performant, zero telemetry Windows setup.
===================== SD10_Renewed_1.57 ===================== Updated to 1904x.7184 - Several modifications have been added to the $OEM$ folder to use the settings in Setup\FirstLog instead of the C:\Install folder. It's preferable to make these adjustments in the $OEM$ folder, as any subsequent modifications to install.wim would be more complicated. - Added code to rebuild Boot.wim - Added option to integrate drivers in install.wim and/or boot.wim 2 NOTES: 1 - Some drivers have been added for illustration purposes. 2 - Each user must add their own drivers. 3 - They should be extracted to a specific folder, inside the Install or Boot folder(s). - Added code Elevate to TrustedInstaller by freddie-o - 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: W10_19044.7058_x64_pt-BR.iso - Other minor adjustments https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/
Thank you very much, I'm going to try it. edit I won't be able to test it until the weekend, but in the meantime I have a question. I export the drivers using `dism /online /export-driver /destination:"C:\Drivers"`. If I copy all those folders to SD10_Renewed_1.57\Drivers\Install, is that correct? Or should I sort the folders in a specific way?