Did you see the additional info post that I posted concerning the Internal Errors using Clean and Fix on Windows 7 x86 Professional?
jv16 PowerTools 2011 Beta4 released
Version 2.0.0.995 with x64 Windows 7
Action History with C&FMC items:
- 1. "Show backup" on a time stamp grouping line doesn't do anything.
2. "Show backup" seems always to load the Registry data window first, then the Files window, even when the action item clearly is about files.
3. The action code "TempFileRemoval" is on lines showing empty directories detected via the Start Menu Tool.
4. When you close the Backup Tool window while the Action History window is still up, then try to open the Backup Tool from the main window, the Backup Tool doesn't load. Instead, the Action History goes through a time consumng reload process. After the list appears, PowerTools continues heavy CPU use (~40%). When you then close all PowerTools windows, PowerTools drops from the task bar. After about a minute, an AV occurs. jv16pt.exe still shows active in the Task manager and you have to kill it.
Attachment has debug log and bugreport.
*Action History tests 01.zip
_______________________________________________
In most of the tests, the tool finds the correct backup OK.
Once, it said a backup didn't exist (words to that effect), when it did.
Another time, after using the Action History, the Backup Tool, when started from the main window in the same session, would not populate its list.
However, I have not been able to reproduce those issues to document them. Maybe another beta tester will have more luck.
Over time, multiple instances of the Initial Setup registry backups can accumulate in the Backups folder.
I wonder which ones would be accessed by Backup Tool-->Tools-->Registry Recovery-->...?
*
tullik wroteVersion 2.0.0.995 with x64 Windows 7
Access violation during load of Action History list.
I'm afraid I cannot reproduce this problem.
jv16 wrotetullik wroteVersion 2.0.0.995 with x64 Windows 7
Access violation during load of Action History list.
I'm afraid I cannot reproduce this problem.
I can't either, on purpose. It, and a few other untoward symptoms, only happen sometimes, usually just once.
There's enough of these to indicate some sort of stability issue in the tool. Fortunately, more often than not, the tool's functions can be tested.
siliconman01 wrotePlease examine again. I have included more info for showing the result
: Failed to modify "HKEY_CLASSES_ROOT\{0E558950-6D70-4570-70EC-3F15777FBBA1}\"!
I did see these, but these are only errors relating to the fact that Windows doesn't allow these keys to be modified.
I did not see the "Internal Error BT-RK" though, can you reproduce the problem?
tullik wrote__________________________________________________
Version 2.0.0.995 with x64 Windows 7
Action History with C&FMC items:
- 1. "Show backup" on a time stamp grouping line doesn't do anything.
Confirmed and fixed.
tullik wrote2. "Show backup" seems always to load the Registry data window first, then the Files window, even when the action item clearly is about files.
This is correct and by design. The tool must first load up its list of backups in order to locate the correct backup.
tullik wrote3. The action code "TempFileRemoval" is on lines showing empty directories detected via the Start Menu Tool.
I think you are wrong. As far as I can tell, Start Menu Tool correctly marks the items as "EmptyDirRemove" but Clean and Fix My Computer logs empty folder removals as "TempFileRemoval". Am I correct? In such case, the problem is now fixed, Clean and Fix My Computer will starting from the next build log empty folder removals as "EmptyDirRemove".
tullik wrote4. When you close the Backup Tool window while the Action History window is still up, then try to open the Backup Tool from the main window, the Backup Tool doesn't load. Instead, the Action History goes through a time consumng reload process. After the list appears, PowerTools continues heavy CPU use (~40%). When you then close all PowerTools windows, PowerTools drops from the task bar. After about a minute, an AV occurs. jv16pt.exe still shows active in the Task manager and you have to kill it.
Can you reproduce the problem? I can't.
jv16 wrotesiliconman01 wrotePlease examine again. I have included more info for showing the result
: Failed to modify "HKEY_CLASSES_ROOT\{0E558950-6D70-4570-70EC-3F15777FBBA1}\"!
I did see these, but these are only errors relating to the fact that Windows doesn't allow these keys to be modified.
I did not see the "Internal Error BT-RK" though, can you reproduce the problem?
Yes, I can reproduce it at will. These keys are created when I run program "VHS to DVD" which converts VHS tapes to DVDs. This is not a permissions problem because Ace Utilities and TuneUp Utilities 2011 easily detect and removes them. The Internal Error BT-RK occurs some 33 times during the attempted Fix.
Further Info: jv16 actually removes these keys even though it issues all these BT-RK errors.
jv16 wrotetullik wrote3. The action code "TempFileRemoval" is on lines showing empty directories detected via the Start Menu Tool.
I think you are wrong. As far as I can tell, Start Menu Tool correctly marks the items as "EmptyDirRemove" but Clean and Fix My Computer logs empty folder removals as "TempFileRemoval". Am I correct? In such case, the problem is now fixed, Clean and Fix My Computer will starting from the next build log empty folder removals as "EmptyDirRemove".
Actually I wasn't wrong, just unclear. The heading for the report was "Action History with C&FMC items." I should have said "via Start Menu Tool functionality."
jv16 wrotetullik wrote4. When you close the Backup Tool window while the Action History window is still up, then try to open the Backup Tool from the main window, the Backup Tool doesn't load. Instead, the Action History goes through a time consumng reload process. After the list appears, PowerTools continues heavy CPU use (~40%). When you then close all PowerTools windows, PowerTools drops from the task bar. After about a minute, an AV occurs. jv16pt.exe still shows active in the Task manager and you have to kill it.Can you reproduce the problem? I can't.
All that happened the one time I did that sequence of actions. I will do it again (later) to see if it recurs.
tullik wroteOver time, multiple instances of the Initial Setup registry backups can accumulate in the Backups folder.
Do you always see the __SystemRecoveryX__ backups in the Backup Tool, or have you made something to show them? Users are not supposed to see these backups in the Backup Tool.
tullik wroteI wonder which ones would be accessed by Backup Tool-->Tools-->Registry Recovery-->...?
That is indeed a good point. At the moment the backup is selected by random, but for the next build the very latest backup will be selected.
tullik wroteActually I wasn't wrong, just unclear. The heading for the report was "Action History with C&FMC items." I should have said "via Start Menu Tool functionality."
Oh yes, in any case, the issue is now fixed.
jv16 wrotetullik wrote4. When you close the Backup Tool window while the Action History window is still up, then try to open the Backup Tool from the main window, the Backup Tool doesn't load. Instead, the Action History goes through a time consumng reload process. After the list appears, PowerTools continues heavy CPU use (~40%). When you then close all PowerTools windows, PowerTools drops from the task bar. After about a minute, an AV occurs. jv16pt.exe still shows active in the Task manager and you have to kill it.Can you reproduce the problem? I can't.
tullik wroteAll that happened the one time I did that sequence of actions. I will do it again (later) to see if it recurs.
In XP-SP3 I can confirm this, however without the Access violation occuring!
After closing the Action History window (only jvPT window left) the windows Task Manager keeps showing 50% processor time for jv16PT on a dual core Intel.
Closing the jv16PT window seems to work OK but the Task Manager keeps showing 50% processor time for jv16PT.
Task must be killed with the windows Task Manager.
PS: Action History list takes 12 minutes to build, even closing Action History takes 'quite a while'. Testing this part of jv16PT is therefore not an easy job.
siliconman01 wroteYes, I can reproduce it at will. These keys are created when I run program "VHS to DVD" which converts VHS tapes to DVDs. This is not a permissions problem because Ace Utilities and TuneUp Utilities 2011 easily detect and removes them. The Internal Error BT-RK occurs some 33 times during the attempted Fix.
Further Info: jv16 actually removes these keys even though it issues all these BT-RK errors.
Issue confirmed and fixed, thank you for reporting!
Leonardo wrotePS: Action History list takes 12 minutes to build, even closing Action History takes 'quite a while'. Testing this part of jv16PT is therefore not an easy job.
When it does open, how many items does it show? You can see this from the bottom of the window.
jv16 wroteDo you always see the __SystemRecoveryX__ backups in the Backup Tool, or have you made something to show them? Users are not supposed to see these backups in the Backup Tool.
I used PowerTools 2009.
Its Directories.dat Is this:
Backups=C:\Program Files\Macecraft\F\_2011\Backups
Cache=C:\Program Files\Macecraft\F\_2009\Cache
Tasks=C:\Program Files\Macecraft\F\_2009\Tasks
Snapshot=C:\Program Files\Macecraft\F\_2009\Snapshots
Settings=C:\Program Files\Macecraft\S\2009\_Yes (PT2009)
jv16 wroteLeonardo wrotePS: Action History list takes 12 minutes to build, even closing Action History takes 'quite a while'. Testing this part of jv16PT is therefore not an easy job.
When it does open, how many items does it show? You can see this from the bottom of the window.
I used the UserActionLog.txt file from Beta 1. It took about an hour to load the list. The status bar shows there are over 17,000 items.
Update:
- With the list just sitting on my desktop with no use being made of any PowerTools functions, jv16pt.exe continues to use a steady 25% of an AMD quad-core processor.
tullik wrotejv16 wrotetullik wrote4. When you close the Backup Tool window while the Action History window is still up, then try to open the Backup Tool from the main window, the Backup Tool doesn't load. Instead, the Action History goes through a time consuming reload process. After the list appears, PowerTools continues heavy CPU use (~40%). When you then close all PowerTools windows, PowerTools drops from the task bar. After about a minute, an AV occurs. jv16pt.exe still shows active in the Task manager and you have to kill it.Can you reproduce the problem? I can't.
All that happened the one time I did that sequence of actions. I will do it again (later) to see if it recurs.
The red part is reproducible.
tullik wrotejv16 wroteLeonardo wrotePS: Action History list takes 12 minutes to build, even closing Action History takes 'quite a while'. Testing this part of jv16PT is therefore not an easy job.
When it does open, how many items does it show? You can see this from the bottom of the window.
I used the UserActionLog.txt file from Beta 1. It took about an hour to load the list. The status bar shows there are over 17,000 items.
Update:
- With the list just sitting on my desktop with no use being made of any PowerTools functions, jv16pt.exe continues to use a steady 25% of an AMD quad-core processor.
The Action History list opens with all groups fully expanded (is this really usefull?) and lists a total of 4468 items
XP_Beta4b_ActionHistoryList_Collapsed.jpg
jv16 wrotetullik wrote4. When you close the Backup Tool window while the Action History window is still up, then try to open the Backup Tool from the main window, the Backup Tool doesn't load. Instead, the Action History goes through a time consuming reload process. After the list appears, PowerTools continues heavy CPU use (~40%). When you then close all PowerTools windows, PowerTools drops from the task bar. After about a minute, an AV occurs. jv16pt.exe still shows active in the Task manager and you have to kill it.Can you reproduce the problem? I can't.
tullik wroteAll that happened the one time I did that sequence of actions. I will do it again (later) to see if it recurs.
tullik wroteThe red part is reproducible.
In XP-SP3 I can consistently reproduce the 'red part', but I also encountered the 'blue part'