Using the context menu to open in RegEdit a key found by jv16 using Registry Finder simply opens RegEdit. It does not open to the found key. Anyone else?

17 days later

Just curious, if jv16 us unable to do something simple such as open in RegEdit a previously found selected key, why might I get carried away with all the hype about new and upcoming features? Well, actually, I don't. Please fix the simple stuff, first.

15 days later

Actually, it is not as simple as it sounds because there is no standard way to open RegEdit to point to a specific registry entry that would work on every version of Windows from XP to Windows 10, with 32 bit and 64 bit versions of Windows, with different level of user account rights and so on and so forth. Furthermore, in some cases the issue is simply caused by the fact that the registry key user attempts to open simply doesn't exist in the registry. Though that shouldn't be the case here with Registry Finder.


That being said, this issue should be fixed in a next released build of PT X, which is scheduled to come out later this week.

7 days later

Can you (or someone else) confirm whether the issue has been fixed in the most recent version of PowerTools X?

6 days later

The issue appears NOT to have been fixed with 4.0.0.1514.


It is said, "Furthermore, in some cases the issue is simply caused by the fact that the registry key user attempts to open simply doesn't exist in the registry." This doesn't make much sense given each key I attempt to open was first found by Registry Finder.

Actually, it is not as simple as it sounds because there is no standard way to open RegEdit to point to a specific registry entry that would work on every version of Windows from XP to Windows 10, with 32 bit and 64 bit versions of Windows


With due respect, it's not that my expectation came from out of the blue. Rather, jv16 claims to do what you say above isn't so simple. Because you say so, I expect it to work. It certainly appears to with the FREE Nirsoft regscanner.


Further, because the issue raised here is easily verified, it gives me pause regarding the efficacy of those featured claimed that I'm not likely to verify 'til I need them. At such time, I'd hate to be surprised.

What version of Windows are you using?


The issue is not easily verified, as the feature is working in every test environment we have tried it on, also, no other user is reporting the same problem. If a problem is generic, that is, it exists in all systems, we usually get tens or hundreds of bug reports about it.


Could you download and install the latest Beta version of jv16 PowerTools 2016 from here: https://www.macecraft.com/forum/viewtopic.php?f=10&t=5789 - try the Open In RegEdit feature and send over the contents of the \Backups directory. It will contain debug information about this issue which would help us to fix it.