jv16 PowerTools 2009 (1.9.1.606) available for testing

roberta

roberta wrote
jv16 wroteBuild 599 released, the download link is in the first message of this thread.

This build should address all the remaining issues.

Will report on Build 599 within about 12 hours....

Regards,

Roberta

Hi Jouni,

Have eMailed test results....

Best Regards,

Roberta

tullik

V 1.9.0.599 on x64 Vista HP (SP2)

Registry Cleaner: "Open in RegEdit" does not open at the correct key.

With the safest settings and MRU checked, the results list shows:

this key as an "Obsolete software entry":
HKEY_LOCAL_MACHINE\Software\Gateway\KB0817 Keyboard Driver\1.30.0000\

That is likely true since all of the keys from "Gateway" to "1.30.0000" are empty.

However, that key does not exist in the registry.

The empty key HKEY_LOCAL_MACHINE\Software\WOW6432Node\Gateway\KB0817 Keyboard Driver\1.30.0000\ does exist.

"Open in RegEdit" for the HKEY_LOCAL_MACHINE\Software\Gateway\KB0817 Keyboard Driver\1.30.0000\ shown in the results opens as follows:

the focus is on "Computer"

the window is at an expanded HKEY_LOCAL_MACHINE\SOFTWARE\Gateway\Metadata.

That key exists and has several entries under "Metadata."

Removing what is shown in the list backs up and removes HKEY_LOCAL_MACHINE\Software\WOW6432Node\Gateway\KB0817 Keyboard Driver\1.30.0000\.

This .reg file should allow the situation to be reproduced on an x64 Vista machine which does not have any …\Gateway\... keys in its registry:

Windows Registry Editor Version 5.00






Br="GTW"
Sys="DTP"
Loc="ENG_US"
Ch="Retail"
EarthLink=dword

eBayShortcut=dword

tullik

V 1.9.0.599 on x64 Vista HP (SP2)

Registry Cleaner: shows a possible "false positive" for a …\ATI\ACE\Packages key and entries.

With the safest settings and MRU checked, the results list shows:

items like this as "Useless registry entry" in the MRU category:
Key=HKEY_LOCAL_MACHINE\Software\ATI\ACE\Packages

Entry=ccc-localization-fi Data=C:\Program Files (x86)\ATI Technologies\ATI.ACE

Entry=ccc-localization-es Data=C:\Program Files (x86)\ATI Technologies\ATI.ACE

However, that key does not exist in the registry.

The key HKEY_LOCAL_MACHINE\Software\WOW6432Node\ATI\ACE\Packages does exist.

The folder C:\Program Files (x86)\ATI Technologies\ATI.ACE also exists.

"Open in RegEdit" for the HKEY_LOCAL_MACHINE\Software\ATI\ACE\Packages shown in the results opens as follows:

the focus is on "Computer"

the window is at an expanded HKEY_LOCAL_MACHINE\SOFTWARE\ATI\ACE\Settings.

That key exists and is empty from ATI through Settings.

Removing what is shown in the list backs up and removes (for example):

Key=HKEY_LOCAL_MACHINE\Software\Wow6432Node\ATI\ACE\Packages

Entry=ccc-localization-fi Data=C:\Program Files (x86)\ATI Technologies\ATI.ACE

Entry=ccc-localization-es Data=C:\Program Files (x86)\ATI Technologies\ATI.ACE

This .reg file should allow the situation to be reproduced on an x64 Vista machine which does not have any …\ATI\ACE\... keys in its registry:

Windows Registry Editor Version 5.00






ccc-localization-sv="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"
ccc-localization-no="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"
ccc-localization-nl="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"
ccc-localization-it="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"
ccc-localization-fr="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"
ccc-localization-fi="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"
ccc-localization-es="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"
ccc-localization-de="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"

ccc-localization-da="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"

You may also have to create this empty directory structure: C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static.

This attachment has a .reg file of the complete HKEY_LOCAL_MACHINE\Software\WOW6432Node\ATI\ACE\ structure, which has many keys and entries including those of the Packages key.

ATI regs.zip

These attachments are debug logs when Registry Cleaner was run with ATI\ACE in "Search words."

1.zip2.zip

jv16

tullik wrote
V 1.9.0.599 on x64 Vista HP (SP2)

Registry Cleaner: shows a possible "false positive" for a …\ATI\ACE\Packages key and entries.

