Reboot and login sets Run key?

[wesley]

Hi

I have been using the reboot and login command in Installaware 10.0 in order to start my installer after the user logs in, as we previously had issues with the Reboot and resume. However, the Reboot and Login function sets the Run key, whereas as of 9R2 installaware changed the Reboot and resume to use the runonce key. This key appears to not be deleted on any of our test machines (XP/Vista/Server 2008R2/Windows 7 (x86 and x64) so the setup restarts after every reboot, and prompts the user to remove the software (after the initial install is successful)

I was wondering if this functionality was intentional or not, and also if someone has a simple workaround to ensure that using Reboot and Login deletes the run key after the setup restarts, or writes to the runonce key.

Thanks

[giaviv]

This is intentional, however it does not cause problems for me.
How did you test this?
When I run a setup that calls Reboot and Resume after Login, the setup is only run once...

[wesley]

Our installer installs MSI 4.5, .NET 2 and 4 as prereqs, then installs SQL server 2008R2 express as part of the main install, any of which can trigger a reboot and login, depending on the OS (we have changed the default scripts to reboot and login).
During the install, it works fine, installs the right components, requests the reboot, and restarts the setup after the user logs in. However, we still have the registry key in the Run key after the installer has finished and rebooted, (tested again on XP on hardware, XP on virtual machine, and Server 2008 R2 on hardware today) so we have to manually remove the key at the end of the installer to prevent it restarting after reboot.

I was wondering if you would be able to provide us with a sample installer that does work with reboot and login, and deletes the registry key when the installer successfully completes.
Also, could you possibly tell us at what stage during the installer should the Rebbot and Login Run key get deleted? The only thing I can think of that would cause this failure is that the structure of our code is causing it to skip the part where the key gets deleted once the installer resumes.

Thanks

[giaviv]

Dear wesley,

This is indeed a bug and will be fixed in InstallAware 11+.

Here is a work-around you could use for now - in the beginning of your script, delete the run key that InstallAware did or did not create. Copy this script to the beginning of your script:


~InstallAware Clipboard Data~
~Delete Registry~
~{059C3497-AA5E-4411-9B02-CDCC0785D7E7}~
~1~
~SOFTWARE\Microsoft\Windows\CurrentVersion\Run~
~$PRODUCTCODE_SEGMENT$~
~FALSE~
~Delete Registry~
~{153416E6-EAB0-4E56-9713-9FAE34413660}~
~2~
~SOFTWARE\Microsoft\Windows\CurrentVersion\Run~
~$PRODUCTCODE_SEGMENT$~
~FALSE~
~Parse String~
~{0F00AA36-71A5-4272-886D-CBF21122005E}~
~$PRODUCTCODE_SEGMENT$~
~8~
~PRODUCTCODE_SEGMENT~
~~
~2~
~FALSE~
~FALSE~
~Parse String~
~{1D115A69-461D-4148-9F30-D0FE08517AEA}~
~$PRODUCTCODE$~
~1~
~~
~PRODUCTCODE_SEGMENT~
~2~
~FALSE~
~FALSE~
~Set Variable~
~{57488BA4-5A24-43FA-8A8A-AF62027F0FC5}~
~PRODUCTCODE_SEGMENT$MYAH$MYAH$FALSE~
~~

[wesley]

Thanks for the help and quick response, that workaround works great (tested on XP).

Just out of curiosity, is there a timeline for InstallAware 11 release?

Thanks

[giaviv]

Dear wesley,

Glad it works!

There is no estimate for version 11 at the moment. We will keep you posted though!

[wesley]

Hi again

I couldn't see anything in the release notes for IA 11/12, so I was just wondering if this bug did actually end up getting fixed in the current release?

Thanks

[giaviv]

Hi,

We haven't had reports of this issue in IA 2012, however you are more than welcome to test it out with the trial version!