Reboot Suppress for a MSI(captured one) Urgent

Go to the Property Table and change the REBOOT Property to the Value: ReallySuppress

Check for ForceReboot standard action in MsiScript, if found remove it.

Hi
Thanks for your input.
There are 4 action which I could see from the log file
setRebootAllowed
setRebootPending
setRebootSuppressed
unsetPENFROPS_VALUE

If I delete anyone form these MSI does not run the active setup....

Did you create those actions?

Is it really a recaptured Wise MSI?

This is incorrect. Active Setup is run by the operating system, it is only INSTALLED by the MSI.
Do you mean that the MSI does not install Active Setup registry keys when you change the reboot settings, or that the Active Setup is not running whatever process you have nominated when you reboot and login?

Hi Edt,
Sorry, The Active Setup is not running whatever process I have nominated when I  reboot and login?
It does creates the active setup entries....
These actions are getting created automatically,I have not added it...

Are you clearing your HKCU registry profile before each test? Active Setup only runs once - then keys are created in HKCU which stop it running again unless the version information in HKLM is incremented. If you are using the same test machine or test profile, then unless you specifically clear the active setup entries from HKCU and HKLM, then they will not run after the first attempt, and your test results will be inaccurate.

There is no way that such registry entries - even in their thousands - would trigger a reboot. I think the cause was elsewhere but anyway, you're sorted now.

In contrast to my normal advice for registering DLLs and OCXs (i.e. one should use the advertising tables and not run RegSvr32 or MSIExec /Y against them), registering EXEs is by and large quite safe, since all the COM information they register is self-contained and not reliant on any other file. Thus, you could have saved some heartache by adding the EXE registration in Custom Actions.