InstallAware

Posted: **Thu Mar 03, 2011 12:44 pm**

On secured military Windows XP systems, the reboot Computer and resume setup command is not always resuming my setup after .NET Framework 4.0 requests a reboot. The reboot always works correctly, but in on many systems the resume does not happen. I have been able to confirm with logging that my installer is never started after the reboot. I am also installing MSI 4.5 and SQL Express and if they require a reboot my setup is properly started after the reboot. The.Net 4 framework is installed correctly.

I am using the Installaware 9 script setupnet4_x86, the following is the relevant code:

Code: Select all

Run Program $DOTNET40_FILEBAG_X86$\Setup /x86 /q (WAIT, get result into variable DOTNET40_RESULT_X86)
 Set Variable PROGRESSMODE to 
 if Variable DOTNET40_RESULT_X86 Equals 3010
   MessageBox: $TITLE$ Setup, Your computer needs to be restarted before $TITLE$ Setup can continue.$NEWLINE$$NEWLINE$Please save your work in all running programs and click OK to restart your computer. Once your computer restarts, login as “$USERNAME$” to resume setup.$NEWLINE$$NEWLINE$If you click CANCEL, setup will exit. You will have to run setup again at a later time to install $TITLE$.$NEWLINE$
   if Variable REBOOTNOW Equals OK
     Reboot Computer and Resume Setup
     else
     Terminate Installation
   end
 end

In our testing the systems that don’t resume are consistent in that they never resume. I have tried to determine why these systems require a reboot in the first place, but to no avail.

Has anyone seen anything like this?

Sincerely,
John LeBrun ([email protected])

Posted: **Sat Mar 05, 2011 5:55 am**

Dear John,

Does this happen on machines other than your secured military XP?

Posted: **Mon Mar 07, 2011 12:04 pm**

Aviv,

I have not seen this problem on other systems. Everything we work on is secured at least a little. We have discovered more about this problem. We have identified a list of 46 Microsoft updates that have the following impact:

Apply these 46 updates and .Net 4 Framework install does not require a reboot and the user experience
Do not apply these 46 updates and .Net 4 Framework requires a reboot and then out setup fails to restart

Today I have the lovely task to identify which missing Microsoft updates are causing the need for a reboot after .Net 4 is installed. Once this is narrowed down I should be able to determine why the setup.exe is not restarted after the Reboot Computer and Resume Setup command is executed.

Our current theory is that one of the Microsoft security updates is clearing the runonce registry key.

Posted: **Mon Mar 28, 2011 4:32 pm**

I never found a solution to this issue.

I changed the install to create a shortcut to itself in the startup folder instead of using Reboot Computer and resume Setup. Then on restart of the installer I delete the shortcut.

I discovered that the following windows updates are somehow related to this issue:

KB2418241
KB2416473
KB2416447
KB983583
KB982168
KB979909
KB982524

I ran out of time to find the real solution and we shipped with the work around above.

Sincerely,

John LeBrun
[email protected]

Posted: **Mon Mar 28, 2011 4:35 pm**

Dear John,

I apologize, but it makes perfect sense that somehow the RunOnce gets deleted..

InstallAware

Reboot Computer and Resume Setup fails to resume

Reboot Computer and Resume Setup fails to resume

Re: Reboot Computer and Resume Setup fails to resume

Re: Reboot Computer and Resume Setup fails to resume

Re: Reboot Computer and Resume Setup fails to resume

Re: Reboot Computer and Resume Setup fails to resume