Registry Editor crashing

Page 7 of 9 FirstFirst ... 56789 LastLast

  1. Posts : 41
    Windows 10 Pro
       #61

    Intrepid1 said:
    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: Attachment 58413

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


  2. Posts : 54
    Windows 10
       #62

    Intrepid1 said:
    Here is Regedit extracted from the RTM Windows 10 Pro 64-bit build 10240
    It may work with new MUI but to be on safer side you'll need MUI from the corresponding version too.
      My Computer


  3. Posts : 8
    windows 10 pro
       #63

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


  4. Posts : 591
    Windows 10 Pro 64bit; Windows 10 TP; KDE Neon
    Thread Starter
       #64

    schmety said:
    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...
    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.
      My Computers


  5. Posts : 134,237
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #65

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


  6. Posts : 31
    Windows 10
       #66

    Yep, I'm getting it too


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


  7. Posts : 113
    Win10
       #67

    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.
    http://www.resplendence.com/downloads

    O&O RegEditor
    OO RegEditor

    Search Only - Opens results in Regedit:
    Nirsoft RegScanner
    http://www.nirsoft.net/utils/regscanner.html
    Last edited by Intrepid1; 17 Mar 2016 at 08:58.
      My Computer


  8. Posts : 75
    Windows 10 Pro
       #68

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


  9. Posts : 20
    Windows 10 Pro - what ever the latest Insider build is
       #69

    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.

    Joanne said:
    This problem, which I have reported 2 weeks ago, persists in my system with the latest Windows 10 Pro TH2, as well.

    I have clean installed Windows 10 Pro build 10586.3 (the latest build) twice. On my primary SSD as my main OS and on my secondary SSD, as an Insider with my MS Insider account. On both of these installations the Registry Editor crashes exactly as I describe on my first post. On both of these installations I have run SFC /SCANNOW and I have finally repaired both of them with DISM, and by running SFC twice afterwards.

    I'm grabbing the opportunity to report something else here, as well: I am VERY surprised about the fact that SFC detects corruption in my system immediately after the clean installation of the OS and of my system's drivers! I repeat: immediately after clean installing Windows 10 Pro, and after installing my system's drivers, I run SFC /SCANNOW and it finds corrupted files!... I then repair them with DISM and SFC run twice. Very surprising since I've not touched (altered, tweaked) anything!

    So, in my case there is no suspicion of malware, a virus or something like that. And I fully trust all of my devices - shown in my System Spec's.
      My Computer


  10. Posts : 591
    Windows 10 Pro 64bit; Windows 10 TP; KDE Neon
    Thread Starter
       #70

    vijer said:
    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...
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:30.
Find Us




Windows 10 Forums