[W11 25H2] The RunOnceEX procedure is not executed

DMD · Oct 14, 2025

Good morning, I was trying the RunOnceEx procedure, which only works if I use the ISO structure of 23H2, and I can't understand why.

The ISO structure with RunOnceEX is as follows:

The scripts folder contains these instructions:

Code:

@echo off

SET CDROM=%WINDIR%\Setup

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY% /v Flags /t REG_DWORD /d "20" /f

REG ADD %KEY% /V Title /D "Post Installation..." /f  >NUL

REG ADD %KEY%\01 /VE /D "Simple Sticky Notes" /f  >NUL
REG ADD %KEY%\01 /V 1 /D "%CDROM%\Software\Simple_Sticky_Notes_6.8.0.0.exe" /f  >NUL

REG ADD %KEY%\02 /VE /D "Visual_C++2015-2022_(14.44.35211.0)" /f  >NUL
REG ADD %KEY%\02 /V 1 /D "%CDROM%\Software\Visual_C++2015-2022_(14.44.35211.0).exe" /f  >NUL

REG ADD %KEY%\03 /VE /D "Open Shell" /f  >NUL
REG ADD %KEY%\03 /V 1 /D "%CDROM%\Software\Open_Shell_4.4.170_preconfig.exe" /f  >NUL


EXIT

The silent mode files are in the Software folder.
This structure in ISO 25H2 does not work. Should the procedure, which is now obsolete, be updated?

Thank you.

garlin · Oct 14, 2025

The $OEM$ layout is the same in 24H2 & 25H2, the only change is the new Setup client. Some users claim in certain cases, it's not copying $OEM$ content to the target folder (?)

1. Are your installer files copied to \Windows\Setup\Software? If true, then $OEM$ works as before.
2. What calls this script?

DMD · Oct 15, 2025

Good morning, Garlin.
The script is called “SetupComplete.cmd.”
After installation, the “Script” and ‘State’ folders are created in the “C:\Windows\Setup” path.
The following files are located in the “Scripts” folder:

In the “State” folder

garlin · Oct 15, 2025

You specified Flags = 20 (decimal) or 0x14 (hex)

Value	Function	Function definition
0x00000000	Default	All functions are disabled
0x00000001	Delete	Delete registry entries after processing them (normally only RunOnceEx)
0x00000002	Wait	Causes items to be run synchronously
0x00000004	Check Shell Status	Verifies shell is ready to accept OLE commands
0x00000008	No Error Dialogs	Error dialog boxes are not displayed
0x00000010	Create Error Log File	Create C:\Windows\RunOnceEx.err file if errors occur
0x00000020	Create Execution Log File	Create C:\Windows\RunOnceEx.log file with status of commands
0x00000040	No Exception Trapping	Does not trap exceptions that occur when registering DLLs
0x00000080	No Status Dialog	Status dialog box is not displayed while RunOnceEx runs
0x00000100	Ignore Flags	Flags registry key is ignored

Did you really intend to specify 0x20 (32 in decimal)?

DMD · Oct 15, 2025

I have always used setting 20. Are you saying that this is incorrect with the new ISO 24H2/25H2 structures?

garlin · Oct 15, 2025

reg add /t REG_DWORD /d 20 = hex 14
reg add /t REG_DWORD /d 0x20 = hex 20

0x20 = Create Execution Log File
0x14 = (0x10) Create Error Log File + (0x04) Check Shell Status

I think you've been doing the math wrong for a while. It doesn't change the running tasks, but you don't get the same log files.
My recommendation for debugging is "/d 0x32".

0x32 = (0x20) Create Execution Log + (0x10) Create Error Log + (0x2) Run synchronously

DMD · Oct 15, 2025

Please excuse my ignorance, but do I need to enter
REG ADD %KEY% /v Flags /t REG_DWORD /d “0x20” /f
to also obtain the execution log and error log?

garlin · Oct 15, 2025

You don't need the quotes.

REG ADD %KEY% /v Flags /t REG_DWORD /d 0x20 /f

DMD · Oct 15, 2025

I tried with the new value, test failed.

garlin · Oct 15, 2025

You're suppose to reveal what the log files reported. If FLAGS = x30, and you have no logs, then SetupComplete.cmd didn't run to create the RunOnceEx tasks.

DMD · Oct 15, 2025

Only the two folders created: Scripts and State.

Inside the State folder.

This is the log I found in
C:\Windows\Panther\UnattendGC.

JustPaste.it - Share Text & Images the Easy Way

justpaste.it

garlin · Oct 15, 2025

I see a Schneegan's script running, but no SetupComplete.cmd in what I assume is the setupact.log. SetupComplete.cmd won't run if your PC detects an OEM product key in the BIOS.

DMD · Oct 17, 2025

After many tests, I found the culprit.
he autounattend file generated by Generate autounattend.xml files for Windows 10/11

In ISO 23H2, it worked with my RunOnceEx structure.
In ISO 24/25H2, the same RunOnceEx configuration with the same autounattend file does not work.
Without the autounattend file, the procedure works.
I contacted the author, who inserted a specific command for this:

Inserting the new autounattend file generated with my RunOnceEx procedure in the 25H2 structure worked.
Thank you for the information you gave me, but I saw that my old procedure worked, as in ISO 23H2 do I still need to make the changes?

I have to fix another procedure that isn't working properly (Auditmode), but I'll continue on a specific thread.

garlin · Oct 17, 2025

I don't debug auto-generated unattended files, since it's not my code. This likely isn't a problem when using the legacy Setup.

[W11 25H2] The RunOnceEX procedure is not executed

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Similar threads