1053, registry cleaner will not delete...

arctucas

I updated my Java Runtime Environment from version 6 (update 26) to version 7.

I ran the Registry Cleaner and it found a lot of entries, but would not delete several, and I had to manually delete them.

Should the Registry Cleaner not delete all the erroneous keys?

leonardo

Arctucas wrote

I updated my Java Runtime Environment from version 6 (update 26) to version 7.

I ran the Registry Cleaner and it found a lot of entries, but would not delete several, and I had to manually delete them.

Should the Registry Cleaner not delete all the erroneous keys?

Well that depends on registry ownership & permission!

jv16PT does not have unlimitted ownership/permission, as user tullik explained earlier.

On rare occasions the user must first manually reset ownership/permission in order to get the erroneous key's deleted.

Tullik created a procedure for this, see the attached .zip file.

arctucas

Leonardo wrote
Arctucas wrote

I updated my Java Runtime Environment from version 6 (update 26) to version 7.

I ran the Registry Cleaner and it found a lot of entries, but would not delete several, and I had to manually delete them.

Should the Registry Cleaner not delete all the erroneous keys?

Well that depends on registry ownership & permission!

jv16PT does not have unlimitted ownership/permission, as user tullik explained earlier.

On rare occasions the user must first manually reset ownership/permission in order to get the erroneous key's deleted.

.

Tullik created a procedure for this, see the attached .zip file.

.

I understand that, having had to take ownership and/or change permissions for other items.

However, in this instance, I merely went to the key that the registry cleaner identified and deleted them, no changes required.

redseujac

Arctucas wrote
I updated my Java Runtime Environment from version 6 (update 26) to version 7.

I ran the Registry Cleaner and it found a lot of entries, but would not delete several, and I had to manually delete them.

I did the same (upgraded java to version 7), ran the registry cleaner and all found entries were deleted without any problem.

I must specify that I uninstalled the previous java version (6 update 26) before running the registry cleaner.

arctucas

redseujac wrote
Arctucas wroteI updated my Java Runtime Environment from version 6 (update 26) to version 7.

I ran the Registry Cleaner and it found a lot of entries, but would not delete several, and I had to manually delete them.

I did the same (upgraded java to version 7), ran the registry cleaner and all found entries were deleted without any problem.

I must specify that I uninstalled the previous java version (6 update 26) before running the registry cleaner.

Perhaps that is the solution.

I installed JRE 7, but did not uninstall JRE 6 update 26 first.

I uninstalled JRE 6 update 26 afterwards, and then found the various leftover registry entries.

Even so, I would like to believe the registry cleaner would delete those entries.

By the way, the registry cleaner did give any errors, it simply did not remove the entries, even though it cleared them from the list. Running another scan, those same entries reappeared, until I manually deleted them.

leonardo

Arctucas wrote
Leonardo wrote
Arctucas wrote

I updated my Java Runtime Environment from version 6 (update 26) to version 7.

I ran the Registry Cleaner and it found a lot of entries, but would not delete several, and I had to manually delete them.

Should the Registry Cleaner not delete all the erroneous keys?

Well that depends on registry ownership & permission!

jv16PT does not have unlimited ownership/permission, as user tullik explained earlier.

On rare occasions the user must first manually reset ownership/permission in order to get the erroneous key's deleted.

.

Tullik created a procedure for this, see the attached .zip file.

.

I understand that, having had to take ownership and/or change permissions for other items.

However, in this instance, I merely went to the key that the registry cleaner identified and deleted them, no changes required.

If jv16PT could not delete these key's, but you could manually delete these entries without changing either ownership or permission,

I think jv16 should be informed about these key's. Can you reproduce this issue?

arctucas

Leonardo wrote
<SNIP>If jv16PT could not delete these key's, but you could manually delete these entries without changing either ownership or permission,

I guess jv16 should be informed about these key's. Can you reproduce this issue?

Possibly.

It is not the first time I have had registry entries that would be reported as errors by the registry cleaner, but would not be deleted, and could be manually deleted by simply navigating to the entry using regedit.exe and deleting.

If it could be made so the registry cleaner would delete them, fine.

But it is not really that much of a problem to use the registry cleaner to identify them, and then manually delete them.

arctucas

I encountered two more entries that the registry cleaner identifies as errors and will not delete, but can be deleted from regedit without changes to any permissions or the like.

I had uninstalled SpyBot Search&Destroy 2.0 BETA3, and nVIDIA Forceware 280.28.

Each left a registry entry that was manually deletable, but the registry cleaner would not delete.

At least the registry cleaner finds the entries, allowing me to manually delete them.

leonardo

Arctucas wrote
I encountered two more entries that the registry cleaner identifies as errors and will not delete,

but can be deleted from regedit without changes to any permissions or the like.

I had uninstalled SpyBot Search&Destroy 2.0 BETA3, and nVIDIA Forceware 280.28.

Each left a registry entry that was manually deletable, but the registry cleaner would not delete.

At least the registry cleaner finds the entries, allowing me to manually delete them.

As said before: I think jv16 would like to be in formed about these key's you mentioned. Personally I never experienced this.

If jv16PT could not fix/remove the found erroneous key's, manual changes in ownership/permission were needed before I could manually delete these key's.

arctucas

Leonardo wrote
As said before: I think jv16 would like to be in formed about these key's you mentioned. Personally I never experienced this.

If jv16PT could not fix/remove the found erroneous key's, manual changes in ownership/permission were needed before I could manually delete these key's.

Does he not read these forum posts?

If you are going to suggest I submit a ticket, save your breath. I have tried several times in the past for other issues, but as I never got a reply, I decided to try posting here in the forum.

If posting here does not work, I suppose I am out of luck. Although, the issue I am attempting to address is more of an inconvenience than a 'problem'. And, as I did not record any specific information regarding the keys in question, the point is probably moot.

But, thanks anyway.

arctucas

Here are two errors that the registry cleaner finds and will not delete, but I am able to manually delete:

arctucas

BUMP

Having had no response for nearly a month-and-a-half, I was wondering what ever happened, if anything?

arctucas

And another three weeks with nary a reply...

I really just want confirmation this is normal, or maybe it is not and someone is investigating, or perhaps a 'we have no idea what it is you are going on about'...