jv16 pt 2005 Doesn't remove all the found Registry Entries

optikl

When I try to fix or remove registry entries, using the registry cleaner, I'll get a prompt to back-up. When I chose to back-up and assign a name to the file, jv16 doesn't always fix or remove everything on the first pass. In other words, some items stay *checked* and remain on the screen until I go through the process, again.

This does not occur when I use RegSupreme Pro.

I'm using the lates build of jv16.

The system I have jv16 installed on is a Windows XP SP2 system.

Is this a bug, or by design?

optikl

optikl wrote
When I try to fix or remove registry entries, using the registry cleaner, I'll get a prompt to back-up. When I chose to back-up and assign a name to the file, jv16 doesn't always fix or remove everything on the first pass. In other words, some items stay *checked* and remain on the screen until I go through the process, again.

As a test, I installed jv16 2005 on a Windows2K Pro laptop of mine. Same result.

Am I doing something wrong?

optikl

Bones wrote
The same thing happened to me as well only, JV16 Didn't remove anything the first time. The second time it worked.

Well, I've seen that happen too. Today in fact, while I was testing. So, it's probably not just me. I might just use RegSupreme for registry cleaning until I understand what's going on. thanks.

optikl

Bones wrote
Just out of curiosity, do you find Reg Supreme to be a more stable product?

I also have a license for RegSupreme Pro. I don't experience these same issues with it. So, I guess I'd say it appears to be more predictable. But then again, it has many fewer features than jv16.

easymode

Same problem here (sometimes).

jv16

Could you check the Help > About box what version of the product you are running?

optikl

jv16 wrote
Could you check the Help > About box what version of the product you are running?

I'm running build 277. I just tried it again. Found 10 errors and tried to fix all 10, making back ups, first. It let me do 4, then stopped. Had to close program and rescan. Found the other 6 (all were marked high, BTW- in the past, there seemed to be a segregation of fixing by high, medium and low).

Let me fix 2, then stopped. Finally I rescanned and just deleted with out back up and it took care of it. I definitely don't see this problem with RegSupreme Pro. I've tried this on 2 different systems. 1 Windows XP SP@ and this system, Windows 2K SP4. Same results.

jv16

Are you logged in as the administrator to the computers?

optikl

jv16 wrote
Are you logged in as the administrator to the computers?

On the Win2K machine, I am a "power user". On the WinXP machine, I am an adminstrator.

redwolfe_98

when i was using jv16pt 2005 (build 277), i did not experience the same problem, but there could have been an "update" for the program that introduced addtiional bugs..

optikl

optikl wrote
jv16 wroteAre you logged in as the administrator to the computers?

On the Win2K machine, I am a "power user". On the WinXP machine, I am an adminstrator.

Just tried it again on my Win2k system, this time logged on under an Administrative account. After 3 tries of fixing registry entries, I finally had to remove the entries. Again, I get the same issue on two different machines; 1 Win2K SP4 and the other WinXP SP2.

optikl

optikl wrote
optikl wrote
jv16 wroteAre you logged in as the administrator to the computers?

Just tried it again on my Win2k system, this time logged on under an Administrative account. After 3 tries of fixing registry entries, I finally had to remove the entries. Again, I get the same issue on two different machines; 1 Win2K SP4 and the other WinXP SP2.

Hello? Any responses forthcoming? Is it just me, or is there an issue here? What concerns me is that with RegSupreme Pro very shortly being given a face-lift with the registry cleaning engine from jv16, I'll have this problem regardless of which Macecraft *licensed* product I use. I'd like to have something that when I click to fix, I get some kind of consistent response.

jv16

I'm trying to get it fixed for next version.

The problem shouldn't affect the new RegSupreme Pro 1.1 since its remove button works just like before. Only the registry cleaner engine (i.e. what items are listed) is changed.

optikl

Thanks. Greatly appreciated. :)

evil_psychiatrist

I´ve had this problem too on win2k SP4.