Registry Cleaner 590 does not fix some errors

henry

PT 1.9.0.590 Registry Cleaner running in Agressive Mode under Windows 7 RC Build 7100 detected 108 errors related to ActiveX/DDE/COM/... However, after pressing the Fix button, none of the errors were cleaned. All errors remain as before even after repeated runs of Registry Cleaner. Other types of errors are fixed all right. The screenshot is attached. This is a clean install of PT 590.

jv16

What happens if you try to delete some of these items instead of fixing?

henry

With only one item selected, I pressed Delete. The effect is identical to pressing Fix. Nothing is deleted. The screen capture is attached. If I can be of assistance in debugging the symptom at this end, I will be happy to.

dinny

I get that but sometime using Delete removes them, in both W7 7100 x64 and Vista x32.

Other times I have to go into that "section" and delete all entries in it manually by selecting the entries one at a time.

henry

Dinny:

Thank you. I did try just about every combination that came to mind in order to get Registry Cleaner 590 to clean the errors, to no avail. Deleting one at a time or all at once does nothing. Custom Fix also leaves the errors in place but produces the message "Access denied of invalid key". The screenshot for the latter is attached. If you could spell out your procedure that works, I will try it on my W7 7100 x86.

dinny

Henry,

Yesterday I ran jv16 590 in Vista x32.

Errors were indicated,fix did not remove them - there about 7 of them.

Using Delete did not remove them.

Selecting only one of them maually and then pressing Delete did not work, I'm thinking they are in use in the OS.

I've just done 2 scans, here are the results.

I'm using FireFox3.5.1.= in Vista X32 (untill RTM W7 is released).

==========================================

These are in the scan setting "Normal Registry Cleaning"

HKEY_CLASSES_ROOT\clsid\{300165d9-44b1-4c7a-ad58-4a9e7200e2e8}\LocalServer32\@ : "%ProgramFiles%\Internet Explorer\IEUser.exe"

HKEY_CLASSES_ROOT\clsid\{300165d9-44b1-4c7a-ad58-4a9e7200e2e8}\LocalServer32\ServerExecutable : %ProgramFiles%\Internet Explorer\IEUser.exe

HKEY_LOCAL_MACHINE\Software\classes\clsid\{300165d9-44b1-4c7a-ad58-4a9e7200e2e8}\LocalServer32\@ : "%ProgramFiles%\Internet Explorer\IEUser.exe"

HKEY_LOCAL_MACHINE\Software\classes\clsid\{300165d9-44b1-4c7a-ad58-4a9e7200e2e8}\LocalServer32\ServerExecutable : %ProgramFiles%\Internet Explorer\IEUser.exe

HKEY_LOCAL_MACHINE\software\eset\eset security\currentversion\plugins\01000400\Profiles\@My profile\MirrorFolder : C:\ProgramData\ESET\ESET Smart Security\mirror

The Error description column for the first 4 are the same,

File or directory "C:\Program Files\Internet Explorer\IEUder.exe" does not exist.

The 5th is =

File or directory "C:\ProgramData\ESET\ESET Smart Security\mirror" does nt exist.

------------------------

Using the Safest registry Cleaning Policy =

No errors.

tullik

I just installed IE8. That triggered the "ieuser.exe" errors shown in Dinny's post.

I removed them with the PT Registry Cleaner after doing the permissions changes described in the quote:

tullik wrote
... the IE8 install removed C:\Program Files\Internet Explorer\ieuser.exe.

Then the Registry Cleaner found a CLSID key ({300165D9-44B1-4C7A-AD58-4A9E7200E2E8}) "error" in HKCR and HKLM because the file no longer existed.

The items could not be removed by Registry Cleaner because TrustedInstaller "owned" the keys (and subkeys).

I used RegEdit to add my userid to the HKCR key (and one subkey), and give ownership to my userid instead of TrustedInstaller.

Then the items could be removed by Registry Cleaner.

Based on all that, I believe the errors (as described) can be safely removed if you have IE8 on your X86 system. ...

henry

Tullik:

Thank you for the info. I checked the permissions and ownership of e few of the 108 registry keys detected as errors. Some are indeed owned by TrustedInstaller but other are owned by SYSTEM. The administrators (my userid) have read only permission on some keys and full control on others. Also, I do not have any browsers other than IE8 that came with Windows 7. My system is what you may call vanilla: it has no hacks whatsoever and it works very well. I would much prefer that Regisgtry Cleaner fixed the detected errors, as usual, rather than me having to change the ownership of registry keys. Does jv16 recommend your suggestion as the workaround? Thank you again.

tullik

Henry wrote
Tullik:

Thank you for the info. I checked the permissions and ownership of e few of the 108 registry keys detected as errors. Some are indeed owned by TrustedInstaller but other are owned by SYSTEM. The administrators (my userid) have read only permission on some keys and full control on others. Also, I do not have any browsers other than IE8 that came with Windows 7. My system is what you may call vanilla: it has no hacks whatsoever and it works very well. I would much prefer that Regisgtry Cleaner fixed the detected errors, as usual, rather than me having to change the ownership of registry keys. Does jv16 recommend your suggestion as the workaround? Thank you again.

My more or less vanilla W7 Build 7100 also has several keys with "errors" where the "Administrators" group, and thus PowerTools, does not have "Full Control."

The immediate, and likely recommended, workaround is use of the "Ignore words" tab. Anyway, that's what I normally do for such cases.

IMO, most such instances are oversights by the MS folks that put together the build.

dinny

I have just come in to make a reply similar to Henrys, I could not get tuliks sugestions to work,

or rather I was doing the wrong things.

Anyway, I'll have a look at your last post and have a go at that.

tullik

Dinny wrote
I have just come in to make a reply similar to Henrys, I could not get tuliks sugestions to work,

or rather I was doing the wrong things.

Anyway, I'll have a look at your last post and have a go at that.

That RegEdit permissions change thing can be sort of tricky. It sometimes requires a certain order.

If you start with the last key in the structure and work up the tree, it should work.

The procedure is something like this; starting at the last key in the structure:

1. From the menu, select "Permissions"

2. In the first pop-up, click-->Add, type your userid-->click Check names-->OK (twice), then click "Advanced"

3. Click the "Owner" tab-->select your userid from the list-->click Apply, then OK

4. Check "Full control" for your userid-->Apply-->OK

5. If at the top of the structure, look at 7. Otherwise,

6. For the next low key in the structure, repeat 1 through 5

7. You (and PowerTools) should now have "Full control" of the keys in the structure

uriel

That RegEdit permissions change thing can be sort of tricky. It sometimes requires a certain order.

If you start with the last key in the structure and work up the tree, it should work.

The procedure is something like this; starting at the last key in the structure:

1. From the menu, select "Permissions"

2. In the first pop-up, click-->Add, type your userid-->click Check names-->OK (twice), then click "Advanced"

3. Click the "Owner" tab-->select your userid from the list-->click Apply, then OK

4. Check "Full control" for your userid-->Apply-->OK

5. If at the top of the structure, look at 7. Otherwise,

6. For the next low key in the structure, repeat 1 through 5

7. You (and PowerTools) should now have "Full control" of the keys in the structure

Thank you

After wasting a few hours looking for a cure to this headache, I followed these directions line for line and it worked.