Registry Cleaner Build 580 Internal Error

redseujac

And "accured" (i.e. occurred) also I guess :

boofo

So, I guess "tevelision" would be wrong, too? ;)

All seriousness aside, they have this on the newsletter error page.

Macecraft Software Newsletter subscription verification

You have NOT been subscribed to selected Macecraft Software newsletter(s) due to an iternal error.

redseujac

Well I guess it should be "eternal" error instead of "iternal" :

boofo

Something like that. ;)

aar1

Not so - After updating to .580 I get the same suff as previously reported using Vista Ultimate - I reported twice and this morning advised it was being kick upstairs - until I get a fix am not trying it on my XPS-435 running Windows 7 RC

aar1

In addition to reporting the Internal Error: SafetyNetV2 I also reported the following after "trying to update" the Vista Ultimate machine to SP2 - Error E_Failed (0x80004005) but no reply to that report yet, been several days now. I ran an webscan for this type error and found numerous "registry cleaning" programs that indicated they can fix the "error e_failed (0x80004005) and advertise that fact - still waiting for thses guys to reply to my bug report.

redseujac

redseujac wrote
...And indeed, when I do a registry scan in that "aggressive mode", I get several messages as reported in this thread!

Further investigation learns that the error messages occur during the Final Analysis following the ActiveX/COM/DCOM/... scan!

hawkeyelom

Using Vista 32bit ultimate I get the same erros as 0thers have reported whn Activex/Dcome etc are selectd--either by themswelves or as the only one selected. I beleieve this strted after Vistq SP2 was installed.

redseujac

hawkeyelom wrote
...I beleieve this strted after Vistq SP2 was installed.

I don't think so, because - as you can read in my signature - my OS = Vista Ultimate SP1.

jv16

This indeed seems to be a real issue. The error message mainly means that the data got from the registry cleaner engine does not match the data in the registry.

This can mean only two things:

1. Something is wrong in the registry cleaner engine.

2. The data has been changed in the registry between the time it was read by the engine, and the time the data was re-checked by the SafetyNetV2.

Most of the cases I have seen seems to suggest case 2, but it's still an annoying popup when it does occur. I will try to find a way to fix it for the next version, without giving away too much of the extra safety the system also provides.

slroberts42

This error is also happening on my HP laptop with Windows XP SP3, so it is not related to the newer operating systems. I have submitted a bug report with attachment showing the error message and the resulting list of errors found.

redseujac

SLRoberts42 wrote
... so it is not related to the newer operating systems...

I can't remember someone has said it was...

tullik

With Windows 7 Ultimate Build 7100 and an aggressive scan (slider at the bottommost position), I get about a half dozen of these internal error pop-ups.

Some occur whether or not I choose the "Deep analysis scan."

I can suppress the ones I get with these "Ignore words:"

\Interface\

\Clsid\

ROOT\eh

jxrgaf8npjen

jv16 wrote
This indeed seems to be a real issue. The error message mainly means that the data got from the registry cleaner engine does not match the data in the registry.

This can mean only two things:

1. Something is wrong in the registry cleaner engine.

2. The data has been changed in the registry between the time it was read by the engine, and the time the data was re-checked by the SafetyNetV2.

Most of the cases I have seen seems to suggest case 2, but it's still an annoying popup when it does occur. I will try to find a way to fix it for the next version, without giving away too much of the extra safety the system also provides.

Hello.

So what do you recommend? As long as this is not fixed no registry clean-up?

tullik

JxrgAf8npjEN wrote
... So what do you recommend? As long as this is not fixed no registry clean-up?

This post from the PTLite forum suggests an interim approach: Cosmetic?

tullik

jv16 wrote
This indeed seems to be a real issue. The error message mainly means that the data got from the registry cleaner engine does not match the data in the registry.

This can mean only two things:

1. Something is wrong in the registry cleaner engine.

2. The data has been changed in the registry between the time it was read by the engine, and the time the data was re-checked by the SafetyNetV2.

Most of the cases I have seen seems to suggest case 2, but it's still an annoying popup when it does occur. I will try to find a way to fix it for the next version, without giving away too much of the extra safety the system also provides.

The screenshot shows the keys (excepting the RegEdit item) for which I consistently get "Internal Error: SafetyNetV2, error code two" on my W7 x-32 system.

The dates suggest your reason #1 applies for these keys.

A PTLite user has reported "Internal Error: SafetyNetV2, error code four" involving the Reg Edit applet. Perhaps your reason #2 applies to that.

Other observations:

The pop-ups I'm getting show the HKCR key, not the HKLM key.

The pop-ups occur whether or not the deep analysis option is chosen.

Sometimes the progress indicator does not show until the program enters the final scan phase (another bug).

06-14-2009_17-11-45.jpg

michael_in_atl

FWIW, I get SafetyNet2,error code 2, CallID Regcleaner 1a on my system, which is XP Professional. Key\Software\WexTech.

Response from Customer Support was to hit OK, and this will be fixed in the next release. I have no idea what functions are left incomplete.

« Previous Page