Test version 1.9.0.581 released (and now: 590)

mrcs

584

Big improvement in Registry Cleaner over the last version, thanks.

One cosmetic item: Under Settings > Advanced > Default date format, the MM.DD and DD.MM seem to be reversed when selected.

Also, I don't know if this is expected behavior but it finds the recent MS updates for C++ and Silverlight as "does not exist" (the drive letter is lower case "L"). The directories don't exist, of course, but I don't know if Silverlight is expecting these keys to be present and are not safe to delete.

HKEY_LOCAL_MACHINE\Software\classes\installer\patches\7c7a69d5bdc7d4349baa7eb72e1fb1bf\sourcelist\net\1 :

l:\7c82e13aec8f9877821f4f3be8\

XP Pro SP3

------

One other item. In our forum exchange of some time ago ( http://www.macecraft.com/phpBB3/viewtopic.php?f=21&t=3734&st=0&sk=t&sd=a&start=60#p19267 ) you said, "But maybe I'll just might add some option to edit the ignoring policy, thanks! I think I figured out a way to do this." I know you have a lot on your plate, but do you have any version or time when you anticipate this feature might be added?

jv16

MRCS wrote

One other item. In our forum exchange of some time ago ( http://www.macecraft.com/phpBB3/viewtopic.php?f=21&t=3734&st=0&sk=t&sd=a&start=60#p19267 ) you said, "But maybe I'll just might add some option to edit the ignoring policy, thanks! I think I figured out a way to do this." I know you have a lot on your plate, but do you have any version or time when you anticipate this feature might be added?

This feature will be added to PowerTools 2010.

tullik

On Vista BE

Note the following analysis was done without debug mode. I will repeat it in debug mode and post the debug file here (or in the bug tracker if it is too big).

Registry Cleaner

Current registry value: C:\PROGRA~1\MI1933~1\OFFICE11\GRAPH.EXE is green. However, ...\MI1933~1\... does not exist. GRAPH.EXE does exist, but in c:\Program Files\Microsoft Office\OFFICE11\. This issue appears in at least two categories. The .reg file for one instance is in the .zip attachment as 01.reg. Other sub-programs used by MS Office, not just GRAPH.EXE, are referenced by other categories. In one case, the "Current registry value" correctly displays in red. All these instances, which are left by an MS Office install, are in the .zip attachment as 02.reg.

After deleting all the items reflected by 02.reg, launching MS Word triggered an error saying I should do a "repair" reinstall, but the MS Word window came up OK anyway. Restoring the backup got rid of the error message.

I then rebuilt the file cache and confirmed graph.exe was in it. It was, as <graph.exe>@<c:\program files\microsoft office\office11\>. I then ran Registry Cleaner and did "Fix" for the same errors. It fixed nothing, removed everything, and the same "do a repair" message occurred.

Conclusion: MS Office is checking, but probably not actually using, the installer keys.

Recommendation: PT2009 should ignore these MS Office installer keys.

Note: the above analyisis had all scans enabled. The same errors show with just the "File reference scan." The debug log will have just the "File reference scan," but also include the "Fix" action, and the restore.

Note: in debug mode, the program got an "AppHangB1" while attempting to populate the Backup Tool list. I had to let windows close PT2009.

Note: the zipped debug log was too big, so I'll put the files in the bug tracker.

thedude20165

TheDude20165 wrote
jv16 wrote
TheDude20165 wroteVista Ultimate x64. "Performing Final Analysis..." never ends. Using 584.

That is good news! Could you please create a Debug Log of the issue and send it here?

I'm getting the same result with 585.

Anything new on this one? I sent the debug report using 584. The problem still exists with 585.

tullik

On Vista BE

Registry Cleaner

I restored all the errors found by 584. They had been removed without apparent impact.

These errors (probably just minor) occur with 585:

There is some incorrect truncation of file or directory paths and of displayed registry values.

There is some incorrect parsing of "program, parameter" strings.

There were similar errors in 584, but 585 fixed many.

Current registry value: C:\WINDOWS\SYSTEM32\CONFIG\COMPON~2.TMP.LOG2 is red but it does exist

Current file reference: C:\WINDOWS\SYSTEM32\CONFIG\COMPON~2.TMP.LOG is red and does not exist

The "2" is incorrectly truncated.

Current registry value: C:\WINDOWS\SYSTEM32\CONFIG\COMPON~2.TMP.LOG1 is red but it does exist

Current file reference: C:\WINDOWS\SYSTEM32\CONFIG\COMPON~2.TMP.LOG is red and does not exist

The "1" is incorrectly truncated.

Current registry value: C:\Python22\pythonw.exe "C:\Python22\lib\site-packages\win32com\server\localserver.py" {30BD3490-263

Current file reference: C:\Python22\pythonw.exe "C:\Python22\lib\site-packages\win32com\server\localserver.py" {30BD3490-2632-11cf-AD5B-524153480001

Both strings are incorrectly truncated. The second string is incorrectly parsed.

Current registry value: C:\Python22\pythonw.exe "C:\Python22\lib\site-packages\win32com\server\localserver.py" {39b61048-c75

Current file reference: C:\Python22\Scripts

The first string is incorrectly truncated.

Current registry value: C:\Python22\pythonw.exe "C:\Python22\lib\site-packages\win32com\server\localserver.py" {DF630910-1C1

Current file reference: C:\Python22\pythonw.exe "C:\Python22\lib\site-packages\win32com\server\localserver.py" {DF630910-1C1D-11d0-AE36-8C0F5E000000

Both strings are incorrectly truncated. The second string is incorrectly parsed.

Current registry value: C:\Program Files\muvee Technologies\muvee autoProducer 3.5 magicMoments - HPD

Current file reference: C:\Program Files\muvee Technologies\muvee autoProducer 3.5

The second string is incorrectly truncated.

Current registry value: n;1;C:\Users\Owner\AppData\Local\Temp\miaCFC3.tmp\data\Microsoft Visual C++ Runtime 9.0 (includes AT

Current file reference: C:\Users\Owner\AppData\Local\Temp\miaCFC3.tmp\data\Microsoft Visual C++ Runtime 9.0 (includes ATL and MFC) Service Pack 1\mFileBagIDE.dll

The first string is incorrectly truncated.

Current registry value: C:\Users\Owner\AppData\Local\Temp\miaCFC3.tmp\data\Microsoft Visual C++ Runtime 9.0 (includes ATL an

Current file reference: C:\Users\Owner\AppData\Local\Temp\miaCFC3.tmp\data\Microsoft Visual C++ Runtime 9.0 (includes ATL and MFC) Service Pack 1\mFileBagIDE.dll

The first string is incorrectly truncated.

Current registry value: C:\Users\Owner\AppData\Local\Temp\7ZipSfx.000\

Current file reference: C:\Users\Owner\AppData\Local\Temp\7ZipSfx.000

The "\" should not be dropped from the second string.

Added note: if you need a debug log or .reg files for these error types, let me know. 8)

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

TheDude20165 wrote
TheDude20165 wrote
jv16 wrote

That is good news! Could you please create a Debug Log of the issue and send it here?

I'm getting the same result with 585.

Anything new on this one? I sent the debug report using 584. The problem still exists with 585.

Where did you send the debug log? I do not recall receiving them.

tullik

jv16 wrote
TheDude20165 wrote ... I'm getting the same result with 585.

...

Anything new on this one? I sent the debug report using 584. The problem still exists with 585.

Where did you send the debug log? I do not recall receiving them.

He posted it in this thread, here: http://www.macecraft.com/phpBB3/viewtopic.php?p=20776#p20776

jv16

tullik wrote
jv16 wrote

Where did you send the debug log? I do not recall receiving them.

He posted it in this thread, here: http://www.macecraft.com/phpBB3/viewtopic.php?p=20776#p20776

Got it now, thanks!

jv16

TheDude20165 wrote
TheDude20165 wrote

I'm getting the same result with 585.

Anything new on this one? I sent the debug report using 584. The problem still exists with 585.

I have now located the problem, the issue should be fixed for the next released test version. I cannot say anything for sure because I have not been able to reproduce the issue.

siliconman01

siliconman01 wrote
On Vista SP2 x64, following a scan in the Registry Cleaner at top menu under File, the "Save list as" does nothing.

My apologies if this has been reported as a bug in bug tracker and is waiting to be fixed.

I submitted a BugTracker report on this because it does not work on the V1.9.0.580 either for x64 systems. Works fine on XP-SP3 x86 and Windows 7 RC 7100 x86.

thedude20165

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

tullik wrote
On Vista BE

Registry Cleaner

I restored all the errors found by 584. They had been removed without apparent impact.

These errors (probably just minor) occur with 585:

No need to report these "current file reference" inaccuracies. This is because it's impossible to extract the filename from a random string with 100% efficency, but this is simply a GUI issue. The engine goes through all the possible variations, and thus will also check for the correct filename as well.

jv16

Test version 587 released (for the download link, please see the first post of the thread), this version should fix the problems of the Registry Cleaner in the previous versions.

But in the case it doesn't, if you experience any of these problems:

a) the Registry Cleaner hangs or crashes on your computer every time you try it.

b) the Registry Cleaner misses items you know that should be included, every time you run it.

c) the Registry Cleaner includes items that you know should not be included, every time you run it.

Please start the program in debug mode and run the Registry Cleaner. It can take a long time to finish, and the resulting debug log will be more than 4 MB in size. After done, please ZIP the file and send it here for further analysis.

The new 587 also includes some nice improvements to the Registry Cleaner's result list, such as tooltips for columns and data, and a fix to the lack of horizontal scroll bar issue.

siliconman01

I sent you a Registry Cleaner Debug log from B587. Your fixes in B587 have stopped the false detections I reported in B585. Thanks very much. Below is from the new BugTracker submittal.

Here is a list of 438 Registry Cleaner detections by Build 587 on Vista SP2 x64. These detections occur on the most aggressive scan and I believe are related to Volume Shadow Copy. I think these are unsafe to delete and will damage MS Volume Shadow Copy which is used by my Casper V5.0 backup software as well as PerfectDisk 10 Pro.

Please note that these are NOT new detections by Build 587. They have been detected by all builds including B580. I have had them in my Ignore List and forgot about them.

jv16

siliconman01 wrote
I sent you a Registry Cleaner Debug log from B587. Your fixes in B587 have stopped the false detections I reported in B585. Thanks very much. Below is from the new BugTracker submittal.

That is some great news!

tullik

On Vista BE

Registry Cleaner

Apparently 587 now ignores certain MS Office install keys. Those keys reference two invalid folders (C:\PROGRA~1\MI1933~1\OFFICE11\ and C:\WINDOWS\Installer\{91110409-6000-11D3-8CFE-0150048383C9}\), but MS Office requires the presence of the keys anyway. Who knows why? Issue avoided. :)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Current registry entry: C:\Users\Owner\AppData\LocalLow\Sun\Java\jre1.6.0_12\ (does not exist)

Current file reference: C:\Users\Owner\AppData\LocalLow\Sun\Java\jre1.6 (an incorrect truncation of Current registry entry)

In 585, the program "fixed" the data incorrectly by changing C:\Users\Owner\AppData\LocalLow\Sun\Java\jre1.6.0_12\ to C:\Program Files\Java\jre6\.

In 587, "Fix" causes removal of the entry (InstallSource), not just the data. Issue fixed. :)

tullik

jv16 wrote
... No need to report these "current file reference" inaccuracies. This is because it's impossible to extract the filename from a random string with 100% efficency, but this is simply a GUI issue (?). The engine goes through all the possible variations, and thus will also check for the correct filename as well. ((?) added to quote ...)

Be that as it may, the program really ought to handle "program parameter" strings, especially, with better precision.

Here's a case on Windows 7 that is rather important:

Error relating to %SystemRoot%\System32\rundll32.exe shell32.dll,SHCreateLocalServerRunDll {722b3793-5367-4446-b6bb-db89b05c1f24}

Since %SystemRoot%\System32\rundll32.exe obviously exists, the key should not trigger an error at all!

Here's the debug log and Entries.reg for the category.

rundll32.zip

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Additional information: per Registry Finder, these similar strings exist, but only the red one triggers an error in Registry Cleaner. Why?

File=rundll32 parameters (on dt7).txt

jv16 PowerTools 2009

Data fields are: Key, Entry's name, Value, Entry last modified

HKEY_CLASSES_ROOT\clsid\{ffb8655f-81b9-4fce-b89c-9a6ba76d13e7}\LocalServer32\, @, %SystemRoot%\System32\rundll32.exe shell32.dll,SHCreateLocalServerRunDll {FFB8655F-81B9-4fce-B89C-9A6BA76D13E7}, 22.04.2009, 03

HKEY_CLASSES_ROOT\clsid\{fb479c02-9ec4-4fed-8599-debe037452cb}\LocalServer32\, @, %SystemRoot%\System32\rundll32.exe shell32.dll,SHCreateLocalServerRunDll {fb479c02-9ec4-4fed-8599-debe037452cb}, 22.04.2009, 03

HKEY_CLASSES_ROOT\clsid\{9a97f12a-6b73-4dc4-b3c1-e9244c03adac}\localserver32\, @, %SystemRoot%\System32\rundll32.exe shell32.dll,SHCreateLocalServerRunDll {9a97f12a-6b73-4dc4-b3c1-e9244c03adac}, 22.04.2009, 03

HKEY_CLASSES_ROOT\clsid\{995c996e-d918-4a8c-a302-45719a6f4ea7}\LocalServer32\, @, %SystemRoot%\System32\rundll32.exe shell32.dll,SHCreateLocalServerRunDll {995C996E-D918-4a8c-A302-45719A6F4EA7}, 22.04.2009, 03

HKEY_CLASSES_ROOT\clsid\{722b3793-5367-4446-b6bb-db89b05c1f24}\LocalServer32\, @, %SystemRoot%\System32\rundll32.exe shell32.dll,SHCreateLocalServerRunDll {722b3793-5367-4446-b6bb-db89b05c1f24}, 22.04.2009, 03

HKEY_CLASSES_ROOT\clsid\{3eef301f-b596-4c0b-bd92-013beafce793}\LocalServer32\, @, %SystemRoot%\System32\rundll32.exe shell32.dll,SHCreateLocalServerRunDll {3eef301f-b596-4c0b-bd92-013beafce793}, 22.04.2009, 03

thedude20165

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.

« Previous Page Next Page »