V1.9.0.548- x64 Startup Manager still not fixed

siliconman01

x64 Startup Manager still is not showing HKLM\Software\Microsoft...\Run items.

jv16

I am happy to report that this issue is now fixed, the Startup Manager is now almost perfectly 64 bit Windows compatible. It can already list all the data, the Delete feature still needs some work.

The new version with hopefully full x64 support will be released later in this month.

siliconman01

Awesome... looking forward to the next test on x64.

jv16

No need to wait for too long, here you go:

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

This is a private test build to test the 64 bit compatibility, this version is not ment for production use. With this test build two features should be fully 64 bit compatible: Registry Compactor and Startup Manager. Other tools should also be working rather well with 64 bit Windows, but I cannot say much about that yet because I haven't fully tested the other tools under 64 bit system yet.

And oh, a "" text should show in the product's caption bar when it is running in 64 bit aware mode.

Please let me know (in this thread) how it works 8)

siliconman01

Vista SP1 x64 Business, PT Test Version.

The Registry Compactor is still getting an error that it cannot open registry key HKLM\Security during the compaction. The debug logs are provided. It compacts all the hives except the Security hive.

jv16

siliconman01 wrote
Vista SP1 x64 Business, PT Test Version.

The Registry Compactor is still getting an error that it cannot open registry key HKLM\Security during the compaction. The debug logs are provided. It compacts all the hives except the Security hive.

Is it possible to compact the Security hive with any other compactor program? And what about the Startup Manager?

siliconman01

Is it possible to compact the Security hive with any other compactor program?

Yes, I can compact it with two other x64 registry compactors on my system...No errors reported on either.

And what about the Startup Manager?

The Startup Manager is properly displaying all startup entries in the 3 Run registy keys. I "removed" one entry from each RUN keys. PT did remove them properly. HOWEVER, it cannot restore the removed entry back to HKCU\Software\Microsoft\Windows\CurrentVersion\RUN. It can restore the removed entries back to the two RUN keys in HKLM. This is 100% repeatable. Do you need a debug log?

siliconman01

Is it possible to compact the Security hive with any other compactor program?

Yes, I can compact it with two other x64 registry compactors on my system...No errors reported on either.

I get the same error when compacting my XP-SP3 x86 Home Edition system with the official Build 550 of PT 2009. So it is not a x64 bit problem only.

siliconman01

Okay, here is what happened when I tried to restore the HKCU...\Run entry back. It restored it to the wrong location in HKCU.

Here is the HCKU\Software\Wow6432 key BEFORE the restore.

Windows Registry Editor Version 5.00

"Version"="8,0,6001,18762"

"Locale"="*"

"Version"="8,0,6001,18702"

"Locale"="*"

"Version"="1,1,1,9"

"Locale"="EN"

"Version"="6,0,6001,18000"

"Locale"="*"

"Username"="Tom"

"Version"="11,0,6000,6324"

"Locale"="EN"

"Version"="6,0,6001,18167"

"Locale"="en"

"Version"="8,0,6001,18762"

"Locale"="en"

And here is what PT 2009 Restore did to this key.

Windows Registry Editor Version 5.00

"Version"="8,0,6001,18762"

"Locale"="*"

"Version"="8,0,6001,18702"

"Locale"="*"

"Version"="1,1,1,9"

"Locale"="EN"

"Version"="6,0,6001,18000"

"Locale"="*"

"Username"="Tom"

"Version"="11,0,6000,6324"

"Locale"="EN"

"Version"="6,0,6001,18167"

"Locale"="en"

"Version"="8,0,6001,18762"

"Locale"="en"

"WeatherWatcherLive"="\"C:\\Program Files (x86)\\Weather Watcher Live\\ww.exe\""

siliconman01

This pertains to Vista SP1 x64 Business with the test version of PT 2009, Registry Cleaner tool:

In the set of keys shown below under "Invalid file or directory reference", PT says that these are in the location. They are however in . The detection itself is a valid error because I do not have a C:\Windows\nvtmpinst folder on my system. I've attached the exported registry key for PnpLockdownfiles. An attempt to Fix these by PT results in an error message.

siliconman01

