Cancelled .exe placed in HKLM\Software\Microsoft\CurrentVersion\Run
Hello All,
I use Wise Installation Studio 7.3.0.250.
I have built hundreds of installs over the years and havent seen this issue before.
I am using a pre-requisite .wse script to check a few products are not installed before the MSI launches.
If the checks are not past a warning message is displayed using the "Display Message" command
Message Icon: Exclamation
Start If Block: False
No Cancel: False
If Ok is clicked from warning dialog the msi launches without any issues.
If Cancel is clicked It prompts the user to "Exit Setup".
On our Windows 2008 Server I have found clicking Cancel and "Exit Setup" places a link to the install package in
HKLM\Software\Microsoft\CurrentVersion\Run so when I re-boot the installation package is laucnhed again.
What is the trigger for this installation package to be placing itself in the the run folder.
The same issue does not occur on a Windows XP workstation.
Any help or tips that could be provided would be greatly appreciated.
regards
Shaun
Comments
Is this default behaviour of Windows 2008 server?
If I read your posting correctly, you are not getting to the point of running the MSI, but are exiting the wisescript, and that action appears to be populating the HKLM....RUN key with a path to your EXE so that it runs again after reboot.
In this situation, if you are ABSOLUTELY sure that nothing in the Wisescript is writing to this key, and here I'm thinking of any code which might be rebooting the machine after installating a pre-requisite, and then continuing the install from your wisescript wrapper, then the only other possibility is some aspect of Windows 2008 server behaviour.
To try and debug this scenario, one possible way would be to install the wisescript editor on your Windows 2008 server box, and then single step through the wisescript, checking the RUN key in the registry at each step. Then at least you may be able to determine whether the RUN key is being set via the wisescript, or after the wisescript terminates.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Thanks for the reply. You
Thanks for the reply.
You understood the issue perfectly. The Msi never gets executed just the script.
As I mentioned the issue only occurs on a Windows 2008 Server so I cant see that its anything in the script. The script itself doesnt install any pre-requisites. It ultimately just checks a registry key and issues a warning if it has been set to specific value.
Ill try and debug the script to see what is placing the entry in the RUN key.
Thanks again for your suggestions
Did you solve this? I would
Did you solve this? I would guess that this is a Restart Manager 'feature' in Windows 2008/Vista/7. I have not seen exactly this problem, but instead had dialogs coming up asking me if this program finished correctly, after executing different wise scripts.
Would you like to reply?
Login or Register to post your comment.