===================== SD10_Renewed_1.15 ===================== Updated to version 1904x.5917 - Updated the hfixes_all.txt file - Updated the Restricted Codec Dolby - Fixed Basic Theme - Adjusted other configs Tested with: - en-us_windows_10_iot_enterprise_ltsc_2021_x64_dvd_257ad90f.iso - pt-br_windows_10_enterprise_ltsc_2021_x64_dvd_f318268e.iso - 19045.1826.220708-0121.22H2_RELEASE_SVC_REFRESH_CLIENTBUSINESS_VOL_X64FRE_PT-BR.ISO https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/
Have not had a chance to test 1.14 or 1.15 out yet, wondering what the new "Add Basic Theme" feature is/does?
Nothing special. Just a simple theme with a wallpaper and custom color schemes. Just to make it look nice in the end.
So, I just ran the new 1.5 release, and for the first time with SD10 I got a buttonload of errors I've never seen before. All the updates pre-downloaded perfectly -- but, I'm running this on a very hardened and secured Windows install with a lot of third party tools, and the one thing that immediately comes to mind as some of the error messages look innocuous (though some are not): Does SD10 require that the Windows Event Log Service to be enabled? Also, I'm a Maximist when it comes to 'just an OS first' with nothing additive, so I can pick and choose what and how things are installed, or tweaked -- so for example, I like and use Open Start Menu on almost every Windows install, but I want to install it my way and appreciate very much that there's the option to just have it extracted to the desktop! However (pet wish winging coming) some of the tweaks, and the new Theme with no option: not a Fan of this approach. Even Windows Themes as innocuous as they seem add a considerable amount of crap to the registry, that even if undone, and deleted will leave empty hives; and while individually trivial, like all things Windows leads to a cumulative effect added to everything else you have to go in and fix, clean up, and then clean up the clean up again (which is a literal thing with Windows, not a redundant statement) and even then there is crap that can't be removed. So without options, anything added or tweaked will often have added source of measurable outcomes that may not be desirable for a particular installation, a specific hardware target, or a specific person -- more options are better, everything optional is best... As well, having things as options make it clear what your changing if you're changing something. Of course I can (and do) go in and edit the script, and having an overriding default profile for the less initiated makes sense, but I'd prefer option prompts for anything additive or tweaked (and all tweaks are additive). Will run 1.5 again, look more closely and post any errors.
I just ran 1.15, only error I see was in dismounting install.wim, though did not result in any issue running the final image in a VM. Working great here.
I used the script two days ago and had no problems. Everything went well. It seems you made a mistake somewhere.
I just r There were some other minor errors as seen in the log, none of which affected a fully functioning desktop following the installation of the OS.
Well, the only error found was when unmounting install.wim. This occurred because you had some other file in the folder open or also some folder open during the process. This prevents the correct unmounting. When running the script, make sure you close all running files and all open explorer folders. Good luck!
Usually it's open Explorer windows, as Explorer hooks into some file types like .cab etc. for showing then as folders on the left. These hooks prevent correct unmounting, so, close all Explorer windows first. Note that most third-party file managers do not have that problem, even the 7-Zip one works.
Found out my power options were not set up so well so the PC hibernated during the process! Reset those & ran it again, zero issues now, though first attempt still gave me a working desktop too, no difference in both in reality!
@Meru 1. Don't use Fullquotes. Tag the User instead. 2. Sharing Homebrew ISOs in these forums is not allowed. There's no problem sharing in private (Conversation).
Fullquotes are not per se forbidden, but they aren't encouraged to keep topics clean. Do you want to scroll down tons of fullquotes of previous posts to get to the actual content? Tagging is easy, just use like this: @hoak - you will be noticed, no fullquote necessary. Plus, the forums offer another method, by marking the relevant snippet of text, then using Reply. Much cleaner and doesn't hurt. Why should it. Fullquotes are just F*ck ugly and against the Netiquette, that's all. Disclaimer: Fullquoting is especially not recommended for walls of text (and pictures, like in your case). Short posts are no problem.
We get a lot of feedback from members who dislike full quotes. I doubt that @Meru was intimidated. Be careful. @Carlos Detweiller may be the only one who is too moderate to send you away.