PDA

View Full Version : Weird NOD32 message on install


Ryuman123
November 3rd, 2007, 02:49 AM
I'm trying to install the newest version, but it always comes up with this error message:
"Cannot write value ConfigPath to key \SYSTEM\CurrentControlSet\EhttpSrv\Parameters.
Verify that you have the sufficient access to that key or contact your support personnel.

I never got that message before, only thing I did was reinstall windows earlier.
I'm using Windows XP Home Edition.

Ryuman123
November 3rd, 2007, 04:47 AM
I guess no one is going to help me..Alright, thanks anyway.

Marcos
November 3rd, 2007, 05:31 AM
Ryuman123,
please remember that it's a weekend morning here and late night in the USA. You complained after 2 hours of waiting for a response which is quite a short time. Please allow us more time on weekends to respond if there's no reply from other guys here.

As for your issue, I assume you didn't have write permissions for the HKLM\SYSTEM\CurrentControlSet key and the subkeys didn't inherit it either. The administrator should have full access granted for the given key as well as all its subkeys.

Ryuman123
November 3rd, 2007, 11:44 AM
Sorry about being impatient but this issue is annoying me. I've been trying for a day and a half to install it. I'm logged on as an administrator, but I still can't install it. I can't find that certain key either, I don't think it's there.

GAN
November 3rd, 2007, 05:32 PM
Are you sure that the error message say "\SYSTEM\CurrentControlSet\EhttpSrv\Parameters" and not "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EhttpSrv\Parameters"?

I believe it should be HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EhttpSrv\Parameters

Using regedit you can also check the permission of that key to make sure you have the correct permissions to make the required changes. Are you sure the account you use is an administrator of the local computer? Unless the permissions on your computer is changed the administrators should have access to make changes in the registry.

Blackspear
November 4th, 2007, 08:31 AM
Hi there, please check the Registry Permissions:

1. Click on Start

2. Click on Run

3. Type in regedit

4. Click on OK

5. Right Click on HKEY_LOCAL_MACHINE

6. Click on Permissions

7. Click on Advanced

8. On the “Permissions” tab and make sure at the bottom of this window the following lines are ticked:

• Inherit from parent the permission entries that apply to child objects. Include these with entries explicitly defined here.

• Replace permission entries on all child objects with entries shown here that apply to child objects.

After the above, please try reinstalling a FRESH copy of NOD32.

Cheers ;D

creapure
November 7th, 2007, 07:23 AM
Hi Blackspear,

I am getting the same error message as Ryuman123.

I have tried your instructions, however on reaching step 8, when I click 'OK', I get a message saying "Registry Editor could not set security in the key currently selected, or some of its subkeys".

Any idea what I am doing wrong? Not sure why I am getting this error message, have never had this one before.

Would be grateful for any help.

Cheers

Crea

techtype
November 7th, 2007, 12:20 PM
-{ Quote: "Hi Blackspear,

I am getting the same error message as Ryuman123.

I have tried your instructions, however on reaching step 8, when I click 'OK', I get a message saying "Registry Editor could not set security in the key currently selected, or some of its subkeys".

Any idea what I am doing wrong? Not sure why I am getting this error message, have never had this one before.

Would be grateful for any help.

Cheers

Crea" }-

In order for these instructions to work, you should try running "regedt32.exe" instead of regedit.

ASM
November 7th, 2007, 02:27 PM
Mine don't work too... getting the error message, edit the registry... still the same.???

creapure
November 8th, 2007, 04:32 AM
-{ Quote: "In order for these instructions to work, you should try running "regedt32.exe" instead of regedit." }-

I thought with Win XP, both regedt32 and regedit were the same.

creapure
November 8th, 2007, 06:22 AM
OK guys, finally fixed it.... thanks to larryb52.... Here is what I did:

1) Uninstalled firewall (in my case Outpost Pro).
2) Used CCleaner for registry.
3) Installed Nod32 v3.0.
4) Installed my firewall (Outpost Pro).

Worked like a charm!

Hope this helps!!!

Cheers

Crea ;D

P.S: Thanks to everyone who tried to help! ;D :thumb: