PG 3.2 won't install

[Rui]

Hello

I have just tried upgrading my licensed PG from version 3.150 to version 3.2.
I uninstalled version 3.150 manually, according to Gavin's instructions at
http://www.wilderssecurity.com/showthread.php?t=16931

After rebooting, and when trying to install version 3.2 I get the following error message:

"Error writing to registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
RegSetValueEx failed; code 5
Access is denied"

So, it happens that PG driver is not installed and PG won't run.

I restored my system to a previously saved image, made just before trying to upgrade.

Note that PG 3.2 installation was tried with all security software disabled (KAV 5, RegDefend, Spysweeper).

Help will be much appreciated.

Best regards

Rui

[Mele20]

What OS and service pack?

[Rui]

Sorry, forgot to mention I am running XP Pro SP2 fully patched.

Originally Posted by Mele20

What OS and service pack?

[Osaban]

Originally Posted by Rui

Hello

Note that PG 3.2 installation was tried with all security software disabled (KAV 5, RegDefend, Spysweeper).

Rui

Hi there,

Look I don't know if this is a bit silly, but it happened to me: When you disabled Regdefend, did you actually do it from the GUI or you just exited RegDefend from the quick launch tray? If you don't disable Regdefend from the GUI it might block silently some installations.

[Gavin - DiamondCS]

Either that or PG driver is still installed and running, it must be uninstalled. Delete procguard.sys from Safe Mode if there is one there.. then install.

[Rui]

Hi Osaban and Gavin

Thank you very much for your responses.

Before Installing PG 3.2 I ensured that RegDefend (gss.exe) was not running.
Also ensuired that procguard.sys was not in Windows\system32\drivers folder, as well as procguard.dll and pguard.dat (these two in folder Windows\system32 folder) were removed from my system.
I have shut down Spysweeper's module "WRSSSDK.exe", too.
I have even shut down Outpost, so that the Anti-Spyware plug-in could not conflict with PG 3.2 installation.
All these procedures did not avoid the mentioned installation error.
Best regards
Rui

Originally Posted by Osaban

Hi there,

Look I don't know if this is a bit silly, but it happened to me: When you disabled Regdefend, did you actually do it from the GUI or you just exited RegDefend from the quick launch tray? If you don't disable Regdefend from the GUI it might block silently some installations.

Originally Posted by Gavin - DiamondCS

Either that or PG driver is still installed and running, it must be uninstalled. Delete procguard.sys from Safe Mode if there is one there.. then install.

I too have gotten this error at the windows xp logon screen, I type my username/password and the I get access denied, I can login fine in safemode with same info, and after uninstalling process guard 3.2 I have no problems and have reinstalled 3.15 without any issues.

was something with the driver the wasnt uninstalled in normal mode... did uninstall in safemode as mentionned in upgrade sticky and everything is fine didnt keep my configuration though..

[redwolfe_98]

this sounds like a major issue.. unfortunately, i don't have the "old" build 3.15 backed up..

can diamondcs make a download for build 3.15 available at the diamondcs website, somehow, for people who might need to reinstall build 3.15?

[Rui]

Hi redwolfe_98

I have just sent you a PM. Please check it.
Regards
Rui

Originally Posted by redwolfe_98

this sounds like a major issue.. unfortunately, i don't have the "old" build 3.15 backed up..

can diamondcs make a download for build 3.15 available at the diamondcs website, somehow, for people who might need to reinstall build 3.15?

I successfully booted into windows xp with Processguard 3.2, reconfigured process guard and upon rebooting got the same access denied error, again going into safemode was the only way to go past it, since I couldnt make any changes to the config in safemode then only solution was to uninstall and reinstall once again. I was playing with the protection tab initially, most likely gave read protection to something I shouldnt have and it was causing problems upon reboot. Didnt feel like testing out which one was causing the issue since I didnt wanna have to uninstall/reinstall each time. I noticed that some of the windows files in the protection tab have locked settings that we couldnt be changed. I thought I could change the rest of em but guess not .

Anyways reconfigured one last time giving read protection to none of the items and maybe tweaking a little less then I should have. I'll have a look at some more guides on this site to get a better idea of how to use the program.
Seems like something was missed or could be added to those locked settings to prevent this from happening to others.

[Remouald]

Originally Posted by Rui

H

Before Installing PG 3.2 I ensured that RegDefend (gss.exe) was not running.

As Osaban wrote, you must disable Regdefend from the GUI, switching from "RDStandard" to "<DISABLED>" (on the main table - security components). If you exit it from the tray you won't see gss.exe as a running process (on Task manager) BUT Regdefend will still be active and will block any protected area from the registry.

[redwolfe_98]

where are y'all getting PG 3.2 from? i downloaded the file from the "memeber's area", and got build 3.15 (?) (which happened to be what i wanted) i am just wondering where y'all are getting build 3.2 from since the download in the member's area is still build 3.15..

[Hexaguano]

Check the first sticky in this forum.

[redwolfe_98]

thanks hexaguano

[Rui]

Hi Remouald

That detailed explanation of yours happened to solve my problem!
Unfortunately, I did not understand well Osaban's previous explanation...
Thank you very much!
Best regards
Rui

Originally Posted by Remouald

As Osaban wrote, you must disable Regdefend from the GUI, switching from "RDStandard" to "<DISABLED>" (on the main table - security components). If you exit it from the tray you won't see gss.exe as a running process (on Task manager) BUT Regdefend will still be active and will block any protected area from the registry.