RegDefend 1.300 performance problem

I guess the best description of what I am seeing is a sluggishness when using the GUI. One example (see below) is the length of time it takes for the GUI to "show up" when I click the tray icon the first time after startup. The GUI pops up much faster with subsequent clicks. Another example is that there is a noticeable lag (2-3 seconds) between clicking an item (like a Registry Group) and the GUI responding to it. This lag does not improve with subsequent clicks. The main popup alerts (not the balloon alerts) also generate slowly on the screen.

I have seen this on two systems so far, both running only PG, BOClean, and Outpost Pro. I am going to install it on a third running with only a clean XP Pro and see if things change.

Nick

 

Nick,

I've seen this also. When I shutdown Outpost, the sluggishness is gone. Really have no idea what's up here. I wouldn't think that they would interact like this (assuming it's not a third party conflict that I haven't noticed - but I assume it's not).

Here's a new wrinkle, on a lark I put Outpost in background mode - sluggishness is gone. This might drive me crazy.

Blue

 

Same problem here. I am using Outpost v2.5.375.4822 (374), PG 3.150, NOD32 v2.5, TH Guard 4.2 on XP SP2.

I was getting the following warnings from Outpost, but they seem to be gone now after a couple of reboots and reinstalls:

21:56:39 Process network access blocked REGDEFEND.EXE modified memory of REGDEFEND.EXE

I never had problems with RD v1.200 and below.

 

Hi blue,

Thanks for finding that. I had only shut PG and BOClean. RD worked fine on a clean install of XP. If I shut down OP, RD works well. I also see the same improvement with OP set to run in the background (no tray icon).

Nick

 

Could quite possibly be the issue with EXE protection I use (armadillo) and Outpost. I saw recently on the armadillo forum that Outpost has some protections which could possibly need some tweaking. Can you verify if the v1.200 was "as" sluggish as this v1.300 ? If it wasn't, send me an email (support@) and I will send you a new regdefend.exe which may fix the problem. If it does fix the problem I will silently update the existing build with the fix. Hopefully outpost will eventually address the issue themselves.

 

If this is related to Outpost's Open Process Control option (which blocks network access to any processes that may be modified), then this can be disabled via Options/Application/Components/Open Process Control. Process Guard can also be used to "protect" RegDefend as an alternative workaround (see the "Known Issues" section of Outpost 2.5 - what to expect for more details).

Being able to define exceptions for Open Process Control is supposed to be on the feature list for the next release of Outpost - no details of a release date though.

 

Details escape me. All I know is that I did not have Open Process Control enabled within Outpost, I still experienced the problem, and the build Jason mentions above seems to have resolved the problem.

Blue

 

The new executable resolves both the Open Process Control-related crash and the sluggish GUI issues I experienced. Disabling OP's Open Process Control did not remedy the sluggish GUI. In any case, RD is now running nicely .

Nick

 

The new build of RegDefend is available for the Outpost users. Please re-download the setup and reinstall following the normal instructions. Thanks to the people who tested.

 

The new build is working great here, no more issues.

Thanks everyone.

 

A sure sign of a well conceived, well-designed program is when issues such as this can be quickly addressed.

Rich

 

@Jason

It's interesting that you have decided to use Chad Nelson's Armadillo. Personally, I would have picked another protector. But let's wait and see.