[24/25H2] RunOnceEx procedure does not run with autounattend.xml

[Victory61]

Same RunOnceEx configuration with same autounattend.xml file in ISO 23H2 structure works

The autounattend file script used in both structures is as follows:
link

In my ignorance, I can assume that there may be a change in Windows 11 version 25H2 (which shares the same base as 24H2) that makes the management of the entire installation sequence more rigid or that shifts the focus to the exclusive use of commands in autounattend.xml for post-installation tasks, implicitly ignoring SetupComplete. cmd if there are competing or incompatible commands.

Thanks for the advice.

[cschneegans]

Works for me in 25H2, i.e. C:\Windows\Setup\Scripts\SetupComplete.cmd gets automatically executed. Check that this file exists.

The C:\Windows\Panther\UnattendGC\Setupact.log log file should also mention SetupComplete.cmd, like so:

[windeploy.exe] RunUserProvidedScript: Found script at [C:\Windows\Setup\Scripts\SetupComplete.cmd]; executing with UI hidden...
[windeploy.exe] RunUserProvidedScript: Successfully executed script; (returned with exit code 0x0)

[Victory61]

I also wanted to mention a test I conducted with ISO 25H2, introducing the smallest autounattend file, and RunOnceEX worked.
However, I am convinced that there is some command I added that is preventing the process from completing successfully.
The file used that works is this one:
https://justpaste.it/awabq

[cschneegans]

Totally missed the <UseConfigurationSet>false</UseConfigurationSet> in your autounattend.xml file. To process the $OEM$ folder, you must check the Use a distribution share / configuration set setting on the form.

[Victory61]

This one?

[cschneegans]

Exactly.

[Victory61]

Thank you very much, you solved the problem.
Everything is working fine now.
Thank you for introducing the specific command.