Errors re: software deep trace items

laserfan

I installed and ran 2013 this a.m. on my W7HPx64 and when I try Registry Cleaner it finds over 1500 errors in the HKCR\Wow6432Node\clsid area, most of which are related to Java plugins, many of which appear to be for old versions never installed on this PC, as if latest Java installs every old one ever released regardless. Anyway when I let jv16PT attempt to clean these, I got hundreds of errors that it could not delete the keys, which seemed to indicate a Permissions problem as discussed elsewhere here. But later when I run jv16 again, it indicates all these were indeed cleared-out i.e. when I run Reg Cleaner again it does not find these entries any longer. So I open Regedit.exe and indeed it does seem that they were cleared-out after all--here is just one example:

HKCR\Wow6432Node\clsid\{cafeefac-0015-0000-0021-abcdeffedcbb}\ - @ - Java Plug-in 1.5.0_21 - 04.04.2012, 09 - 35 - Software deep trace item Fix registry error (by removing the data)

So why would jv16PT report problems deleting these, then apparently be able to do so anyway?

When I search in Regedit.exe on cafeefac-0015-0000-0021-abcdeffedcbb I find this still appears in HKCR\CLSID and also HKLM areas, so it was only cleared from Wow6432Node. Why would these be cleared from Wow6432Node but not these others?

Finally is there any place that I can look to see the errors jv16PT reported in the first run? Are these not saved to a log file?

redseujac

laserfan wrote
Finally is there any place that I can look to see the errors jv16PT reported in the first run? Are these not saved to a log file?

If you let the Registry Cleaner make a backup before deleting the erroneous entries, then normally you'll be able to find the errors in the backup tool.

laserfan

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

laserfan

I just made another Registry Cleaner run and again had errors though the handling was different this time:

1. There were 10 entries selected for deletion

2. All 10 were backed-up as requested

3. Errors were shown in the status window below for 2 of them: "Failed to modify "HKEY..."

4. This time these keys remain behind and weren't removed

5. I run Registry Cleaner again and again get the errors

6. I can find no evidence that these errors were encountered in the first place

Ignoring the oddity of my first report (it SAID it couldn't modify the keys but then actually did), in this second report it can't modify the keys and leaves them behind.

What I find problematic is that jv16 does not appear to log the errors anywhere, so if a user is not paying attention to the status window, or closes that window inadvertently, there is no way to identify that the cleaning did not occur successfully.

BTW and FYI it appears that one may be able to get-around the issue of PT's not being able to delete keys (the Permissions problem) by running PT under Sysinternal's PsExec as System, i.e. this:

psexec -s -i "C:\Program Files (x86)\jv16 PowerTools 2013\jv16PT.exe"

I've used psexec in the past to run Regedit for this purpose (to delete keys) but it only recently occurred to me to try it with jv16PT and I would be interested to hear any other comments about this.

laserfan

Thanks to whoever moved this to the 2013 area which didn't exist yet when I posted my question.

I still do not understand why jv16PT 2013 does not appear to log-or-save the errors it displays in the Status area when doing in this case a Registry Cleaner operation.

redseujac

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

laserfan

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.