Startup Repair Infinite Loop Recovery

It appeared System recovery but i can't move my mouse and i can't do anything

I used the tutorial and all was going well, but during copying the files at the "copy *.* mybackup" stage it seems to have got stuck at "software" and isn't producing the system file copy, nor is it displaying any error message and I can't type anything. Is it just taking a really long time, or could this be another issue entirely?

I woke up this morning to find my computer stuck in the automatic repair loop. I tried system restore. Didn't work. Tried to fix the startup options. Nada. Tried to fix the boot. Still nothing. Came across this post and in desperation, tried it, even though it was originally written for Win 7. I really didn't want to have to reinstall windows for the second time this year.

It worked.

I have never been happier to see my log on screen. Thank you, thank you, thank you! I joined this forum just to say that.

Dear Dzomlija,

(same as previous poster): joined this forum just to say THANKS! Your instructions worked perfectly on my Windows 7 Professional x64 laptop. Nothing else I tried before worked. I was about to finally succumb to Microsoft and install Windows 10 and reinstall my gazillions of software tools, but your instructions helped me to keep my beloved Win7 laptop alive for some time. You saved me a LOT of time and agony .

Thank you for taking the time to post these instructions (back in 2011). Very much appreciated.

Kind regards,
Porl

lunathecomputer said:

I used the tutorial and all was going well, but during copying the files at the "copy *.* mybackup" stage it seems to have got stuck at "software" and isn't producing the system file copy, nor is it displaying any error message and I can't type anything. Is it just taking a really long time, or could this be another issue entirely?

Lunathecomputer: make sure your disk has enough space left for the copy operation. If that is not the problem, run chkdsk on the command line to see if the disk is OK. (do chkdsk \? to see the command options).

Beyond that, I have no idea.

-Porl

Thanks for the article.
When I try to open the boot drive ( C: ) it says "drive not ready". (step 8)
I am sure this is the boot drive as I unplugged all other drives first. In chkdsk it shows up as 0bytes, but as this machine is a dual boot, when I check the drive in MacOS, it shows that the drive is not 0bytes.

Just like Caeleinn, above, I just joined this forum to say thanks for bringing my computer back from the death start loop. I first had to figure out why I couldn't do anything to even affect the loop screen. Finally realized I had to switch ports to plug in my keyboard; (computer probably couldn't load the drivers for the rear, add-on usb device which added ports.) After that I tried all options on the screen and several I read on line. Not til this blog did I find the solution. And I also am running Win10, but the process worked smoothly. I probably screwed up my computer trying to delete an old joystick driver which wasn't loading properly. This blog, published by Dzomlija certainly saved me tons of grief. I don't know why or how it worked, but it sure did! Bless you folks!!

Does this method works with Windows 10?

This method works easily with Windows 10. In fact it is simpler than in 7 as one of the alternatives presented on the Blue Screen of Death ( which is reporting that you are having start problems...and therewith traps you in the infinite loop ) is the option of bringing up the command prompt ( dos prompt ). So you can start from that point.
Obviously you must be judicious, as with any computer command, and type all commands exactly as instructed, noting periods and spaces precisely. That done, then magic occurs and your computer starts working!!
Good luck!

Thanks for this tutorial, but could this computer be too late for for the recovery too resolve the issue? That is, after I got to step 8 and found regback directory on the system drive, the dates of the regback files were ALL more up to date than the date I noticed the repair error message. I would suspect in my case, the hives problem has now been copied to the backup files?