Hi @Shrinklier I ran some tests with code unification using NSudo, and for Windows 11 scripts, it worked fine, without errors. But when I used it with a script I use to create my personal Windows 10 EnterpriseS, I got errors in two places: - Disable News and Interests ==> "ERROR: Access denied" - Removing tasks from task scheduler ==> "ERROR: The system cannot find the specified registry key or value" When I went back to using the NSudo codes within the main script, these errors disappeared. So, my suggestion is to keep the NSudo codes in the main script, as this doesn't cause any problems during execution. I also tested using @freddie-o's code in the Start script, keeping the NSudo code in the main script where necessary. This model worked well, without errors. I don't know if it will work well with Windows 11 as the HOST. Someone just needs to test it... Anyway, thank you for the help, because this way we will only have one Start script. For those who want to test, here are the two models attached (NSudo and Elevate_as_TI.ps1 by freddie-o).
Hi @SunLion ! Thank you for taking the time to test the script. The issues you mentioned are actually expected and make sense. Previously, when you used NSUDO per command, each NSUDO call would spawn a new process (flash a terminal for half a second), that new process was never logged, that is why the LOG file never showed any issues. So basically using NSUDO per command will hide any possible issues with the script. Regarding Access denied error, we need to pin point the exact operation that failed so we can further investigate. Regarding the task removal, the error that you see is "The system cannot find the specified registry key or value", this is not an elevation issue, this is a path issue, if you share the code we can identify the source of the problem. @sainfo used Windows 11 as host and reported no issues. Also, viewing slimdown for both Win versions, you need to also remove the self elevation code from the main script, once it is launched as TI any other method of elevation could potentially cause issues. If you already created an image you can test on VM and verify that News and Interests is disabled and the tasks were removed. Edit: I investigated the Access Denied issue, the problematic key is ShellFeedsTaskbarViewMode, probably caused by ACL restrictions, but since you already set EnableFeeds to 0, this completely disables News & Interests, so ShellFeedsTaskbarViewMode is irrelevant.
I really don't get any errors when running the script. Lately, I've stopped using `NSudo` in the main script and run the entire script with `Ti` privileges. It seems to me that this is both more convenient and the right way to do it (but that's just my personal opinion). Out of all the different Windows editions, I personally prefer the IoT LTSC edition. That’s why I work exclusively with the Windows 11 IoT Enterprise LTSC [26100.1742] image, processing it with my own script and applying the latest updates to it. I’m really looking forward to version 26H2; I’d like to use it to create my own IoT Enterprise LTSC version. Only time will tell how practical and feasible this is ...
When a person has the desire, he can overcome all difficulties. I am sure that you will achieve success.
Good morning, Actually, since the original script by WKeller, the commands with NSudo have always been used, without the need for privilege elevation. The additional Start script was added only for the creation of the log file. I'll try some more tests and see how this works best...
Yes, WKeller's script had per-command elevation since you would run the main script directly, and the only check there was for admin rights. The current Start and Start_Nsudo scripts already attempt to launch the main script with system/TI elevation, thus adding any elevation in the main script is redundant. If you want to keep the per-command elevation in the main script then the Start script elevation is redundant and running as admin will suffice. Also, any HKLM modification and removal of non-protected files does not require TI elevation on a mounted system, if you remove nsudo from these i will expect that new "errors" will appear. Since you do a great work here maintaining the script, go with the option that makes your life easier!
Convenient? yes, very! The right way to do it? Yes and no, technically, there are very few operations that require TI elevation in this script, most of it does not, but as long as your script touches only the mounted system and not the host os, there will be no problems. Same here about IoT LTSC, this is the "consumer" edition for me, the rest are beta testers and AI farms. If they keep with 3 years release cycle, the next IoT LTSC version should be 27H2. 26H2 is an incremental update, no new base.
In IoT Enterprise LTSC 28000.1836 have problem with work folders ( in Russian language lp)? (У меня вылетает при нажатии на рабочие папки в панели управления. Собирал на скрипте bedi. По идее можно конечно удалить fod из образа, но интересно получилось ли у вас собрать ltsc без такой ошибки).
I also used the @Bedi script, and nothing crashes for me. Hmm, what do IP and FOD have to do with image creation? That’s right, nothing at all. Those are localization files. In my case, it doesn't matter at all, because I used a PRO [28000.1836] image with the localization I already needed. So I simply commented out everything in the script related to localization. Next, after obtaining the IoT LTSC version from the PRO version, I processed it with my script and performed the final image configuration in DISM++.
I used the English version of 28000.1 and installed the Russian localization. Apparently, there was a localization error somewhere in this fod, which is why it crashes. If you don't mind, please share your modified batch file in a private message. I'd also like to build the iot ltsc version. I'd be grateful.
There are as many opinions as there are people. In other words, everyone does what they think is best. Why localize an image when you can use UUP Dump to build the image you need with the localization you want? I set myself the task of obtaining the 26H1 IoT LTSC version. To do this, I used UUP Dump to build the 26H1 PRO [28000.1836] ru-RU version. To accomplish this, I used a great script by @Bedi (which I modified slightly to suit my needs). I processed the resulting Windows 11 26H1 IoT Enterprise LTSC [28000.1836] RU image using my own version of the image-processing script. In my case, the result was saved in the DVD folder. As usual, I perform the final, clean configuration of the install.wim image using DISM++ and save the result in the DVD\sources folder in .esd format. That’s the gist of it; next, I use Rufus to burn the contents of the DVD folder to a bootable USB drive and install the resulting image on the PC. As they say: it’s as simple as pie...
Would you be comfortable sharing your script so that we can create our own "Windows 11 26H1 IoT Enterprise LTSC"? If it's not too much trouble for you.
So, what exactly is the process? I use two scripts to work with the image. To get the 28000.xxxx IoT Enterprise LTSC version from the 28000.xxxx PRO image, I use a great script by @Bedi. Next, I process the resulting 28000.xxxx IoT Enterprise LTSC image with my own script (I posted it, and it’s still available in the distribution). I’m currently trying to combine these two scripts with the ability to select which actions to perform on the image. This would allow the tool to work with images of versions 24H2–26H1 (26H2) of the PRO and LTSC (IoT LTSC) releases. Once I finish testing it, I’ll post it.
Please, do NOT pollute this topic with unofficial Windows version constructs. 28000.x LTSC is not an officially existing build, so, please stay in the (Re-)construction topic.
Well, if it’s not possible, then it’s not possible—I won’t “clutter up” this thread with it anymore. Sorry about that. It’s just that I’ve wanted to get the 26H2 IoT Enterprise LTSC x64 RU build for myself for so long, but I couldn’t manage it. I know it isn’t officially available and probably never will be, but I really wanted to have it. And when I finally managed to get it, I was so happy that I decided to share it with other users. I didn’t even expect that I’d be “cluttering up” this thread with it. Well, if not, then not—to each their own—good luck to you all!
You can post about it, just not here. The Reconstruction topic exists for exactly that reason. No one will judge you there. We just don't want users getting confused thinking these builds are real.