Ignore words problem in registry cleaner

nikolaos

Hello All,

Registry cleaner v.338 does not ignore the words inserted in the ignore words list. Is there anyone with the same problem ? v.335 works fine.

Nikolaos

jv16

What words have you entered to the Ignore Words list and what entries the Registry Cleaner finds that you feel it shouldn't find?

tullik

Have not had that problem.

Copy and paste into a reply your ignore words and an example of an item not ignored. It may just be spelling.

nikolaos

Hello jv16

I inserted AutoRoute and AutoRout but Registry cleaner finds 2 registry keys with AutoRoute, If I delete them Microsoft Autoroute gives me an error.

Nikolaos

nikolaos

Hello tullik,

Spelling is OK I checked it many times. Registry cleaner reports that Autorout.exe does not exist, but it is there I checked it. Anyway I am not at home now and I do not remember the report. I can posted it later.

Nikolaos

nikolaos

This is my ignore words(copy and paste):

AutoRoute

AutoRout

and this is what registry cleaner finds after a normal scan:

High, HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{75048700-EF1F-11D0-9888-006097DEACF9}\Count\, HRZR_EHACNGU:\Cebtenzzv\Zvpebfbsg NhgbEbhgr\NhgbEbhg.rkr, N/A, File or directory "C:\Programmi\Microsoft AutoRoute\AutoRout.exe" does not exist, 08.05.2006, 20.20

High, HKUS\S-1-5-21-2322712386-3341562259-4179051517-1005\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{75048700-EF1F-11D0-9888-006097DEACF9}\Count\, HRZR_EHACNGU:\Cebtenzzv\Zvpebfbsg NhgbEbhgr\NhgbEbhg.rkr, N/A, File or directory "C:\Programmi\Microsoft AutoRoute\AutoRout.exe" does not exist, 08.05.2006, 20.20

Nikolaos

tullik

Since the file exists, there is probably a minor bug.

Try using this ignore word until it is fixed: \Explorer\UserAssist\

nikolaos

OK tullik your suggestion works. Thank you. This is probably a minor bug introduced after v.335. With v.335 I have not this problem. How the error description is generated ?

Nikolaos

jv16

This minor bug is now fixed, thank you for reporting. The next released version will contain the fix in question.