Registry Editor crashing

Page 1 of 9 123 ... LastLast

  1. Posts : 591
    Windows 10 Pro 64bit; Windows 10 TP; KDE Neon
       #1

    Registry Editor crashing


    Hello, I hope I am posting in the appropriate section :)

    In the recent TP builds of Windows 10 Pro I am facing a weird problem with the Registry Editor in my system, so I thought to post here in order to research this matter deeper and discover what is causing it.

    Specifically, starting from TP build 10565 - if I recall correctly - and continuing in the latest TP build 10576, if I will run RegEdit (as Admin) and search for an arbitrary, goofy, non-existent value, the Registry Editor keeps searching and searching and searching - I've left it for max = 20 minutes (!) - and then when I press "Cancel" it crashes. A pop-up window comes up saying "The Registry editor has stopped working." Then it restarts.

    I've posted this issue in the "Announcing...." threads but it seems that other members of this site do not face this issue. I've heard other people, too, having it though, and also when I posted this problem in the Feedback I got 7 up-votes.

    - What is going on, what is the problem, you think?
    - How can I check out what is causing this? Should I look in the Event Viewer and if so, where and how exactly?

    I'd like to add that this crash is happening in my system both on clean installations and on in-place upgrades. I do not perform any kind of modification / tweaking, and I do not install any programs. I keep my TP builds as virgin (unaltered) as possible.

    Thank you :)

    PS: My System Specs is fully updated. Also, I have run SFC /SCANNOW and it does not find any integrity violations but of course I am eager to try whatever will be suggested :)


    EDIT:
    After clearing all the Logs, so my entire Event Viewer, I have performed a search in the Registry again. It crashed, of course. Here is what I got from the Event Viewer:

    Registry Editor crashing-2.png

    Any ideas why is this happening on a clean-installed, virgin, installation and how can I resolve it?
    Last edited by Joanne; 31 Oct 2015 at 01:56.
      My Computers


  2. Posts : 1
    Windows 10
       #2

    I have the same problem in the latest version 10586. It's exactly as you describe.

    I know of no fix for this.
      My Computer


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

    Yes, it still exists on my 10586, too. I have already reported twice (on Win Feedback). Let's hope they will do something about it.
      My Computers


  4. Posts : 1
    64 bit Windows 10 Pro Version 1511 (OS Build 10586.17)
       #4

    Same problem here...
      My Computer


  5. Posts : 2,799
    Linux Mint 20.1 Win10Prox64
       #5

    Have you tried running: dism /online /cleanup-image /restorehealth
      My Computer


  6. Posts : 204
    Windows 10 Pro
       #6

    You might try this Repair Install Windows 10 with an In-place Upgrade - Windows 10 Forums

    Try Tweaking.com - Windows Repair Free/Pro Tweaking.com

    Run adwcleaner from Downloading AdwCleaner make sure you have no virus, maleware, etc.

    Create an iso install disk or usb with Windows media creator. Uninstall any anti-virus, anti-malware, and ad filters.
    Upgrade your Windows 10 . It will save your data and apps.

    I've done this with several laptops and desktops and it has fixed problems.

    good luck
      My Computer


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

    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 Computers


  8. Posts : 131
    Windows 10 PRO for Workstations
       #8

    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.
    We're exactly, once more, in the same situation. I've also expressed my concern about the fact of finding system corrupted files just after a clean installation; something that has been happening to me since a few Insider's builds before 10240.

    I also suffer from the same registry editor ailment and I have reported it using Windows Feedback. Hopefully, sooner rather than later, Microsoft will do something about it.

    Cheers!
      My Computer


  9. Posts : 41
    windows 10
       #9

    Greetings from Holly Jerusalem
    Today, I have the same problem as per image,I have followed all the suggestions of Mr. Slugger
    and even more, I reimaged my backup, ANY LUCK OF SOLUTION !!!!!!!!!!!!!!!!!

    Registry Editor crashing-screenshot-13-.png
      My Computer


  10. Posts : 54
    Windows 10
       #10

    If new regedit finds a long enough key, it loops as you show. Just use regedit from 10240, it don't have this bug.
      My Computer


 

  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 09:43.
Find Us




Windows 10 Forums