Need help! Registry Error causing endless restart loops

[Sonikku]

My computer is my life and I need back in asap! My computer has been looping for hours due to a registry error. My first effort to resolve it was to try and use the Windows Media tool I have on a USB to scan and repair it but it said it couldn't. Then I tried to rollback the latest updates with the media tool and it said it couldn't without any details.
Then I used the command prompt in the media tool to chkdsk and it found problems in the uppercase but when I tried to apply fixes it said the drive was write protected.
I then tried a system restore and it told me "to use system restore, you much specify which windows installation to restore. Restart this computer, select and operating system then select system restore".
I tried a SFC scan but ran into "windows resource protection could not perform the requested operation". I then tried to see if I could reinstall windows with the tool but it said that "windows cannot be installed to this disc. The selected disk has an MBR partition table". So I tried to install it on a ssd I had only been using to save games to and it said "we couldn't create a new partition or locate an existing one".

The computer has been running fine for a couple years with no problems. I don't know what the heck happened or how to fix it. I'm only about as tech savvy as "google this message and try googled suggestions and command prompts" so I'm out of my depth with an issue the windows media tool can't repair or fix. Any help would be appreciated.

 

[VirtualLarry]

Page 46 - The cheap SSDs thread

Page 46 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

forums.anandtech.com

 

[mikeymikec]

I'd run memtest86 on that PC and also chkdsk /f /v /r the main Windows partition.

Hold on - has something else changed? Why is it complaining about MBR? Have you done a BIOS update or something and the BIOS is attempting a UEFI boot perhaps?

 

[Captante]

First what EXACTLY were you doing when/immediately prior to the error starting? Change anything at all (even if it appears unrelated) or add/remove any software or drivers?

Second do you have any mission-critical AND not backed up data on the drive you were booting from?

If not I suggest a full-format and clean Windows re-install which isn't that difficult and should result in a much "snappier" and more stable PC.

If so however, you have to determine if you have corrupted data which is usually fixable or a hardware failure which usually isn't. (the complication here is that corrupted data CAN be caused by an impending hardware failure like a failing drive)


EDIT: And I know this doesn't help a whole lot right now but weird/random crap like this is why I go to the trouble of continuing upkeep on my old FX-8350 backup PC.

Yeah it's relatively slow but it's really nice knowing all I need to do is power it on and I'm right back online even if my primary catches fire!

 

[Iron Woode]

assuming the drive is fine, I would do a repair install.

 

[Torn Mind]

I once saved my Windows 2000 install by copy and pasting a line from a registry right after an clean, new install, copied a line into the borked registry, and it did save the day for myself.

Probably can't do that now.

 

[Captante]

assuming the drive is fine, I would do a repair install.

I haven't had great luck with repair-installs actually fixing anything.

IME at least half the time all that happens is you end up exactly where you were when you started but with an hour of your time wasted.

 

[jmagg]

I'd run a Linux Live CD/USB to try to pull off important files, then a System Restore attempt, then a repair install.

 

[Captante]

Been a while since I used Hirens (or similar) repair utility.... saved my bacon MANY times back in the day when this kind of nonsense was a lot more common. (as was FSB overclocking not coincidently!)

 

[Sonikku]

Windows repair neither works nor can booting from a windows 10 flash even describe the nature of the issue or why it can't fix it. Tried booting from Hirens and I got to the registry repair tool but says I need to buy the full version to do that... I tried to chkdsk but it says it's write protected and can't do anything.


I did right click the drive within the hiren's windows OS and clicked check the disk for errors but then windows pops up "Windows found errors on this drive that need to be repaired. Close this dialog box , and then repair this drive." But after closing the dialog box there is no option to repair. Hmm.

 

[Captante]

Been a long time.... I believe you need to run the "repair" manually at a command-prompt.

 

[Captante]

 

[RLGL]

Save time and effort, do a fresh install, and be done with it.

 

[Captante]

Save time and effort, do a fresh install, and be done with it.

Something to be said for this method!