jv16 PowerTools 2009 (1.9.1.606) available for testing

jv16

tullik wrote
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.

I have now analyzed the debug logs sent by Naiden and mauricev (thank you so much for those!) and an internal exception occurs in PowerTools that basically makes it stop working. The permission issue might be the root cause that causes the internal exception but the problem is the exception itself, it shouldn't ever happen, no matter what kind of key the user attempts to fix or delete.

I'm afraid, with this information I can't exactly pinpoint what causes the problem. I did one change in attempt to address the issue, and I added a lot more debug code that causes the Debug Log to contain more information.

So, I will be releasing a new beta version for testing later today. I'd really like to get this issue fixed as well. It's a rare problem and doesn't cause any harm to the computer, but still.

roberta

jv16 wrote

....

.......

So, I will be releasing a new beta version for testing later today. I'd really like to get this issue fixed as well. It's a rare problem and doesn't cause any harm to the computer, but still.

Jv16,

Please let us know what changes are included in the new Beta....

Best Regards,

Roberta

jv16

roberta wrote
jv16 wrote

....

.......

So, I will be releasing a new beta version for testing later today. I'd really like to get this issue fixed as well. It's a rare problem and doesn't cause any harm to the computer, but still.

Jv16,

Please let us know what changes are included in the new Beta....

Build 605 released. The changes are:

