Windows 10 Corrupt registry

dmoe33

Reputable
May 18, 2016
88
0
4,630
So ive searched and tried multiple different fixes and reinstalls and none of which worked and im at a loss of what to do. Ive had a plethora of issues with this pc to which I have followed the breadcrumb trail to find that apparently I have some corrupt registries that I have no idea how to locate or fix. This is causing (I assume) drivers not being installed properly, certain applications not launching (such as games) and windows unable to update.

Ive tried a clean reinstall of windows to which im hesitant to do again as there is a high chance this laptop will brick itself or forever loop trying to install windows which takes too much time that I cant spend without a working pc (schoolwork, etc) or if it does work it still doesnt fix the issue. Im at a loss of what to do.
 
Solution
The registry shouldn't persist beyond a clean install. If you've already done this, you should be looking elsewhere. Please try running the following and report back on what it shows:

Hard Disk:
1. Open Command Prompt as Administrator, and type: CHKDSK /scan
If it requests being allowed to do this after a restart, do so. Note, this can take quite some time. I'd suggest running it overnight or something similar.

Windows' Integrity:
1. Open command prompt as Administrator and type: SFC /verifyonly

But yea, your registries should NOT be causing this issue if you do a clean install, and the odds of you doing something that screwed them up twice are fairly low.
 


Appreciate the quick response. I just assumed as it seemed to be the root of all the other issues I am having. Ran the chkdsk which finished surprisingly quick and found no errors, where the issue comes is the SFC command which ive tried sfc /scannow and it comes up with the same error: "Windows Resource Protection could not start the repair service"

On a side note what would be causing the reinstall failure? Am I missing something obvious?
 


Are you formatting the drive and deleting all its partitions (WARNING: BACK UP DATA FIRST.)? I would think that would prevent any major issues from stopping windows, if we are able to assume that your hard disk is actually in good health. You may also wish to scan it using <brand> hard disk utilities (they all make something for this purpose) and see if that reports back anything that CHKDSK didn't find.

Basically, when you're getting these sort of OS failures, the only culprit I've yet known in my 5 years of working as a technician (retail, admittedly, but still, I've seen things) is that either the HDD is failing or the installation was botched. Motherboard failures are... rather rare, to say the least, and expensive, so you're best to make a major effort at removing those two as points of failure.

Worst case scenario, go to a generic retailer with a good return policy, buy an internal drive, see if it works, and then return it in either case to make an appropriate decision thereafter.
 
Solution