i noticed the same bahaviour, when i was seaching one string key in registry editor and
pressing F3 (next find), registry didn't finalize searching and i was able just to click cancel,,
Windows 10 pro 64bit build 1511,
new, clean install.
also i have another computer running Windows 10 home 64bit build 1511,
new, clean install, registry editor working normally.
I am sorry this issue is happening in your system. I am still facing this Registry crashing issue on my system, as well...
Even though I have reported it numerous times in Windows Feedback (as an Insider) it has not been fixed yet, and you can see when I have first discovered / referred to this by looking at the 1st post of this thread. It was on 31 Oct 2015, which feels like centuries ago...
My personal (and subjective) belief / opinion is that many (many) more people are having this problem but they are not aware of it simply because they do not perform Registry searches for values that do not exist, in their systems.
They best thing you can do is to report this in Windows Feedback and upvote every similar issue reference you can find there.
Let's hope that one day this will be fixed. On my primary OS, Win 10 Pro, I am using the RegEdit file given a couple of posts above, and this is the only way I have found to resolve this issue: to prevent my Registry Editor from crashing.
Well another fix would be not to use the built-in registry program in Windows. I have not used it since Windows 7. Their are a few of us on here, that use a program called Registry Workshop. This is not a free program thou. But well worth the price, and it has always worked, with no problems. Of course if you don't edit your registry, search for things in your registry, then I guess stick with your Windows version.
I was just making sure a app I uninstalled cleaned up its registry entries. A search found several entries but eventually hung after several continued searches F3. Regedit is using 8.7% of my i7 CPU and has gone on for about 20 minutes. Well, at least I'm not the only one. God, as a retired programmer, I wonder what's going on with the innards of this one.
Regedit chokes on keys that are too long and/or deny permission. That doesn't mean the keys won't be read by the application or OS. The keys should be left alone. Simply use an alternate registry editor:
Sergey Filippov Registry Finder (and editor)
Resplendence Registry Manager - Free and Pay Versions. I've used the paid version for years.
Search Only - Opens results in Regedit:
Last edited by Intrepid1; 17 Mar 2016 at 08:58.
I discovered I have this problem too, and I found this thread. Hopefully this gets fixed soon...
Finally, quite a few times, third-party Registry Editors have been suggested. I do not know how you all feel about this, but personally it does NOT feel good to me, it does NOT feel right to me, to use a third-party tool for an action as FUNDAMENTAL as dealing with the Registry! This is something that it should function perfectly right for the very beginning, which is also the reason why the argument "Windows 10 is still a work in progress, bugs are going to exist / are supposed to exist" does not sound valid to me...