Version 2.1.0.1141 on 64-bit Windows 7 -- Registry Cleaner


With some Wow6432Node keys, RegEdit appears not to open correctly.


With others, for example Obsolete software entry type errors, it works.


This is so for CTRL-click on a top panel green key and also for right click-->Open in RegEdit on a detail line. It seems some "green" keys really don't exist under the Wow6432Node section, but do exist in the other part of the registry.

Capture bad RegEdit open with Wow6432Node keys.JPG

21 days later

This issue is now fixed, thank you for reporting! The fix will be included to the next released build.


The issue was purely in the GUI, so nothing very serious.

Does this build fix this issue?

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

tullik wrote
Version 2.1.0.1141 on 64-bit Windows 7 -- Registry Cleaner


With some Wow6432Node keys, RegEdit appears not to open correctly.


With others, for example Obsolete software entry type errors, it works.


This is so for CTRL-click on a top panel green key and also for right click-->Open in RegEdit on a detail line. It seems some "green" keys really don't exist under the Wow6432Node section, but do exist in the other part of the registry.

Capture bad RegEdit open with Wow6432Node keys.JPG

In the absence of Tullik I did some testing with Registry Cleaner, W7-SP1-x64 and jv16PT b1165 on 'Wow6432Node keys' :


1. right click-->Open in RegEdit on a detail 'Wow6432Node key line' seems to work OK now. RegEdit opens correctly!


2. However CTRL-click on a top panel green key does NOT seem to work right.

a. If I place the cursor at the end of the 'top panel green key', the whole key name becomes underlined. CTRL-click causes RegEdit to open correctly.

b. If I place the cursor anywhere on the 'top panel green key' name, a part of the key name becomes underlined. In this case CTRL-click causes RegEdit NOT always to open on the location of the partial underlined green key name (it opens mostly on HKLM\Software) and sometimes jv16PT_b1165 even becomes 'non-responsive'.

Only Windows Task manager can than remove jv16PT.


EDITED: updated the 2b. text!

The problem should now be fixed, thank you for reporting! An updated test build with the fix included will be released shortly.