Test version 1.9.0.581 released (and now: 590)

tullik

On Vista BE

Registry Cleaner

Regarding:

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

Since the {722b3793-5367-4446-b6bb-db89b05c1f24} CLSID is not present on my Vista BE system, I put the key from the Windows 7 system into the Vista registry.

Registry Cleaner on Vista BE then shows the same error as it does on Windows 7.

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

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 dt1).txt

jv16 PowerTools 2009

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

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

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

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

HKCR\clsid\{722b3793-5367-4446-b6bb-db89b05c1f24}\LocalServer32\, @, %SystemRoot%\System32\rundll32.exe shell32.dll,SHCreateLocalServerRunDll {722b3793-5367-4446-b6bb-db89b05c1f24}, 04.08.2009, 16

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

tullik

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

How does one see those tooltips? I deleted Tips.dat, but nothing new showed.

I didn't notice any difference in the scroll bar behavior between 585 and 587. The scroll bar in both makes it easy to see more of the error description column with a single click. However, it seems that column cannot be drag-resized to make it wider or less wide.

jv16

tullik wrote

How does one see those tooltips? I deleted Tips.dat, but nothing new showed.

Simply keep your mouse cursor over a column or a line for a second or few (the time debends on the settings in your Windows).

tullik wrote

I didn't notice any difference in the scroll bar behavior between 585 and 587. The scroll bar in both makes it easy to see more of the error description column with a single click. However, it seems that column cannot be drag-resized to make it wider or less wide.

In the 587 the last column of the Registry Cleaner is automatically wider, this makes it easier to use the horizontal scroll bar.

tullik

Thank you.

tullik

Just noticed this ...

When I click the Registry Compactor icon using my Vista BE desktop PC, this message appears:

: This feature is not available with Windows 7.

That does not happen with 585 ...

jv16

tullik wrote

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!

You are correct. Could you please send a Debug Log where you run the Registry Cleaner of build 587 with most aggressive settings and only the "File reference scan" module. This would help me to see what's going on under the hood to determine why this false positive gets through. Thanks!

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

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.

tullik

jv16 wrote
tullik wrote

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!

You are correct. Could you please send a Debug Log where you run the Registry Cleaner of build 587 with most aggressive settings and only the "File reference scan" module. This would help me to see what's going on under the hood to determine why this false positive gets through. Thanks!

A little snag. The error did not show with just the "File reference scan." However, when the "ActiveX/et cetera" scan is also selected, it did show.

The debug log is too big to attach here, so I'll put it in the bug tracker.

Note: in a prior version here (584? 585?) the error did show with just the "File reference scan."

Edit: maybe not -- I think perhaps all the errors except this one showed with just the "File reference scan."

jv16

tullik wrote

The debug log is too big to attach here, so I'll put it in the bug tracker.

Looking forward to receive that.

Edit: Got it, thanks!

jv16

jv16 wrote
tullik wrote

The debug log is too big to attach here, so I'll put it in the bug tracker.

Looking forward to receive that.

Edit: Got it, thanks!

A new test version, build 588 released that should address the issue you reported. I say "should" because I have not been able to reproduce the issue in any of our test enviroments, but based on the debug log you sent I have a good idea what is going on.

siliconman01

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.

tullik

This false positive does not appear in the 588 Registry Cleaner results list:

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

jv16

Can anyone confirm any remaining issues in the latest test version (build 588)?

siliconman01

siliconman01 wrote
siliconman01 wroteOn 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.

This is the only issue that I see .... and only on x64.

tullik

jv16 wrote
Can anyone confirm any remaining issues in the latest test version (build 588)?

I did a "quick and dirty" test of this issue: http://www.macecraft.com/bugtracker/bug/111243/

The fix is not working.

That is, the first PT task started still ends abruptly when the second PT task ends.

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

When two tasks are automated to run at startup, they interfere with each other and seldom complete their jobs.

Sometimes, an APPCRASH shows up in WER. This example is, I believe, v.1.0.9.580:

Product

jv16 PowerTools

Problem

Stopped working

Date

6/24/2009 6 AM

Status

Not Reported

Problem signature

Problem Event Name: APPCRASH

Application Name: jv16PT.exe

Application Version: 1.9.0.580

Application Timestamp: 2a425e19

Fault Module Name: StackHash_1703

Fault Module Version: 0.0.0.0

Fault Module Timestamp: 00000000

Exception Code: c0000005

Exception Offset: 00000000

OS Version: 6.0.6000.2.0.0.256.6

Locale ID: 1033

Additional Information 1: 1703

Additional Information 2: 2264db07e74365624c50317d7b856ae9