In the registry cleaner, structured format, the full row select/unselect is not working correctly. Once you unselect an item, it cannot be re-selected. If you click on another item, the original item unselected then selects. Makes this feature unuseable. I suspect that this is not just on x64.

siliconman01

In aggressive mode, there are errors being detected for TrustedInstaller.exe and hnetcfg.dll. These appear to be invalid detections by PT 2009. Also, registry keys for a network monitoring gadget of Windows Sidebar appears to be an invalid detection (removal of these keys damages the gadget).

jv16

siliconman01 wrote

The Startup Manager is properly displaying all startup entries in the 3 Run registy keys. I "removed" one entry from each RUN keys. PT did remove them properly. HOWEVER, it cannot restore the removed entry back to HKCU\Software\Microsoft\Windows\CurrentVersion\RUN. It can restore the removed entries back to the two RUN keys in HKLM. This is 100% repeatable. Do you need a debug log?

Instead of Debug Log I'd like to get the backup file (entries.reg) of the entry at HKCU\Software\Microsoft\Windows\CurrentVersion\RUN. I'm asking for the backup file in order to see whether the problem is in the backup creation or in restoring the backup. I'd guess the first, but I would like to be sure.

siliconman01

The problem is in the backup itself for HKCU. The two HKLM backups are correct.

Also, did you get my email this AM with the Debug Registry Cleaner run?

Windows Registry Editor Version 5.00

; File created by TBackupTool

; Component version: 1.4.2

; Component used by: jv16 PowerTools 2009

; Program version: 1.9.0.550

; File Description: Display.exe, THGuard.exe, ww.exe

; Date: 15.04.2009

; Time: 09

"PowerChute"="\"C:\\Program Files (x86)\\APC\\APC PowerChute Personal Edition\\Display.exe\""

"THGuard"="\"C:\\Program Files (x86)\\TrojanHunter 5.0\\THGuard.exe\""

"WeatherWatcherLive"="\"C:\\Program Files (x86)\\Weather Watcher Live\\ww.exe\""

siliconman01

One area that PT 2009 seems to miss several invalid keys is in the MuiCache registry keys located throughout the x64 and x86 registry sections. Competitors find these invalid or empty keys after PT 2009 has run. I'm speaking of the MuiCache keys such as:

HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\Shell\MuiCache

jv16

FYI: Build 542 does not address any of these findings, no need to test it with x64.

redseujac

jv16 wrote
FYI: Build 542 does not address any of these findings, no need to test it with x64.

I guess the developer means "Build 552"?

siliconman01

Just for info, the backup problem still exists in Build 552 on x64 systems, even though it is addressing the x86 part of the registry.

Windows Registry Editor Version 5.00

; File created by TBackupTool

; Component version: 1.4.2

; Component used by: jv16 PowerTools 2009

; Program version: 1.9.0.552

; File Description: Error relating to Obsolete software entryMRU and other history data

; Date: 18.04.2009

; Time: 16

"Name"="Dwm.exe"

"Download Directory"="D:\\ProgramUpdates Vista x64\\jv16 PowerTools 2009 x64"

"url6"="http://www.hulu.com/"

"url5"="http://www.foxnews.com/"

"url4"="C:\\Users\\Tom\\Downloads"

"url3"="Computer"

"url2"="D:\\"

"url1"="D:\\ProgramUpdates Vista x64"

As a suggestion, it would be safest to temporarily have PT throw out a warning message to anyone using it on x64 that PT is not working on x64 systems and should not be used. You already have it displaying the x64 status on the main window of PT so perhaps that can be used to trigger such a warning message

jv16

redseujac wrote
jv16 wroteFYI: Build 542 does not address any of these findings, no need to test it with x64.

I guess the developer means "Build 552"?

Yes, 552.

jv16

siliconman01 wrote
In aggressive mode, there are errors being detected for TrustedInstaller.exe and hnetcfg.dll. These appear to be invalid detections by PT 2009. Also, registry keys for a network monitoring gadget of Windows Sidebar appears to be an invalid detection (removal of these keys damages the gadget).

These issues are now fixed, thank you for the attached files, they made fixing the problem very easy!