Test version 1.9.0.581 released (and now: 590)

jv16

Here is a test version 1.9.0.590:

(Download link removed, the final version has already been released)

It contains these bug fixes:

http://www.macecraft.com/bugtracker/list_next_version_fixed_bugs/

And improvements to the debugging system made in order to fix the problem of the Registry Cleaner freezing before completing the scan. So, if you experience the problem of the Registry Cleaner not ever finishing, please create a debug log and send it to this thread.

All feedback including bug reports about this test version should be sent to this thread using the "Post Reply" button. You can install this version over any existing version of jv16 PowerTools 2009.

This version is released here for testing because of the large number of changes (bug fixes), and because a few issues that were not yet fixed (Registry Cleaner hanging on some systems). The final version will be released after these issues have been solved, hopefully within a week.

Warning: This version is ment for testing purposes only.

Warning: This version contains more debug code than the release versions, therefore it will work much slower and produce larger debug logs when ran in Debug Mode. Only download and try this version if you want to help the development.

roxie

Beta still fails to find a significant number of "Invalid Files or Folders" Bug Report #317213 Sent new zip file showing errors directly to jv16

tullik

On Vista BE x32

Using the most aggressive settings, but excluding MRU/History, the 581 Registry Cleaner finds 117 items in 14 categories that are not found by the 580 Registry Cleaner. Note: There are very likely more than the 117 HKCR items since I suppressed HKLM items.

I haven't checked all the displayed categories yet, but here's two with anomalies:

1. Error relating to File or directory "C:\Users\Owner\AppData\Local\Apple\Apple Software Update\" does not exist

That folder indeed does not exist. However, the category shows in the results list with a zero detail count. That is, there is the category header line, but there is no detail under it.

Added note: This line appeared consistently in subsequent scans, until I deleted 10 uncomplicated categories. Then it no longer showed.

Using Registry Finder, I found this structure containing the Apple Software Update reference (shown in hex because of the data type):

Windows Registry Editor Version 5.00

"PackageName"="QuickTime.msi"

"LastUsedSource"=hex(2),00,3b,00,33,00,3b,00,43,00,3a,00,5c,00,55,00,73,00,\

65,00,72,00,73,00,5c,00,4f,00,77,00,6e,00,65,00,72,00,5c,00,41,00,70,00,70,\

00,44,00,61,00,74,00,61,00,5c,00,4c,00,6f,00,63,00,61,00,6c,00,5c,00,41,00,\

70,00,70,00,6c,00,65,00,5c,00,41,00,70,00,70,00,6c,00,65,00,20,00,53,00,6f,\

00,66,00,74,00,77,00,61,00,72,00,65,00,20,00,55,00,70,00,64,00,61,00,74,00,\

65,00,5c,00,00,00

"1"=";"

"1"=hex(2),00,3a,00,5c,00,55,00,73,00,65,00,72,00,73,00,5c,00,4f,00,77,00,\

6e,00,65,00,72,00,5c,00,41,00,70,00,70,00,44,00,61,00,74,00,61,00,5c,00,4c,\

00,6f,00,63,00,61,00,6c,00,5c,00,54,00,65,00,6d,00,70,00,5c,00,49,00,58,00,\

50,00,39,00,31,00,30,00,2e,00,54,00,4d,00,50,00,5c,00,00,00

"2"=hex(2),00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,44,00,\

61,00,74,00,61,00,5c,00,41,00,70,00,70,00,6c,00,65,00,20,00,43,00,6f,00,6d,\

00,70,00,75,00,74,00,65,00,72,00,5c,00,49,00,6e,00,73,00,74,00,61,00,6c,00,\

6c,00,65,00,72,00,20,00,43,00,61,00,63,00,68,00,65,00,5c,00,51,00,75,00,69,\

00,63,00,6b,00,54,00,69,00,6d,00,65,00,20,00,37,00,2e,00,32,00,2e,00,30,00,\

2e,00,32,00,34,00,30,00,5c,00,00,00

"3"=hex(2),00,3a,00,5c,00,55,00,73,00,65,00,72,00,73,00,5c,00,4f,00,77,00,\