Additional Information 3: 1344

Additional Information 4: 875fa2ef9d2bdca96466e8af55d1ae6e

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

On the plus side, these bugs appear to be gone in 588:

http://www.macecraft.com/bugtracker/bug/312224/

http://www.macecraft.com/bugtracker/bug/536869/ (reported for PTLite)

http://www.macecraft.com/bugtracker/bug/132497/

http://www.macecraft.com/bugtracker/bug/789234/

http://www.macecraft.com/bugtracker/bug/873532/

http://www.macecraft.com/bugtracker/bug/633762/ (reported for PTLite)

http://www.macecraft.com/bugtracker/bug/765963/

leonardo

tullik wrote
jv16 wroteCan anyone confirm any remaining issues in the latest test version (build 588)?

I did a "quick and dirty" test of this issue: http://www.macecraft.com/bugtracker/bug/111243/

The fix is not working.

That is, the first PT task started still ends abruptly when the second PT task ends.

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

When two tasks are automated to run at startup, they interfere with each other and seldom complete their jobs.

Sometimes, an APPCRASH shows up in WER. This exWith XP-P SP3 ample is, I believe, v.1.0.9.580:

I can NOT confirm this problem.

With XP-P SP3 I ran several tests with 2 started copies of jvPT2009-v588 running Registry Cleaner.

Both copies complete normally, no functional interferece, only a certain performance impact.

tullik

Leonardo wrote
... I can NOT confirm this problem.

With XP-P SP3 I ran several tests with 2 started copies of jvPT2009-v588 running Registry Cleaner.

Both copies complete normally, no functional interferece, only a certain performance impact.

It depends on which task ends first.

Try this:

1. Start a first instance of the 588 PT2009 and start the Registry Cleaner.

2. Immediately start a second instance of the 588 PT2009, start a tool that finishes quickly, then exit the second instance (all its windows).

3. Notice what happens to the first instance with the running Registry Cleaner.

4. Hint: it abruptly goes away.

Then try this:

1. Start a first instance of the 588 PT2009, but don't start any tools.

2. Immediately start a second instance of the 588 PT2009 and start the Registry Cleaner.

3. Exit the first instance of the 588 PT2009.

4. Notice what happens to the second instance with the running Registry Cleaner.

5. Hint: it keeps on running as it should.

It is true that if both tasks are manually allowed to finish what they are doing, the issue may not even be noticed.

However, with automated tasks, some of which may be configured to end automatically, the order in which the tasks end is not always the same, or even predictable.

This is not a new issue with 588.

It happens in every PT2009 version.

It happens in most PT2008 versions (it was introduced perhaps halfway through its life).

It does not happen with PT2007.

The impact is more noticeable when using automated tasks, and also when launching tools with command line parameters.

redseujac

Registry Finder / File Finder / probably all tools

Message "At least one search argument..."

After changing the focus on e.g. the Options tab, when you click on the blue link in the message window nothing happens.

I did a test and this issue applies probably to all such messages in every tool: the blue links don't work.

File Finder

In the Error Message "At least one...", the possibilities "Search by contents" and "Search by owner" are missing.

leonardo

tullik wrote
Leonardo wrote ... I can NOT confirm this problem.

With XP-P SP3 I ran several tests with 2 started copies of jvPT2009-v588 running Registry Cleaner.

Both copies complete normally, no functional interferece, only a certain performance impact.

It depends on which task ends first.

Try this:

1. Start a first instance of the 588 PT2009 and start the Registry Cleaner.

2. Immediately start a second instance of the 588 PT2009, start a tool that finishes quickly, then exit the second instance (all its windows).

3. Notice what happens to the first instance with the running Registry Cleaner.

4. Hint: it abruptly goes away.

Then try this:

1. Start a first instance of the 588 PT2009, but don't start any tools.

2. Immediately start a second instance of the 588 PT2009 and start the Registry Cleaner.

3. Exit the first instance of the 588 PT2009.

4. Notice what happens to the second instance with the running Registry Cleaner.

5. Hint: it keeps on running as it should.

It is true that if both tasks are manually allowed to finish what they are doing, the issue may not even be noticed.

However, with automated tasks, some of which may be configured to end automatically, the order in which the tasks end is not always the same, or even predictable.

This is not a new issue with 588.

It happens in every PT2009 version.

It happens in most PT2008 versions (it was introduced perhaps halfway through its life).

It does not happen with PT2007.

The impact is more noticeable when using automated tasks, and also when launching tools with command line parameters.

Thank you Tullik,

I repeated the two test you described and the results are as you described, It indeed depends on which task ends first.

« Previous Page Next Page »