Does these x64 issue also exist in 1.9.0.590? If they do, I'm thinking about not fixing them now and instead release the new build in order to solve the main issue of false positives.

jv16

Naiden wrote
Hi,

thanks for the new Build. The Safetynet error has gone now.

Is is normal that not all ActiveX/COM ... errors can be fix?

i i select agressivmode and click on fix errors, 1060 errors remain each time.

Would it be possible for you to send me a debug log of such event? With the log file I could see what's happening and possibly fix the issue.

tullik

jv16 wrote
tullik wrote V 1.9.0.599 on x64 Vista HP (SP2)

Registry Cleaner: shows a possible "false positive" for a …\ATI\ACE\Packages key and entries.

Does these x64 issue also exist in 1.9.0.590? If they do, I'm thinking about not fixing them now and instead release the new build in order to solve the main issue of false positives.

Yes.

Windows Registry Editor Version 5.00

; File created by TBackupTool ...
; Program version: 1.9.0.590
; Date: 12.10.2009 ... Time: 09
;
; ******* Made with "Export as .reg file"


"ccc-localization-fi"="C:\\Program Files (x86)\\ATI Technologies\\ATI.ACE"

And "Open in RegEdit" works with x64 in 599. It doesn't work in 590 which made these errors (bugs) with x64 hard to spot with that version.

There are 3 to 5 additional similar cases on my machine with safest settings, so an x64 compatibility statement in the release notes is warranted, IMO.

naiden

jv16 wrote
Naiden wroteHi,

thanks for the new Build. The Safetynet error has gone now.

Is is normal that not all ActiveX/COM ... errors can be fix?

i i select agressivmode and click on fix errors, 1060 errors remain each time.

Would it be possible for you to send me a debug log of such event? With the log file I could see what's happening and possibly fix the issue.

jv16

Naiden wrote
jv16 wrote
Naiden wroteHi,

thanks for the new Build. The Safetynet error has gone now.

Is is normal that not all ActiveX/COM ... errors can be fix?

i i select agressivmode and click on fix errors, 1060 errors remain each time.

Would it be possible for you to send me a debug log of such event? With the log file I could see what's happening and possibly fix the issue.

Thanks but the file you included is not a debug log.

To create a debug log, please follow these simple steps: http://www.macecraft.com/phpBB3/viewtopic.php?f=10&t=3958&p=21682#p21682

roberta

Hi Jouni,

Will report on Build 601 within about 24 hours....

Regards,

Roberta

naiden

To create a debug log, please follow these simple steps: http://www.macecraft.com/phpBB3/viewtopic.php?f=10&t=3958&p=21682#p21682

roberta

roberta wrote
Hi Jouni,

Will report on Build 601 within about 24 hours....

Regards,

Roberta

Hi Jv16,

Have now sent You an email documenting the unexpected outcome for Build 601.....

Best Regards,

Roberta

roberta

Greetings Jv16,

Will report on Build 602 within about 24 hours....

Regards,

Roberta

roberta

roberta wrote
Greetings Jv16,

Will report on Build 602 within about 24 hours....

Regards,

Roberta

Sent eMail with report & attachments about 30 minutes ago (its Not looking any better => Very disappointing indeed)....

jv16

Version 1.9.1.602 released for testing (see the first message of the thread for the download link).

Could you please let me know if the Registry Cleaner shows a different number of registry errors when run many times in a row?

Roberta reported this issue, as well as some crashing. I would like to hear if these issues are happening with other users as well.

naiden

same as Build 599. 1018 Erros found with could not been corrected

leonardo

jv16 wrote
Version 1.9.1.602 released for testing (see the first message of the thread for the download link).

Could you please let me know if the Registry Cleaner shows a different number of registry errors when run many times in a row?

Roberta reported this issue, as well as some crashing. I would like to hear if these issues are happening with other users as well.

On one of my smaller XP-Prof.-SP3 systems I restored my registry to an old starting point and rebooted.

Than I ran v1.9.0.599 for 10 times (one notch aggressive, all scan options selected except ActiveX/COM/DCOM/OLE/DDE)

8 times: 531 errors, 89 key´s, 442 entries

2 times: 513 errors, 71 key´s, 442 entries (run 3 and 5, is it possible that a running process influence the Registry Scan results?)

