RegDefend interferes with Registry Cleaner

Discussion in 'Ghost Security Suite (GSS)' started by NormanS, Oct 10, 2005.

Thread Status:
Not open for further replies.
  1. NormanS

    NormanS Registered Member

    Joined:
    Feb 3, 2004
    Posts:
    84
    RegDefend, without waiting for permission, blocked JV16 from enumerating values.
    I have no idea of the consequences. So, I'm looking for a scheme to shut-down RegDefend, short of uninstalling it.

    Is there a solution?
     
    Last edited: Oct 10, 2005
  2. nick s

    nick s Registered Member

    Joined:
    Nov 20, 2002
    Posts:
    1,430
    Hi NormanS,

    The consequences of blocking enumeration will be that JV16 will literally not "see" those values. The first thing you should do is take a look at the log entries in the RD tab. Highlight one of the "Blocked" enumeration events and, in the Full Alert Information below, identify the Group responsible for blocking JV16. From there, open the Configuration editor and identify the Rule(s) within that Group that block Read Key and/or Read Value. Reset the rule(s) to allow and enable all the actions below. This will permit JV16 to do its job.

    Nick
     

    Attached Files:

  3. NormanS

    NormanS Registered Member

    Joined:
    Feb 3, 2004
    Posts:
    84
    Many thanks Nick.

    Your guidance on this issue has been A1.

    Norman :D
     
  4. Robyn

    Robyn Registered Member

    Joined:
    Feb 1, 2004
    Posts:
    1,189
    When I clean with my Registry cleaner after an uninstall I have never had an alert from RD o_O
    I will be uninstalling and cleaning up after a program over the next few days so will have to check the logs to see if anything
    is being blocked without asking. I am now curious as to why RD did not alert me previously o_O

    I use Registry First Aid.
     
  5. TopperID

    TopperID Registered Member

    Joined:
    Oct 1, 2004
    Posts:
    1,527
    Location:
    London
    Registry cleaners will usually be clearing the 'gumf' out of the less important nooks and crannies of the Registry, so I would guess you have not been cleaning a protected Key and hence have not been alerted.

    Now I think of it, I don't recall being prompted by RD while doing a Reg clean either! But Reg cleaners tend to be careful about what sort of things they clean.
     
  6. Robyn

    Robyn Registered Member

    Joined:
    Feb 1, 2004
    Posts:
    1,189
    me again and thank you.
    I understand this bit now but I did wonder at cleaning yet nothing.
    At least I know my Reg. cleaner must have been leaving protected keys alone and why I receive a prompt when I clean the junk with Ccleaner.

    Lots to learn with all these tools.
     
  7. TopperID

    TopperID Registered Member

    Joined:
    Oct 1, 2004
    Posts:
    1,527
    Location:
    London
    Funnily enough CCleaner isn't causing a pop-up 'cos its cleaning a protected item; rather it is trying to delete a value in the auto start part of the Registry which is protected by RD.

    This is 'cos you don't have CCleaner configured to operate at bootup (by clicking Options/Settings and ticking the box for 'Run CCleaner when comp starts'); CCleaner will continue to ensure its Reg settings match its configeration by deleting the relevant entry - even though the value isn't there at all!

    It does the same for me so I have given it permission to make the change by ticking the 'Allow Always' box in the RD pop-up.
     
  8. Robyn

    Robyn Registered Member

    Joined:
    Feb 1, 2004
    Posts:
    1,189
    Correct I don't have CC to run at start up ;)
    I haven't given it full permission as in 'always use' but I do permit when cleaning.
    Thanks for the info as to what it was trying to do.
     
Thread Status:
Not open for further replies.