Test version 1.9.0.581 released (and now: 590)

siliconman01

Yes, it does exist. I've checked numerous of these new detections and all the files exist.

parkd1

I have it set to emphasize the number of found errors and speed of the Registry Cleaner engiveine over safety and accuracy. Have List MRU and other history data checked and Aggressive checked. This is what it did not fix and left.not fixed.rar

siliconman01

Vista SP2 x64 Business, MS Office 2007, PT B584

The new B584 falsely detects valid keys as shown below concerning MS Office 2007 (not detected in any previous version of PT 2009). It says that Osetupui.dll does not exist and it does exist. I think what is causing the problem is that the DLL is found in folder C:\Program Files (x86)\Common Files\Microsoft Shared\Office12\Office Setup Controller\Office.en-us. The registry says that it exists in @C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\Office Setup Controller\Office.\osetupui.dll,-200. The registry key is attached.

tullik

On Vista BE

Registry Cleaner

When determining the actual path in a value, the program may not be considering the full alphabet possibilities in the Latin 1 (Western European - ISO 8859/1) character set.

Therefore it may incorrectly parse some paths from some of these countries:

(i.e., languages) Albanian, Danish, Dutch, English, Faroese, Finnish, French, German, Icelandic, Irish, Italian, Norwegian, Portuguese, Spanish, Swedish and Welsh

An actual browse directory example:

Current registry value: C:\+A\!P\Camera\Norway\2006\Kopperud\70 år fest

Current file reference: C:\+A\!P\Camera\Norway\2006\Kopperud\70

But perhaps it is just a specific case of the GUI issue you mentioned:

jv16 wrote
... This is simply a GUI issue. I noticed it myself but I wanted to release the new test version anyway. ...

jv16

parkd1 wrote
I have it set to emphasize the number of found errors and speed of the Registry Cleaner engiveine over safety and accuracy. Have List MRU and other history data checked and Aggressive checked. This is what it did not fix and left.not fixed.rar

Do you mean you actually fixed all the errors the program listed? Please be careful, this are beta level releases and it might not be safe to use the fix or delete features of the Registry Cleaner.

siliconman01

On Vista SP2 x64, it looks like the Wow6432Node's are not being scanned. No errors are being reported in these. For example, leftover from IE7 to IE8 conversion, the file ieuser.exe was detected as missing in HKLM and HKCR but not in HKCR\Wow6432Node. I haven't seen anything showing up as errors in the Wow6432Nodes in these new test versions.

Detected correctly:

@=hex(2),00,25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,\

00,65,00,73,00,25,00,5c,00,49,00,6e,00,74,00,65,00,72,00,6e,00,65,00,74,00,\

20,00,45,00,78,00,70,00,6c,00,6f,00,72,00,65,00,72,00,5c,00,49,00,45,00,55,\

00,73,00,65,00,72,00,2e,00,65,00,78,00,65,00,22,00,00,00,00,00

"ServerExecutable"=hex(2),00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,\

00,69,00,6c,00,65,00,73,00,25,00,5c,00,49,00,6e,00,74,00,65,00,72,00,6e,00,\

65,00,74,00,20,00,45,00,78,00,70,00,6c,00,6f,00,72,00,65,00,72,00,5c,00,49,\

00,45,00,55,00,73,00,65,00,72,00,2e,00,65,00,78,00,65,00,00,00,00,00

and