This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: How to create key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 13, 2010
05:04 AM
How to create key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run?
Hi guy,
I am using Installshield 6.3 and through the RegistrySets I am trying to create a new key in the following folders
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
We are trying to do that on a Windows 7 operating system.
The installation creates the HKEY_CURRENT_USER but not the HKEY_LOCAL_MACHINE. How can I overcome the problem?
Thank you for your help,
Donato
I am using Installshield 6.3 and through the RegistrySets I am trying to create a new key in the following folders
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
We are trying to do that on a Windows 7 operating system.
The installation creates the HKEY_CURRENT_USER but not the HKEY_LOCAL_MACHINE. How can I overcome the problem?
Thank you for your help,
Donato
(5) Replies
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 13, 2010
09:40 PM
Maybe you can turn off UAC on Windows 7, then try again.
The better way is upgrade to InstallShield 2010 that support Windows 7.
The better way is upgrade to InstallShield 2010 that support Windows 7.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 13, 2010
10:39 PM
I believe application compatibility will automatically elevate the legacy is6 exe provided it has the name setup.exe or install.exe. Otherwise you can always generate an exeternal manifest file and embed it using mt.exe. ( I haven't tested this, but AFAIK you can do this to any Program Executable (PE) file not just managed exe's. )
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 14, 2010
12:39 PM
Sure, any modification of a file will break a digital certificate. But I'm not aware of InstallShield 6 being able to sign exe's. Don't know that it can't though as I skipped from IS 5.5 to IS Developer 8 and haven't done a pure InstallScript project in years.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 14, 2010
12:42 PM
Christopher Painter wrote:
Sure, any modification of a file will break a digital certificate. But I'm not aware of InstallShield 6 being able to sign exe's. Don't know that it can't though as I skipped from IS 5.5 to IS Developer 8 and haven't done a pure InstallScript project in years.
You beat me to the delete...I realized that it probably wasn't signed since it was that long ago.
(sorry I engaged submit before thinking)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 14, 2010
12:53 PM
No need to delete, it's a very valid observation that may or may not apply but still important to understand. 🙂