Many REG codes only take effect after the User is created and the Desktop is opened. That's why many .reg files are not applied offline by the script. So the solution was to create the PersonalTweaks folder so that they can be applied by RunOnceEX. This works fine. There may be other methods, which I don't know about.
All this is true, all this applies only to executive commands that are used in .cmd files and does not apply to .reg commands for changing the registry. And in my case, these are registry commands. The execution .reg of commands can be easily observed in DISM++. So, these three .reg files are successfully applied to the image in a separate script, but for some reason they do not want to run in the Integrator. It is completely unclear what the difference is for this part of the command where it is applied. In a separate script or as part of the Integrator. Apparently, there is some minor detail here that I personally cannot see. That is why I turned to you as a more experienced colleague in programming.
What is the proper way to install cumulative updates to update the slimmed version of Windows? Does applying this update will undo some of the components or apps you remove or Windows settings undo?
If the ability to update the Windows image is not broken, the system will be updated both through the Central Office and manually. Some of what was removed from the image will be restored (which part depends on the state of the system services), and the settings and applications applied to the image will not change.
@SunLion I took your advice & rebuilt image without WPI included & I ensured the context tweaks were present in the pers tweaks dir. Though I have the same result with the oem context menu?
Instead, you should include WPI so that everything is adjusted. Today I spent the day racking my brains to fix the installation of the Apps through runonce. It's not working as I would like. I think I found an alternative. I'll finish it tomorrow and do the tests. Hope everything works out! Cheers
In that case I could just incorporate the context reg into my own post installation regime, otherwise will wait for the result of your tests, thanks.
Got it, thanks! I'm deleting the Store on purpose because I never use it. I think you've got a really cool script, but it's a shame it's not universal. In my opinion, it is not very convenient to use because you have to use the full names of the components for removal and processing. This is not very convenient because when using a different version of the image, you have to search for all these components in the image again, which is very troublesome. I think the script shouldn't care what it's fed. Its main job is to run the script and not complain.
Well, this is the Dev channel, so there is no time bomb! I compiled this build version 26200.5603. Then, after a while, it was updated via the Update Center to version 26200.5622, then to version 26200.5641, and just recently it was automatically updated to version 26200.5641. According to UUP DUMP, they position it as 25H2. I have it installed on one of my computers. I'm not removing this build because I'm very interested to see what will happen in September: will MS simply change its name from 24H2 to 25H2, or will they release something new with a new kernel, as they promised at one time?
I am interested in trying to do the same for 24H2 as long as someone could guide how i can unpack (expand ) L1_Windows11.0-KB5043080-x64.msu and L2_Windows11.0-kb5063060-x64.msu in order to make an modded update for future use . Regarding your script , i like it and i can use it as long as i will figure out what did you disable or remove regarding the Store in order to use it if i need to update my appx . Today i am playing with 10.0.26100.4351 IOT to see what i can do ... but still could not unpack Windows11.0-KB5063060-x64.wim and Windows11.0-KB5063060-x64.wim
Try this: Spoiler: TEXT - Original Файл .msu, являющийся пакетом обновления Windows, можно распаковать с помощью утилиты expand или PowerShell. Также можно использовать архиватор 7-Zip для извлечения содержимого, если внутри находится CAB-файл. Подробные инструкции: 1. Использование утилиты expand (в командной строке): Откройте командную строку от имени администратора. Перейдите в каталог, где находится файл .msu. Введите команду: expand <имя_файла.msu> -F:* <папка_назначения>. Замените <имя_файла.msu> на имя вашего файла, а <папка_назначения> на желаемую папку для извлечения. Например: expand my_update.msu -F:* C:\Extracted_files. 2. Использование PowerShell: Откройте PowerShell от имени администратора. Перейдите в каталог, где находится файл .msu. Введите команду: expand-archive -Path "<путь_к_файлу.msu>" -DestinationPath "<папка_назначения>". Замените <путь_к_файлу.msu> на полный путь к файлу, а <папка_назначения> на желаемую папку. Например: expand-archive -Path "C:\Updates\my_update.msu" -DestinationPath "C:\Extracted_files". 3. Использование 7-Zip: Откройте 7-Zip. Найдите файл .msu в 7-Zip. Если внутри .msu находится CAB-файл, откройте его как архив. Распакуйте нужные файлы из CAB-архива. Важно: Файлы .msu обычно содержат CAB-файлы, которые также можно распаковать с помощью 7-Zip. Если .msu содержит только один CAB-файл, то распаковка .msu напрямую через expand или PowerShell даст тот же результат, что и распаковка CAB-файла отдельно. Spoiler: TEXT - Translation An .msu file, which is a Windows update package, can be unpacked using the expand utility or PowerShell. You can also use the 7-Zip archiver to extract the contents if there is a CAB file inside. Detailed instructions: 1. Using the expand utility (in the command line): * Open the command line as an administrator. * Go to the directory where the .msu file is located. * Enter the command: expand <file_name.msu> -F:* <destination_folder>. Replace <file_name.msu> with the name of your file and <destination_folder> with the desired folder for extraction. * For example: expand my_update.msu -F:* C:\Extracted_files. 2. Using PowerShell: * Open PowerShell as an administrator. * Go to the directory where the .msu file is located. * Enter the command: expand-archive -Path “<path_to_file.msu>” -DestinationPath “<destination_folder>”. Replace <path_to_msu_file> with the full path to the file and <destination_folder> with the desired folder. * For example: expand-archive -Path “C:\Updates\my_update.msu” -DestinationPath “C:\Extracted_files”. 3. Using 7-Zip: * Open 7-Zip. * Find the .msu file in 7-Zip. * If there is a CAB file inside the .msu, open it as an archive. * Extract the necessary files from the CAB archive. Important: .msu files usually contain CAB files, which can also be extracted using 7-Zip. If the .msu contains only one CAB file, extracting the .msu directly using expand or PowerShell will give the same result as extracting the CAB file separately.
Juste installed, and it's running well, but M€ don't forget to bloat it...and I installed IoT entreprise. Will debloat it soon...