sainfo I tested the script. There were a few errors,and the volume is very large, but the installer was created, so I'll try it out on a virtual machine. I'm not at home right now, but I'll upload some photos when I get back. Good luck with the project.
I understand, but I warned you that this isn't the final version—it's a test version. I didn't squeeze every last drop of juice out of the character. The principle of the script itself was important. If you want, you can go more extreme with the character; it's all in your hands...
Okay, I have a 26300 26H2 IoT Enterprise LTSC installed and had no issues with the tool. Why it wouldn't work on the 28000 is a complete surprise to me. Because the script has no restrictions and doesn't care what you're using. Nevertheless, since this issue exists, I'll look into it. Good luck to you!
just tested with an updated custom IoT LTSC 2024, and got some normal errors due to modifications already done on ISO..the Ui is very pleasant and the menu to choose options is very easy to understand...this tool is a beast and become better on each update...congrats @SunLion just notice than ISO is 12 Gb, because there is install.wim and install.esd together... I removed the initial install.esd file, and thats correct now..
========================= 2xH2_Creator_17.7 ========================= Update to 26x00.9457 NOTE: Replace the attached all.txt and LCU2.txt files with the previous one in the DATA\UUP folder.
I think there are bugs in that OS - I couldn't run applications with city government; with other OS, no problem at all.
I'm afraid I have to disagree with you, because I'm running 26H2 IoT Enterprise LTSC (26300) with the latest updates (which were automatically installed via the Central Management Console), and personally, I haven't encountered any issues with the OS.
Why, 26300, of course. I mean, who needs that hopeless 28,000? It’s basically a nobody with no name. IMHO
Thank you very much for your detailed review! I have corrected all the errors and inconsistencies in my script that you pointed out, and I am currently testing the tool with your corrections incorporated. Thank you, and all the best!
"I think there are bugs in that OS - I couldn't run applications with city government; with other OS, no problem at all." Exactly what I mean.
Thanks to some very helpful information from @jagoanku significant changes have been made to the script. I suggest you try this version of the testing tool as well.
Every time I tried to run the script, it wouldn't work, so I've given up trying. Thanks for the effort, though. [sub_Mount] Initializing target acquisition sequence... PS>TerminatingError(): "Error during automatic media indexing workspace sequence: The variable '$globalrojectRoot' cannot be retrieved because it has not been set." ![PIPELINE CRITICAL CRASH]: Error during automatic media indexing workspace sequence: The variable '$globalrojectRoot' cannot be retrieved because it has not been set. Aborting workflow to protect baseline file structure integrity.
Well, I really don't even know what to say to you about this. Working with this tool is ridiculously simple. Why it isn't working for you is a complete mystery! Today, just to be sure, I ran the script back and forth at least ten times, hoping to find even the slightest error. Nope, everything worked perfectly and without a hitch.