Serious problems with 2008

michel

Have just upgraded from 2007 to 2008 version and have serious problems. To name just 2:

- problems with startup manager which has already been mentionned number of times (strange look of the window)

- Registry cleaner freezes after analyzing number of keys (never the same number); abort does not work must use CTL-ALT-Del to kill the program

Using Win XP/SP2

michel

Have downloaded the latest version of 2008 build 449, the startup manager problem seems to be fixed.

The problem with registry cleaner still present : ssytem freezes after about 16 000 keys (6 threads) in the safest mode.

using XP Pro/SP2

leonardo

XPP/ SP2, jv122008 with latest download version.449

During a register scan, including a "file reference scan" causes jv162008 to hang-up/freeze!

(see the "advanced engine setting" tab to enable/disable the "file reference scan")

With the task manager jv16 can be cancelled.

If I disable only the "file reference scan" in the "advanced engine setting" tab, NO hang-up/freeze occurs!

michel

Disabling the "file reference scan solved the problem of hang up/freeze.

- Now on the next sterp, when trying to fix the problems (18 registry errors) nothing happens

What can I do ?

- concerning yhe file reference problem is there a way to solve this part ?

leonardo

For the remaining errors, that will not be solved with a normal "Select all" followed by activating the "fix" botton,

The following works for me:

1. Open all Pull Down Windows up till the individual key/entry error level,

2. Select one individual error and press the "fix botton",

3. Repeat this process till all the remaining scan errors are fixed.

(In your case this probably means to repeat this action 18 times, =no. of errors)

I hope the developper will look at the "file reference scan" problem!

michel

Have managed to clean everything running Leonardo' suggestion.

Hope now that the developer looks at the "file reference scan" and offers a solution.

leonardo

XP-P SP2, jv16_2008 with latest download version.451

The following problem still exists in version .451:

During a Register Scan, with the "File Reference Scan" enabled in the Advanced engine settings, causes jv16_2008 to hang-up/freeze!

With the task manager the not responding task jv16PowerTool can be cancelled.

If I disable the "file reference scan" in the "advanced engine setting" tab, NO hang-up/freeze occurs!

tullik

Leonardo wrote
... The following problem still exists in version .451:

During a Register Scan, with the "File Reference Scan" enabled in the Advanced engine settings, causes jv16_2008 to hang-up/freeze!

With the task manager the not responding task jv16PowerTool can be cancelled.

If I disable the "file reference scan" in the "advanced engine setting" tab, NO hang-up/freeze occurs!

Confirmed! It doesn't seem to happen every time ... but I'm still checking just the "file reference scan" for other reasons ...

redseujac

tullik wrote
... but I'm still checking just the "file reference scan" for other reasons ...

Tullik, look here.

tullik

redseujac wrote
tullik wrote... but I'm still checking just the "file reference scan" for other reasons ...

Tullik, look here.

I noticed that post by siliconman01. The install paths look like leftover stuff pertaining to a Vista install -- probably not needed any longer in the registry ...

siliconman01

tullik,

When you get SP1 on your Vista system, note the number of registry keys of this type get Errors when jv16 attempts to delete them. Windows Core reports them as Invalid keys.

tullik

siliconman01 wrote
tullik,

When you get SP1 on your Vista system, note the number of registry keys of this type get Errors when jv16 attempts to delete them. Windows Core reports them as Invalid keys.

I just finished processing the stuff newly shown in 451. There were almost 400 items, and I think all are legitimate "does not exist" items. I removed them in groups with no problems, saving 124 "...\component based servicing\packages\..." items for last. The 124 all failed to remove for the alleged "invalid key" reason, so it's a non-SP1 situation too.

I say "alleged" because the only user with full control permissions is the so-called "Trusted Installer." It is likely to be some sort of "super permissions" thing by Microsoft ... I wonder if jv16 can find a workaround for PowerTools ...

In the meantime, for routine use, I will continue to have "\Component Based Servicing\Packages" in my Ignore words tab.

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.

rangerbob

Just installed the 451 update and jv16 PowerTools 2008 is totally unusable for me. When I execute the program all I get is the light blue screen and I am unable to select any of the tools because they do not show up. The previous version was working fine for me.

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.