Than I ran v1.9.1.602 for 15 times (one notch aggressive, all scan options selected except ActiveX/COM/DCOM/OLE/DDE)

14 times: 531 errors, 89 key´s, 442 entries!

1 time : 507 errors, 89 key´s, 418 entries! (run 8th, is it possible that a running process influence the Registry Scan results?)

Than I rebooted and ran v1.9.1.602 again for 15 times (one notch aggressive, all scan options selected except ActiveX/COM/DCOM/OLE/DDE)

15 times: 531 errors, 89 key´s, 442 entries!

On a larger XP-Prof.-SP3 systems I restored my registry to an old starting point and rebooted.

Than I ran v1.9.1.602 for 15 times (one notch aggressive, all scan options selected except ActiveX/COM/DCOM/OLE/DDE)

15 times: 956 errors, 165 key´s, 791 entries

Installing v602 required an additional reboot in order to show the scan progress window

tullik

PT2009 (602) beta Tested on x64 Vista HP SP2 desktop with 4 AMD cores and 4 GB memory

This new system has all the Registry Cleaner results lines either backed up and removed, or hidden with the "Never show" list.

I'll reverse those things, then see what repeated scans with v.1.9.0.602 show.

tullik

tullik wrote
PT2009 (602) beta Tested on x64 Vista HP SP2 desktop with 4 AMD cores and 4 GB memory

This new system has all the Registry Cleaner results lines either backed up and removed, or hidden with the "Never show" list.

I'll reverse those things, then see what repeated scans with v.1.9.0.602 show.

With the safest settings:

4 scans showed 139 lines, 4 categories. Scan sequence: 5, 6, 8, 20.

1 scan showed 139 lines, 3 categories. Scan sequence: 7

With the normal settings:

5 scans showed 243 lines, 6 categories. Scan sequence: 9, 10, 11, 12, 19.

With the more aggressive settings:

5 scans showed 243 lines, 5 categories. Scan sequence: 13, 14, 15, 16, 18.

With the most aggressive settings:

5 scans showed 853 lines, 9 categories. Scan sequence: 1, 2, 3, 4, 17.

All scans:

were done in the same PT session without closing the tool or results windows.

had "List MRU ..." checked.

had "Use deep analysis" checked.

had LastKey and RunMRU in the "Ignore words" tab.

showed the progress indicator and experienced no crashes or hangs.

showed scan speeds from 143 seconds (safest) to 155 seconds (most aggressive).

With the "Never show" list reactivated, a 1.9.0.602 most aggressive scan showed 702 lines, 6 categories.

I deleted all those, and then deleted the few hundred additional lines shown with a "Test Version 11" most aggressive scan.

A "Test Version 11" most aggressive scan now again shows zero lines, so hopefully, the x64 computer's registry is back where it started without restoring either the Restore Point or the ERUNT backup made before doing all this.

mauricev

I found a problem similar to but not 100% identical to the one I reported in http://www.macecraft.com/phpBB3/viewtopic.php?f=21&t=3922&p=21318#p21318 where the Fix button was being ignored. Here the fix button did seem to start, but then quickly gave up. I reproduced it in build 602 and I'm attaching the debug logs.

tullik

Naiden wrote
…

Is is normal that not all ActiveX/COM ... errors can be fix?

i i select agressivmode and click on fix errors, 1060 errors remain each time.

Naiden wrote
same as Build 599. 1018 Erros found with could not been corrected

It seems the registry of some windows systems gets primed or updated by Microsoft (and maybe by others) with many keys that have permissions for which the Administrators group does not have "Full control."

Many of these keys are "owned" by the userid "TrustedInstaller" and it is the only one with "Full control." This apparently restricts PowerTools' ability to remove such keys since PowerTools likely runs with the permissions of the Administrators group.

You could use RegEdit to check the permissions and ownership of a few of the ActiveX/COM … keys that won't go away. If that is the problem, here is a manual procedure that can enable removal of such keys by PowerTools:

http://www.macecraft.com/phpBB3/viewtopic.php?p=20992#p20992

It works but would be tedious if there are 100s of these key structures. So you may prefer to hide the items with "Ignore words" or the "Never show …" feature.

Perhaps jv16 will come up with some other way …

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

This happens for sure with Vista, but maybe your Windows 7 x64 situation is caused by something completely different … ?

« Previous Page Next Page »