Tested script no errors, ran in a vm, small gripe I enabled search though in taskbar settings was disabled by default, easy fix to manually toggle it back on.
I don't think there will be any problems, because the codes in the $OEM$ folder are copied to the same location as in install.wim, i.e. .\Windows\Setup\Scripts. So everything should work normally.
Great Job @SunLion I'm testing tonight. Can anyone tell me whether the flags are set with the script in IOTEternerprise? Or does it remain on EnterpriseS?
The script doesn't change this. It remains EnterpriseS or IoTEnterpriseS depending on the image you're editing.
Everything worked except for LTSC 2025. It is installed as LTSC 2025, but activation does not take place with the original script from Tsforge. I'm now using my modified Setupcomplete.cmd. The first installation is online, the second offline. Let's see how it behaves. Otherwise, I'll build two activations into LTSC 2025. Namely, KMS4k. By the way, I haven't reduced the size of Pro and Enterprise yet. These are original files from MVS that I've tweaked a little, Reg Keys, etc..
the test passed on VM. no issues. all classic apps working fine. (snipping paint calculator) its installed OS size 12.5 GB is similar to last release. but much bigger than that by 24H2_Integrator_10.19 (some 10 GB. must be using W10UI .mum method).
Last weekend, I tested it on physical computer. Its bugs are much less than the early release. It has run last weekend. it's noticed that SD11 explorer got freezing-up often. no response to mouse click. my quick fix is to close the explorer. then re-open a new explorer. my computer was running tiny11 and it didn't have this issue. Can you look into the issue? Thanks,
I'll look into it... Some online comments suggest that Explorer in Windows 11 has been experiencing some bugs. Let's see if we can figure out what it is...
@siliconbeaver There are many questions about this online; I just checked again. Technicians recommend running SFC /scannow, among other measures, in almost all cases. However, in our script, I disabled Windows Update by default at the end of the installation. What we could try is to change this and leave Windows Update enabled and run it after installation to check for updates. To do this without modifying the script, after installation, run the \Utilities\ToggleWindowsUpdate_v3.4 tool. This tool toggles the Windows Update operating mode. After that, it's up to you whether or not to disable Windows Update. For now, please try this method.
Note: You can also use this Updates-On.bat to restore the Update Center to normal operation: Code: @echo off echo Enabling the Windows Update Center... rem Restart the Windows Update Center service net start wuauserv sc config wuauserv start= auto echo The service is started, the startup type has been changed to "Automatic". rem Delete the registry key that blocks updates reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v "NoAutoUpdate" /f > nul 2>&1 echo The registry key that blocks updates has been deleted. echo Enabling Windows Update Center is complete. pause exit