V1.9.0.526/531 Registry Compactor Fails on Vista 64-bit

siliconman01

And here is a debug log where extended messages was off and I tried to turn it on and test via the Settings

jv16

I have now tried to fix the messaging problem:

http://www.macecraft.com/downloads/betas/jv16pt_setup_siliconman03.exe

Also, feel free to try to compact the hives with the Registry Compactor. Could you also try the Flush Caches problem now?

siliconman01

Neither the message issue nor the flush cache issue are fixed. Same characteristics as previous test version.

siliconman01

The Compactor does nothing when I click on Compact. No response whatsoever. Attached is the debug log.

jv16

siliconman01 wrote
The Compactor does nothing when I click on Compact. No response whatsoever. Attached is the debug log.

According to the debug log the same messaging problem also occurs here. Could you try it with the Message Windows feature turned off? I'm working on to get the messaging problem fixed.

siliconman01

I changed messaging to "Show messages in normal Windows dialog". The compactor ran to completion and rebooted as specified. BAK_jv16PT files were created during the compacting on UsrClass.dat, NTUSER.DAT, SOFTWARE, and SYSTEM. The other hives did not look like they needed any compacting. This was with test version siliconman04.

So it looks like the Compactor itself is now working. :)

jv16

Good! I spoke with the developer who made the Messaging Window component. He would like to know whether file riched20.dll and riched32.dll exist in your system? If they do, could you please give me the dates or versions of them?

siliconman01

riched20.dll exists in C:\Windows\System32 and C:\Windows\SysWOW64.

File Version: 5.31.23.1228

Product Name: Microsoft RichEdit Control, version 3.1

Date: 20-Jan-2008

File Size: 592 kbytes

riched32.dll exists in C:\Windows\System32 and C:\Windows\SysWow64.

File Version: 6.0.6001.18000

Product Name: Microsoft Windows Operating System

Date: 20-Jan-2008

File Size: 10.5 kbytes (System32 folder) & 8.00 kbytes (SysWOW64 folder)

NOTE: Messaging appears to be working properly in all the PT 2009 official releases.

siliconman01

I think there is also a bug in the official releases (build 531) of PT 2009 concerning the additional information message window. When PT 2009 is first started, the message window concerning testing the system does not appear on every startup of PT 2009. It appears the first time PT 2009 is opened following an new installation. However, thereafter it does not appear. If my memory serves me correctly, this started with build 528.

tullik

siliconman01 wrote
I think there is also a bug in the official releases (build 531) of PT 2009 concerning the additional information message window. When PT 2009 is first started, the message window concerning testing the system does not appear on every startup of PT 2009. It appears the first time PT 2009 is opened following an new installation. However, thereafter it does not appear. If my memory serves me correctly, this started with build 528.

That is by design to accord with this feature request: Show starting system test messages less often

siliconman01

That is by design to accord with this feature request: Show starting system test messages less often

ahhh...okay. 8)

siliconman01

jv16,

Were you able to fix the messaging error that has been occurring in the test releases siliconman0x?

Feel free to ask me to further test for the x64 issues. :

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.

siliconman01

Using siliconman05 test version.

1. Messaging is working great on this build. Thanks for the fix.

2. The Registry Compactor is broken again on this version. It is showing 0 bytes for the size of hives in C:\Windows\System32\Config again.

3. The new improved GUI for the Registry Cleaner looks excellent.

4. Aggressive registry cleaning has picked up over 1800 items. I want to switch over to my backup drive and do some investigation on these and will make a separate post shortly.

siliconman01

The registry cleaner in aggressive structured format is now showing these additional 1200+ items as registry keys with incorrect permissions. If they are selected for FIX, PT removes all permissions and makes them totally inaccessible via standard regedit. Prior to performing the fix, I checked the permission on several of the keys and it was valid.

In the new GUI for registry cleaner, full row select and full row unselect is not working. Also, if you want to fix or remove a single item, you have to checkmark it and then highlight it as well before PT will fix or remove it.

Select ALL does not place checkmarks in the boxes. It highlights the entries, but without the check marks, nothing is fixed or removed.

siliconman01

In addition to my posts above, the aggressive scan yields erratic results. One run it will give the incorrect permissions posts above. The next run, it may or may not give the incorrect permissions, but will give the results in the attachment herein...which are the false detections in previous versions.

tullik

Various observations v.1.9.0.536 (siliconman05)

* Registry Cleaner:

* fails to locate C:\hiberfil.sys. Its just in a WinPatrol "hidden" tracking entry -- no harm possible there …

* new GUI: checkboxes are very nice! As I got further into it (below), some issues became apparent ...

* new GUI: line and error category caption bars need Select/Unselect in the context menu.

* new GUI: status bar's selected count is not reliable when you click a line. It's OK if you click an error category caption.

* new GUI: when you check an error category checkbox, then click a single line below it, it is not certain what is actually selected. Just the single line, I think, though all the category's lines still have checked checkboxes, and the category caption area count still shows all lines selected ...

* new GUI: it is also not always certain what is actually selected when you do CTRL+click on lines or error category caption bars.

* new GUI: I think the status bar's selected count is probably reliable -- the problem likely lies with the other selection indications …

* new GUI: select all and select none from menu don't work right; neither do CTRL+A and CTRL+N.

* I'm sure these selection issues will be gone before release. It will be a beautiful thing.

* More later maybe...

tullik

Various observations v.1.9.0.536 (siliconman05)

These two issues are fixed in the prerelease test version:

Registry Find & Replace, bug when the match is in entry "Data" . . . . . . . . . . . . Fixed in v.1.9.0.5xx. . . . . (1)

Software Uninstaller, various issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fixed in v.1.9.0.5xx. . . . . (1)

Also, this general issue is fixed, but there are other GUI problems, mainly with selection and its feedback to the user:

Registry Cleaner, structured list GUI too slow and forgetful. . . . . . . . . . . . . . . Fixed in v.1.9.0.5xx. . . . . (1)

jv16

Could you please try this one:

http://www.macecraft.com/downloads/betas/jv16pt_setup_siliconman06.exe

Most of the problems relating to the new list component of the Registry Cleaner are now fixed (including the counting problems, Select menu now works too, as does Tools > Search. Ctrl + A etc do not yet work, also the list's own count numbers do not work if you any other selection methods than clicking (e.g. select > all)).

I have also attempted to address the 0 size problem of the Registry Compact. Could you verify whether the 0 size problem of the Registry Compact has been fixed, and whether the Registry Cleaner still produces false positives relating to "file or directory not found" error message? I have not addressed the registry key permission problem.

siliconman01

Results of siliconman06

1. The Registry Compactor did populate properly. I ran a registry compact and it did compact and reboot. The compact may have been incomplete because of the errors in 2 below.

2. On startup of PT 2009, it is failing to gain access to the registry...even with "Run as Administrator" selected. The debug log below shows numerous errors. I did run a registry scan and it reported 3800+ errors. I could not right click and save the list to attach it...probably because of the initial errors.

3. I won't report on what I experienced with the new GUI because of the initial errors and their possible impact.

« Previous Page Next Page »