6e,00,65,00,72,00,5c,00,41,00,70,00,70,00,44,00,61,00,74,00,61,00,5c,00,4c,\

00,6f,00,63,00,61,00,6c,00,5c,00,41,00,70,00,70,00,6c,00,65,00,5c,00,41,00,\

70,00,70,00,6c,00,65,00,20,00,53,00,6f,00,66,00,74,00,77,00,61,00,72,00,65,\

00,20,00,55,00,70,00,64,00,61,00,74,00,65,00,5c,00,00,00

2. Error relating to File or directory "G:\it54\bin\intel.rel\itircl54.dll" does not exist

That file indeed does not exist. However, the category, per Open in RegEdit, references all the items shown below, and the green one does exist. It does not actually show in the item's detail line or its caption area, so the bug is invisible unless you do the Open in RegEdit.

It seems the program is not properly analyzing the nested CLSID situation that exists in the structure.

Windows Registry Editor Version 5.00

@="Microsoft Infotech ITIR Word Normalizer"

@="Microsoft Infotech ITIR Default Dataspace Node"

@="G:\\it54\\bin\\intel.rel\\itircl54.dll"

"ThreadingModel"="both"

@="Microsoft.ITIR.DefDataSpaceNode.5.4"

@="Microsoft.ITIR.DefDataSpaceNode"

@="c:\\Program Files\\Common Files\\Microsoft Shared\\Information Retrieval\\itircl54.dll"

"ThreadingModel"="both"

@="Microsoft.ITIR.WordNormalizer.5.4"

@="Microsoft.ITIR.WordNormalizer"

07-28-2009_14-23-32.jpg

tullik

On Vista BE x32

I don't know if these two additional displayed categories are potential problems, but they have anomalies. I'll attach a zip directory so the two categories can be reproduced. The other 10 categories appear to be uncomplicated "does not exist" situations:

3. Error relating to File or directory "C:\Windows\system32\rdpencax.ocx" does not exist

InprocServer32 key data references %SystemRoot%\system32\rdpencom.dll which does exist.

ToolboxBitmap32 key data references %SystemRoot%\system32\rdpencax.ocx which does not exist.

4. Error relating to File or directory "d:\cec4291dc15b1a5fe512300ed850eb\" does not exist

There are two references in the key structure's data to this nonexistent folder, but only one is shown in the results list.

Entries.reg .zip

tullik

The "all done" counts are incorrect for Error relating to File or directory " . . . " does not exist categories.

The last line in the message window screenshot is for the Invalid file or directory reference category. It appears to be correct.

07-28-2009_16-46-12.jpg

07-28-2009_17-12-09.jpg

siliconman01

This is Vista SP2 x64 Business.

In most aggressive scan mode, Beta 581 detects the two keys below which are related to Vista SideBar gadget named VolumeGadget. Build 580 does not detect these. Removal of these two keys breaks the gadget.

@="Volume Class"

@="{052DB226-BE3B-44D4-B932-9C8049B2110B}"

@="VolumeControl.Volume.1"

@="Volume Class"

@="{052DB226-BE3B-44D4-B932-9C8049B2110B}"

siliconman01

This is Vista SP2 x64 Business.

In most aggressive scan mode, Beta 581 detects the following key related to nonexistent file C:\Windows\system32\rdpencax.ocx. On doing a FIX, the beta says it removes the key...no error messages occur. The key is, however, unremovable because of permissions.

Beta 581 even builds a backup file which is attached. NOTE in the backup file that it shows the deletion of keys which are not even shown as detected keys in the B581 scan. File rdpencom.dll is existing in the System32 folder. Build 580 did not detect the above.

@="RDPViewer Class"

@=hex(2),00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\

00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,64,00,\

70,00,65,00,6e,00,63,00,6f,00,6d,00,2e,00,64,00,6c,00,6c,00,00,00

"ThreadingModel"="Apartment"

@="0"

@="131473"

@="Rdpvcomapi.RDPViewer.1"

@=hex(2),00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\

00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,72,00,64,00,\

70,00,65,00,6e,00,63,00,61,00,78,00,2e,00,6f,00,63,00,78,00,2c,00,20,00,31,\

