Windows 10: Registry Editor crashing

Here is Regedit extracted from the RTM Windows 10 Pro 64-bit build 10240 (this was the first official build released). This resolves the issue, but I don't know what changes were made to regedit in the most recent build (10586) and why.
Download Regedit.exe Win10 64-bit Build 10240: Regedit Win10 b10240.zip

You'll Need to Take ownership of regedit.exe in C:\Windows and then assign yourself full permissions before you can replace the file. Remember to Backup the Original First!!!! Here are instructions:
How to Manually Take Ownership of a File or Folder in Windows - Make Tech Easier

VirusTotal.com Report of above regedit.exe file:
https://www.virustotal.com/en/file/9...39f8/analysis/

 

Thanks I will give this a go. Microsoft seem to be taking their time with a fix.

 

It may work with new MUI but to be on safer side you'll need MUI from the corresponding version too.

 

hi !



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.

 

Hello, I am the thread starter.

I am sorry this issue is happening in your system. I am still facing this Registry crashing issue on my system, as well... *Sad
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)
Registry Finder

Resplendence Registry Manager - Free and Pay Versions. I've used the paid version for years.
Resplendence Software - Free Downloads

O&O RegEditor
OO RegEditor

Search Only - Opens results in Regedit:
Nirsoft RegScanner
RegScanner: Alternative to RegEdit find/search/scan of Windows

 

I discovered I have this problem too, and I found this thread. Hopefully this gets fixed soon...

 

I have the same problem on a CLEAN install of build 14279. This is a Microsoft issue and we all need to jump on the reporting tool and let them know about it.

 

Exactly! And in addition, ask from your friends / colleagues / acquaintances who run any version of Windows 10 to perform a Registry Search for a non-existent value... Because I am 99% sure that this issue is present in 95% of all the systems out there, or that it will appear on them, at some point in time...

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...

 

I mean, how do you screw up the registry editor? Should work without question. And to ad insult to injury, MS wants to tell us:

"The registry editor has stopped responding we are attempting to find a solution" F@#$@ MS couldn't find the solution to millions of other errors why waste our time, just close and reopen the app, don't Fing waste my time with their silly attempt to find a solution.

 

No way am I going to go third-party for this. What's next, a third party NTFS?

 

From what I can tell, this is fixed in Insider 14316. Just have to wait for it to roll out in a cumulative update for current build.

 

This is really good news!
Thanks for the heads up, f14tomcat