Registry Finder - a search failure (v.1.8.0.455)

tullik

Registry Finder - a search failure (v.1.8.0.455)

With the settings shown in the thumbnails, Registry Finder finds nothing.

What it finds with v.1.8.0.449 with the exact same settings is shown in the results window screenshot.

Search words . . . . . . . . . . Options . . . . . . . . . . . . . . Ignore words

~~... ~~...~~~~

~~Registry Finder results window v.1.8.0.449~~

redseujac

Confirmed
...

That issue in the most recent version should be fixed (again) in the next release :

tullik

Registry Finder - another search failure instance (v.1.8.0.455)

In the case below (on Vista), the tool found the desired high level keys in HKCR, but did not find the corresponding keys in HKLM.

Settings:

The search word: \Search.

The options: search HKLM and HKCR, analyzing only keys

The ignore words: CLSID and curver and office

Search results:

*** Found 74 high level keys in HKCR

*** Found nothing in HKLM

*** None of the HKCR keys could be removed (only "TrustedInstaller" has full control) (*)

*** Searching just HKLM and analyzing only keys also found nothing in HKLM

*** RegEdit shows both the HKCR and HKLM keys are in the registry; for example:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Search.CustomWordbreaker

HKEY_CLASSES_ROOT\Search.CustomWordbreaker

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

(*) An exception -- these two keys could be removed:

HKEY_CLASSES_ROOT\Search.TripoliIndexer

HKEY_CLASSES_ROOT\Search.TripoliIndexer.1

They have the same permissions, including "TrustedInstaller," as the other 72 keys … :?

jv16

This bug has now been fixed, thank you for reporting! The fixed version will be released later this week.

tullik

tullik wrote
Registry Finder - another search failure instance (v.1.8.0.455)

In the case below (on Vista), the tool found the desired high level keys in HKCR, but did not find the corresponding keys in HKLM. ...

The first issue in this topic is fixed by v.1.8.0.457.

The problem quoted is still there ...

jv16

tullik wrote

The problem quoted is still there ...

This problem is also now fixed, thank you for reporting! The fix will be present in the next released version of PowerTools.