Troubleshooting OSDCloudGUI SetupComplete menu options

[skyblaster]

I used to use OSDPad and @AkosBakos script to install and activate the embedded OEM license key.

Since switching to a less complex imaging process, I've tried using the following function via the "Apply Key from UEFI" option in OSDCloudGUI.

As you can see from the logs, Set-SetupCompleteOEMActivation did not run, otherwise, the "Running SetupComplete OEM Activation" message would have been logged.
SetupComplete.log

Warning: I know this is not the best example as this particular machine was imaged offline. I will follow up with another set of results.
2024-09-14-180943-Deploy-OSDCloud.log

Here you can see the global options where GUI is part of the variable name.

Now, below, as part of the main OSD function, GUI is not part of the if statement.

Is there another function that makes $Global:OSDCloudGUI.OEMActivation == $Global:OSDCloud.OEMActivation ???
In the OSDCloud.json file, I can see the variable being set to true, so I'm inclined to say yes. I just don't know where to find it.

In any case, I can see that SetupComplete.cmd is run before the "user perceived" OOBE, which is inline with Ákos' blog post.
I just can't figure out why the key activation script is not added to SetupComplete.

Reference: Microsoft's official documentation

[skyblaster]

Here are some logs from an online run performed earlier today.
2024-09-23-125356-Deploy-OSDCloud.log
SetupComplete.log

Also including C:\Windows\Panther\UnattendGC\ setupact.log

[skyblaster]

Based on prior discussion with Gary, I believe my next step is to run New-OSDCloudUSBSetupCompleteTemplate
Building a new OSDCloudUSB now.

[skyblaster]

Before attempting custom scripts via New-OSDCloudUSBSetupCompleteTemplate, I just wanted to give a fresh ADK install a try and report back.
No change with a fresh OSDCloudUSB using the 10.1.22621.1 ADK updated with the latest 22H2 CU.
I'm using this to deploy 23H2.

[skyblaster]

PR #176 created to resolve issue.