Need help with Feature Update using SetupConfig.ini and SetupComplete.cmd

Question

I am stuck for days and it drives me crazy....
I am trying to test IPU using feature update, but need to run some custom config scripts in OOBE.
I have a SetupConfig.ini and SetupComplete.cmd files configured.

INI:
[SetupConfig]
Compat=IgnoreWarning
DynamicUpdate=Disable
Priority=Normal
DiagnosticPrompt=Enable
InstallDrivers=c:\Programdata\NYL\1909DriversIPU\
POSTOOBE=C:\ProgramData\NYL\Scripts\SetupComplete.cmd
Telemetry=Disable
Copylogs=c:\Programdata\NYL\setupconfig.log

In the CMD file i am adding some registry keys and running a PS script to remove APPX and APPXPro packages.

After the upgrade is complete i do see log directory created and i do see settings in the setupact.log file.

MOUPG SetupHost::Initialize: CmdLine = [/Finalize /Update /InstallFile "C:\$WINDOWS.~BT\Sources\Install.esd" /progressCLSID 24c0a0c0-8aa6-422d-8abc-1a96dff49587 /ReportId {E69F3A03-CB4F-47AB-9B35-7FB261A84CC5}.201 "/ClientId" "e0c73f25-f8d0-4305-af63-594d98f76de7" "/CorrelationVector" "zUm068qxWUWboY1L.2" /WUCachedFileName "18363.1139.201008-0514.19h2_release_svc_refresh_clientbusiness_VOL_x64fre_en-us.esd" /Compat IgnoreWarning /DynamicUpdate Disable /Priority Normal /DiagnosticPrompt Enable /InstallDrivers c:\Programdata\NYL\1909DriversIPU\ /POSTOOBE C:\ProgramData\NYL\Scripts\SetupComplete.cmd /Telemetry Disable /Copylogs c:\Programdata\NYL\setupconfig.log]

The problem is my cmd file never runs and i cant figure out why.
Any help what have i missied?
Thank you

Answer 1

Answer 2

I'm going to suggest skipping leveraging setupcomplete and use success.cmd, the custom action script.

https://docs.recastsoftware.com/ConfigMgr-Docs/Windows-Servicing/Windows-Setup-Custom-Action-Scripts.html

For troubleshooting, I'd also suggest creating a super simple setupcomplete.cmd that does one thing, creates a file or registry value, just to confirm it's running. I'd often do that to make sure things were working, then I'd start adding more, testing, adding more, etc.

You might also try the 2nd example: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-command-line-options#postoobe
Where they specify the path to the folder only, and not the file itself.
/postoobe C:\Fabrikam

Just looking at your notes, I don't see anything wrong personally. That's why I'd start with creating a new SetupComplete.cmd file from scratch that does 1 thing... or moving to Success.cmd Custom Action Script.

Answer 3

I changed the CMD file to only add a registry key and a log file. but its not running.
Is there a way to troubleshoot this issue?
Any way to check or verify before before the reboot? Or only after the reboot setupact.log is generated?
Thank you

Answer 4

Gary,
And one more question, i dont see any options to point to a local driver source using Success.cmd file.
Have i missed it?
Thank you

Answer 5

I have been testing manually by moving content from 1909 iso and running setup.exe /ConfigFile "path to setupconfig.ini"
And everything is working as expected. However when i am placing setupconfig.ini in the "%systemdrive%\Users\Default\AppData\Local\Microsoft\Windows\WSUS\ directory it never executed the SetupComplete.cmd file.
I am running a feature update from SCCM using a "Feature update to Windows 10 (business editions), version 1909, en-us x64" Bulletin ID:
Article ID: 3012973

I am running a wrong patch? I cant figure out why its ignoring the batch file.

Thank you.