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
- :
- Upgraded Projects breaking Regedit and TaskMgr
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
Jan 08, 2009
02:56 PM
Upgraded Projects breaking Regedit and TaskMgr
Hopefully someone can help.
I have been upgrading several installations from InstallShield Professional v6.3 to IS2009. The problem arises when the the package is built when the file source paths are from my local machine. After installation - Regedit is unavailable - as I get a pop-up message “Registry editing has been disabled by your administrator”. Additionally, Task Manager is disabled.
This does not happen if the file source paths are the UNC paths to the original network location where I pulled the original Installation project files.
This does not make any sense to me - and no other installations are exhibiting this behavior.
Thanks,
David
I have been upgrading several installations from InstallShield Professional v6.3 to IS2009. The problem arises when the the package is built when the file source paths are from my local machine. After installation - Regedit is unavailable - as I get a pop-up message “Registry editing has been disabled by your administrator”. Additionally, Task Manager is disabled.
This does not happen if the file source paths are the UNC paths to the original network location where I pulled the original Installation project files.
This does not make any sense to me - and no other installations are exhibiting this behavior.
Thanks,
David
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 08, 2009
02:59 PM
Additionally, I have tried using debugger, but the disabling of Regedit occurs before the script files are invoked.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 09, 2009
02:02 AM
This sounds more like a Group Policy restriction added to your machine by your system administrators.
You can turn off the "Disable Registry Editing" policy by doing the following.
1. Click 'Start'
2. Choose the 'Run...' command
3. Paste the following line into the 'Open' text box:
REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System /v DisableRegistryTools /t REG_DWORD /d 0 /f
4. Click 'OK'.
Now should at least be able to run 'regedit'.
You can turn off the "Disable Registry Editing" policy by doing the following.
1. Click 'Start'
2. Choose the 'Run...' command
3. Paste the following line into the 'Open' text box:
REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System /v DisableRegistryTools /t REG_DWORD /d 0 /f
4. Click 'OK'.
Now should at least be able to run 'regedit'.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 09, 2009
07:51 AM
No, I have Administrative rights on the Machine. If I list the file paths from the network - the same install works fine - and Regedit is not broken - and Task Manager is likewise not disabled.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 09, 2009
10:51 AM
I was able to resolve the problem by creating a path variable: This references the root folder for the project files.
By prefacing every file location with the variable, REGEDIT and TaskMgr are now operational.
By prefacing every file location with the variable, REGEDIT and TaskMgr are now operational.