00,00,00

@="{CC802D05-AE07-4C15-B496-DB9D22AA0A84}"

@="1.0"

@="Rdpvcomapi.RDPViewer"

jv16

tullik wrote

2. Error relating to File or directory "G:\it54\bin\intel.rel\itircl54.dll" does not exist

That file indeed does not exist. However, the category, per Open in RegEdit, references all the items shown below, and the green one does exist. It does not actually show in the item's detail line or its caption area, so the bug is invisible unless you do the Open in RegEdit.

It seems the program is not properly analyzing the nested CLSID situation that exists in the structure.

Windows Registry Editor Version 5.00

This is by design. In the most aggressive setting (starting with version 581) the program will list the entire HKCR key as invalid if it contains one incorrect path. The less aggressive settings do not do this.

tullik

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.

jv16

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.

jv16

Updated version 582 released, the new version should fix the problem reported by Roxie. And the one reported by Tullik above.

jv16

siliconman01 wrote
This is Vista SP2 x64 Business.

In most aggressive scan mode, Beta 581 detects the two keys below which are related to Vista SideBar gadget named VolumeGadget. Build 580 does not detect these. Removal of these two keys breaks the gadget.

This is now fixed, thank you for reporting! The fix will be included to build 583.

jv16

tullik wrote
The "all done" counts are incorrect for Error relating to File or directory " . . . " does not exist categories.

Which counts exactly are incorrect?

roxie

jv16 wrote

This is by design. In the most aggressive setting (starting with version 581) the program will list the entire HKCR key as invalid if it contains one incorrect path. The less aggressive settings do not do this.

Does this mean the Cleaner has to be run in the most aggressive mode to detect other "invalid files or directories?" Is there a way to warn that the entire HKCR key is being listed even if it contains only one incorrect path?

Just ran 582 in the next to the highest mode and it found 10 invalid files or directories, but then ran it in the most aggressive and it found over 8000 and listed them in individual categories (which I like) rather than lumping them in one large group.

tullik

jv16 wrote
tullik wroteThe "all done" counts are incorrect for Error relating to File or directory " . . . " does not exist categories.

Which counts exactly are incorrect?

The message line for those categories always says "1 registry entries and 1 registry keys." In every case, there were many entries and keys. I'm sure the byte count is wrong also.

tullik

On Vista BE x32

582 fixed the list name & value issue discussed above.

It listed 22 categories. That's 8 more than shown with 581. 580 listed nothing.

Most of the increase is apparently due to an expansion of the aggressive HKCR policy. Single items under the Invalid file or directory reference category in 581 have become multiple item new categories in 582.

Two of the categories have no detail in them (see screenshot). That's likely a bug in your consolidation logic.

07-29-2009_08-37-01.jpg

siliconman01

This is on Vista SP2 x64 Business.

Beta V582 is indicating that it is not scanning the 64-bit part of the registry. The number of values and keys scanned is less than 50% that of Build 580. The scan completes approximately 35 seconds quicker than Build 580. I think this was happening in Beta V581 too.

tullik

On Vista BE x32 Registry Cleaner

If none of the categories are expanded, Select-->All (or Ctrl+A) selects everything, but does not update the status bar selected count until you expand one of the categories.

Similar thing happens with Select-->None (or Ctrl+N).

And with Select-->inverse.

siliconman01

This is on Vista SP2 x64 Business.

There is something definitely screwy on x64. I exported the entire key for safe keeping. Then I changed its permissions and deleted the entire key. On running an aggressive scan with B582, it shows the key as existing. If I use the 'Open in Regedit" option, it opens to just the CLSID section of the registry...not on to 32be5ed............

redseujac

Registry Finder

I realize now that the message "At least one search method..." is ambiguous and misleading, because one of the tabs is titled "Search method" and has nothing to do with the final goal of the error message.

Indeed under the tab "Search method" I find:

- Normal, Case insensitive, loose match search

- Case insensitive wildcard search

- Pearl regular expression search

- Artificial Intelligence search

Those search methods are not intended with the error message :

I propose to replace "search method" by "search argument" there.