Run registry key remains - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

KeithG
Posts: 4
Joined: Fri Feb 03, 2012 11:30 pm

Run registry key remains

I have a project that includes the .NET 4 runtime prerequisite package. When it starts installing it adds the install package to the registry to be run automatically on reboot: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run ... That makes sense since the .NET 4 requires a reboot and the install package should pickup where it left off.

However, even after everything is installed correctly and completely, the registry key remains. That means every time the system is rebooted, the package runs again. How can I prevent this and/or how can I force that registry key to be removed when installation is complete.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Run registry key remains

Hello,
How can I prevent this and/or how can I force that registry key to be removed when installation is complete.
This operation should be performed automatically by the .NET installation package. To force it you can add a registry value removal operation in the Registry page:
http://www.advancedinstaller.com/user-g ... ialog.html

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
KeithG
Posts: 4
Joined: Fri Feb 03, 2012 11:30 pm

Re: Run registry key remains

Thanks for the reply. It looks like I can use [SETUPEXEDIR] to get the location of the install package, but is there a property for the name of the EXE itself?
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Run registry key remains

No, but you can get it from the property that contains its full path, thus the name too, "AI_SETUP_EXE_PATH".

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”