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