Startup Repair Infinite Loop Recovery

I have a lite version of windows 10, that I use for my work, working in a virtual machine under ubuntu.
After a system update of virtualbox, windows wasn't able to start entering in an infinite loop of automatic repair.
Following this guide, after 10 min. of timework I resolved.
Thank you very mutch!

Fabio

I am trying to do this but in step 13 the last line say
DIR 0 bytes of free space. The other numbers are almost the same in the instructions. I can still do this if my hard drives has no free space? Do you know how I can free disc space to complete the procedure?
Thanks

Hi Eli21,

ITS NOT saying not enough Disk space BUT NOTHING in the hive if its showing 0 , which it needs to complete the repair, hence the rider you will need to do it a different way
Have you any re-install disks??. if so follow this tutorial
Repair Install - Windows 7 Help Forums

Roy

Just like to thank Peter for this very good info,because I had completely lost Windows.
I persevered refusing to fresh instal Windows,and after 50 or maybe more restarting I actually was able to get into cmd prompt again,and so THANKS you are doing great work Peter.

I've registered on the forum just to say thanks. I'm on Windows 10 Pro, got the infinite startup loop after windows update (I think). Spent hours trying google searched answers, stumbled on this thread, follow the steps, and it worked! Much appreciated!

I am yet another happy customer. This tutorial was perfect and fixed my problem without a hitch. Thank you so much!

i already had that loop problem some time ago, then used those commands, of the front page

CD \windows\system32\config
DIR
MD mybackup
copy *.* mybackup
overwrite with A
CD RegBack
DIR
copy *.* ..
overwrite with A
exit
remove windows DVD and restart go to BIOS and select hard drive as boot device

now it happens again

when entering those commands i get this screen

X is now the new boot drive, which is new to my knowledge
I have double the amount of config files ? with .log endings
And one of those rows show 0 Bytes, so i stopped with going on entering any further commands

is this all just a mistake, and simply means nothing else than, that there is an already once created backup that i can use to restore

sorry for the english, german native language

someone in another forum posted to copy those files, in cmd command window, from the original windows DVD to the hard drive that windows is installed on and everyone was happy with the result, but i am not sure if i should do that, because i am confused as to why the boot drive is called X, why are there a double amount of config files with .log endings, and therefore how to behave in my case

C:\windows\system32\config\regback\system c:\windows\system32\config\system
C:\windows\system32\config\regback\software c:\windows\system32\config\software
C:\windows\system32\config\regback\security c:\windows\system32\config\security
C:\windows\system32\config\regback\sam c:\windows\system32\config\sam
C:\windows\system32\config\regback\default c:\windows\system32\config\default