* There were some issues with saving data (Registry Cleaner's File > Save List As), this should now be fixed

* More debug code. So if anyone still experience the problem of the Registry Cleaner not being able to fix or remove something, please create a debug log and send it to me. I also attempted to fix the issue, so if you can no longer reproduce the issue let me know.

tullik

The jv16pt_setup_1.9.1.605.exe file contains v.1.9.0.602. :

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.

parkd1

When I ran power tools and try and fix or delete these they just stay is there any way to fix these?activex.rar

leonardo

parkd1 wrote
When I ran power tools and try and fix or delete these they just stay is there any way to fix these?activex.rar

jv16 Wrote:

Added more debug code. So if anyone still experience the problem of the Registry Cleaner not being able to fix or remove something, please create a debug log and send it to me. I also attempted to fix the issue, so if you can no longer reproduce the issue let me know.

Parkd1, please look higher up on this forum page!

naiden

Hi JV16,

thanks for the new Build.

1030 errors each time that could not be fixed.

tullik

PT2009 (605) beta Tested on x86 Vista BE pre-SP1 desktop

Questions and observations:

*** I usually use "Delete" instead of "Fix" in Registry Cleaner but used "Fix" now because of the current important issues. On my system, it appears to work as designed, but I noticed it fixes UserAssist entries in a novel way. Namely:

It "fixes" invalid path HRZR entries by deleting them, then if there is some valid path in the file cache, it adds it to the Count key with the path as the entry name and N/A as the data. I suspect windows eventually removes such bogus entries, so this does no harm.

*** Registry Finder does not do a complete search which forces one, for example, to use the tedious RegEdit search to find more of what one is looking for. This has nothing to do with the current important issues, and is not a new issue, so it can be addressed in the PT2010 betas.

Fixes or improvements confirmed:

* There were some issues with saving data (Registry Cleaner's File > Save List As), this should now be fixed

For example, 1.9.0.602 did not list all the items shown in the results, but 1.9.0.605 does.

roberta

jv16 wrote
roberta wrote
jv16 wrote

....

.......

So, I will be releasing a new beta version for testing later today. I'd really like to get this issue fixed as well. It's a rare problem and doesn't cause any harm to the computer, but still.

Jv16,

Please let us know what changes are included in the new Beta....

Build 605 released. The changes are:

* There were some issues with saving data (Registry Cleaner's File > Save List As), this should now be fixed

* More debug code. So if anyone still experience the problem of the Registry Cleaner not being able to fix or remove something, please create a debug log and send it to me. I also attempted to fix the issue, so if you can no longer reproduce the issue let me know.

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

Regards,

Roberta

tullik

PT2009 (605) beta Tested on x64 Vista HP SP2 desktop

Bugs:

Registry Cleaner:

"Save list as …" (always) and "Export as .reg file" (sometimes) don't work on this system. I suppose this could be due to a Vista bug as alleged by jv16.

There are several items which exhibit symptoms such as these:
RegEdit opens at the wrong place.

Registry Cleaner thinks files referenced by some uncomplicated path strings don't exist when they do.

Backup is not correct when the a file reference error exists in identical subkeys both above and below a Wow6432Node.

Such bugs could trigger "false positives" so I'll run RC in debug mode and attach logs and a custom backup folder. I won't go so far as to actually click the FIX button.

parkd1

parkd1 wrote
When I ran power tools and try and fix or delete these they just stay is there any way to fix these?activex.rar

Here is the debug info on the scan that could not fix or delete.jv16 PowerTools 2009 (1.9.1.605).rar

tullik

tullik wrote
PT2009 (605) beta Tested on x64 Vista HP SP2 desktop

. . .

Such bugs could trigger "false positives" so I'll run RC in debug mode and attach logs and a custom backup folder. I won't go so far as to actually click the FIX button.

For 1.9.0.605 debugging (1).zip

roberta

roberta wrote
jv16 wrote

Build 605 released. The changes are:

* There were some issues with saving data (Registry Cleaner's File > Save List As), this should now be fixed

* More debug code. So if anyone still experience the problem of the Registry Cleaner not being able to fix or remove something, please create a debug log and send it to me. I also attempted to fix the issue, so if you can no longer reproduce the issue let me know.

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

Regards,

Roberta

Greetings Jv16,

Error reports eMailed a few minutes ago...

Best Regards,

Roberta

siliconman01

tullik: PT2009 (605) beta Tested on x64 Vista HP SP2 desktop

Bugs:

Registry Cleaner:

"Save list as …" (always) and "Export as .reg file" (sometimes) don't work on this system. I suppose this could be due to a Vista bug as alleged by jv16.

"Export as .reg file" has never worked correctly on x64 systems. As I have reported in a couple of previous posts, if you manually open Regedit or use "Open in regedit" first, then Export as .reg file" works fine. The navigation window opens right up and a user can export properly. Also, once you get it to work in a PT session, then it will work every time thereafter in that session. Personally I do not think this is a Vista x64 bug, but is a bug in PT 2009 and PT 2010. This feature works properly in Vista x86.

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.

siliconman01

On my Vista SP2 x64 Business with 8 gybtes RAM, Aero interface, I ran 10 consecutive registry scans with B605.

First scan:

Export as .reg file -- nothing

Open in RegEdit -- OK

Export as .reg file -- OK

Save list as -- OK

Second thru tenth scan (not closing/restarting PT 2009 in between scans):

Save list as -- OK

Export as .reg file -- OK

I did not get any out-of-resources error messages.

doogie

For me build 605 is still showing false incorrect permission entries. As per the following list.

HKEY_LOCAL_MACHINE\software\Wow6432Node\1C\{97A8C4B4-2B50-42D1-AFE6-5E8433185436}\AppVersion : 1.01

HKEY_LOCAL_MACHINE\software\Wow6432Node\1C\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\software\Wow6432Node\1C\{97A8C4B4-2B50-42D1-AFE6-5E8433185436}\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\software\Wow6432Node\even balance\PnkBstrA\Port : 44301

HKEY_LOCAL_MACHINE\software\Wow6432Node\even balance\PnkBstrA\Version : 1032

HKEY_LOCAL_MACHINE\software\Wow6432Node\even balance\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\software\Wow6432Node\even balance\PnkBstrA\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\software\Wow6432Node\even balance\PnkBstrB\Instance : 1

HKEY_LOCAL_MACHINE\software\Wow6432Node\even balance\PnkBstrB\Port : 45301

HKEY_LOCAL_MACHINE\software\Wow6432Node\even balance\PnkBstrB\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\ConnectCache\78d8fa3c1 : N/A

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\cip : GB

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\CM : 72.165.61.185;72.165.61.186;72.165.61.187;72.165.61.188;69.28.156.250;68.142.64.164;68.142.64.165;69.28.145.170;69.28.145.171;69.28.145.172;208.111.158.52;208.111.158.53;208.111.171.82;208.111.171.83;68.142.91.34;68.142.91.35;68.142.91.36;208.111.133.84;208.111.133.85;68.142.116.178;68.142.116.179

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\CMVer : 1255447299

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\MTBF : 2128573172

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\NCTF : 0

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\SteamPID : 0

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\TempAppCmdLine : N/A

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\TempAppPath : N/A

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\software\Wow6432Node\valve\Steam\ConnectCache\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\software\Wow6432Node\videolan\VLC\@ : C:\Andy\Codecs\VLC\vlc.exe

HKEY_LOCAL_MACHINE\software\Wow6432Node\videolan\VLC\InstallDir : C:\Andy\Codecs\VLC

HKEY_LOCAL_MACHINE\software\Wow6432Node\videolan\VLC\Language : 1033

HKEY_LOCAL_MACHINE\software\Wow6432Node\videolan\VLC\Version : 1.0.2

HKEY_LOCAL_MACHINE\software\Wow6432Node\videolan\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\software\Wow6432Node\videolan\VLC\{KEY} : {KEY}

Deleting any of these causes the relevant app to malfunction.

Running Vista Home Premium x64.

jv16

DooGie wrote
For me build 605 is still showing false incorrect permission entries. As per the following list.

...

Running Vista Home Premium x64.

Fixed now, thank you for reporting! The issue was already fixed in the PT 2010 code but I forgot to include the fix to PT 2009 as well.

jv16

siliconman01 wrote
On my Vista SP2 x64 Business with 8 gybtes RAM, Aero interface, I ran 10 consecutive registry scans with B605.

First scan:

Export as .reg file -- nothing

Open in RegEdit -- OK

Export as .reg file -- OK

Save list as -- OK

Second thru tenth scan (not closing/restarting PT 2009 in between scans):

Save list as -- OK

Export as .reg file -- OK

I did not get any out-of-resources error messages.

These issues are relating to the problem with 64 bit Windows Vista. In this environment the Windows' API call for a file or directory browse dialog sometimes fails for no apparent reason. Microsoft has been informed about this and the issue has been fixed from Windows 7 but the issue is still in Vista SP2 (64 bit) so I don't know if they are going to fix it or not.

« Previous Page Next Page »