Windows 10: Windows 10 10586 build has a corrupt registry.

Well that's the thing - I would suspect that you just happen to be seeing the symptoms first with regedit, but whatever's wrong will eventually cause more widespread problems.

Case in point: I recently helped a relative with a laptop. The only apparent symptom was inability to establish a wifi connection to any hotspot other than the one in their home. After chasing lots of false trails, the system log led me to the real culprit: failing HD. The OS (Win7 in that case) was doing a phenomenal job of keeping the computer functional, but one critical DLL had been irretrievably corrupted, preventing new connections from being established. The system event log was stacked full of reports relating to bad sectors etc.

So check all the non-informational entries in the log. Even if the hardware itself is fine, there could all manner of bad things happening due to driver issues, and if so, they'll probably get logged one way or another.

 

Thanks for your input. I have not yet got to the bottom of it but I have ruled a few things out. I have 2 SSD's installed and I ran HD Tune and there were no errors (whether that proves anything I don't know).
I then installed Windows on my 2nd SSD with the same reg errors. Does that rule out an SSD fault?
I then tried the previous OS build which confirmed it WASN'T the new November build.
I get the errors without any driver installation. I am currently removing my 2 HDD storage drives and front 2 case usb hub connectors and the 19 pin usb 3 hub connector and installing Windows again.
Could the motherboard cause this even though it is showing no boot errors or error bleeps?
Anyway I could upload my system file to see if anyone could spot something obvious.
I don't mind if anything has failed, I just want to know what it is so I don't have to play the expensive guessing game of replacing 1 component at a time.
Oh and there is nothing in the event viewer out of the ordinary that I have not seen since windows 7 that I can't resolve and the device manager is also fine.


Edit. I have again installed the latest version of Windows 10 and installed no drivers. (Windows installed Nvidia in the background but that is not the cause).
I have removed several bits of hardware and there is only the rear USB's operational and my mouse/keyboard.
My Titan X is still there but that is fine.

I have attached my System info file if someone could take a look. I will definitely reward anyone who can point me to the culprit.

Below is also one of many keys in DeviceClasses that "error" when trying to open the "Properties" folder.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceClasses\{09485f5a-759e-42c2-bd4b-a349b75c8643}\Properties

System Info.zip

 

Another update. I removed my Titan X which left an empty PC apart from Keyboard/mouse.
I used a new SSD. Tested memory again with perfect results, burned the hell out of my 6700k with not a single error.
Installed Windows for the 50th time. No drivers installed , I ran another Regedit file search immediately as the format completed with the same search hang. It is littered with hundreds of keys that will not open due to errors.

It has to be a faulty motherboard despite it giving me zero issues that I can see. Normally motherboards either work or not but this obviously is not the case here. RMA time *Sad

 

This happens to me also - hangs and then crashes when you click cancel. It doesn't always happen, but sometimes though.

Others also get it - see Regedit.exe search crashing in W10 1511/TH2

You could report/upvote it in feedback - I don't have a more constructive answer, sorry.

 

Thanks for the link. Looks like it is not an isolated issue. I am totally stuck what to do now.

 

How are you installing Windows? From an ISO perhaps? If so, maybe the ISO is bad, try redownloading a fresh copy?

 

Wow - really looks like a bug then. But other than the search not working, it's seemingly a non-destructive problem?

 

Yeah I have formatted from 2 official copies on usb and disc. I have been reading on other forums that other people are having the same issue too. Maybe it is not hardware and just a bug that is not affecting everyone.

 

Hi Guys, New member here,...

After quite an extensive search, I finally found this thread, and had to join the forum to report this issue. The problems described above, are the same issues that I am having with my laptop.

Just discovered this issue a couple of hours ago, and just want you to know, that have the same identical issues. There are multiple keys where this issue is a problem


This was not happening in the previous build of Win10 10240, but is now, in build 10586.3

Otherwise, the computer is running fine. It's a Toshiba C55t A 5102. I have had windows 10 installed since the 1st of August, with no issues with the regedit function, but i do now !!

I am not real computer savvy, or technical but i just wanted to report that you are not the only one with this issue, and I just wanted to report it, and let you know.

I noticed this problem when I was looking for remnants of Superantispyware in the registry. It had found one or two remnants, and then the registry crashed and restarted, with the same problem occurring over again.

If there is any info that you may need , I will be happy to give it, but once again, I am not that savvy !

 

Never got that problem. Have only one question: When you clean install the build do you choose at the end Customize settings? If so, are you disabling all switches?

 

Also check if there is a common software you are running for Windows housekeeping. For example CCleaner or similar. There are a few known issues with CCleaner as reported on the web if used aggressively to clean registry and PC files.

 

I do use CCleaner because it is mostly non aggressive. I get the regedit error before installing anything, including drivers.

 

When I clean install I do disable a few privacy settings but nothing in there should corrupt the registry, if it did it still points to a bug.

 

It seems more and more people are seeing it but not everyone, strange. I would rather it be a bug than hardware related which it seems to be so I have freshly formatted and reluctantly ignoring it until MS fixes it. I reported it in the Windows feedback tool so the more people that do the same, the better.

 

hi
may i know how did you fix it ?
because it marked solved , i have still this problem
thanks