Windows 8 is stuck in an automatic repair loop

Anonymous
2012-10-26T21:04:03+00:00

My windows 8 get in a automatic repair loop and it couldn't repair it. And than it says log file d:\windows\system32\logfiles\srt\srttrail.txt

What to do?

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2012-10-29T14:14:32+00:00

do a selective boot up with bios

get cmd to open and check

bootrec /fixMBR

bootrec /Fixboot

bootrec /rebuildBCD

and also

chkdsk /r c:

chkdsk /r d:

chkdsk /r e:

chkdsk /r f:

then let repair go thowe again and should be stoped

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2014-12-31T16:33:06+00:00

Hello Coonut,

Thank you for your reply,

I would suggest you to login to any other computer and create a Windows 8 installation disk. Using that disk you can perform the troubleshooting methods given below.

Refer the link to create the installation disk:

How to create installation media for a PC refresh or reset:

http://windows.microsoft.com/en-us/windows-8/create-reset-refresh-media

Hope the information helps.

Please reply with the results, in order to help you fix the issue.

Wish u a Happy New Year!

Thank you

Was this answer helpful?

70+ people found this answer helpful.
0 comments No comments

280 additional answers

Sort by: Oldest
  1. Anonymous
    2013-12-11T04:10:50+00:00

               Can you tell me how to do it? :)

    Try a web search

    http://www.eightforums.com/tutorials/4935-startup-options-menu-boot-windows-8-a.html

    (BING search for

        boot your recoverable media to see the Advanced Options

    )

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-12-11T07:31:37+00:00

    Your help is much appreciated.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-12-17T16:58:15+00:00

    My windows 8 get in a automatic repair loop and it couldn't repair it. And than it says log file d:\windows\system32\logfiles\srt\srttrail.txt

    What to do?

    ok I have also been annoyed with this problem and tried the bcdedit commands, which failed at first saying that it could not load the bcdedit file.  I read somewhere that was because of USB and I was booting win 8 from USB.  I then used command prompt in the repair options built into win 8.1.  Completed the bcdedit commands sucessfully.   But for me and many others it did not remove my repair loop and I could not still get into safe mode.  Until I noticed in the advanced options that there is early mal-ware protection.  So I disabled that assuming this could cause boot issues (my desperate attempt).  On the next boot and to my surprise it booted.  I then shut down the machine and started it up again and it booted normally again without doing anything else. I hope this will help the others that are having issues still, after the bcdedit commands.  I also then re-enabled the recovery with 'bcdedit /set recoveryenabled YES'.  This was successfull and there is still no recovery loop.

    To breakdown what I did:

    1.  'bcdedit /set recoveryenabled NO' in the command prompt.  (This didnt work and may not be needed).

    2.  Wait for the machine to boot into the 'Automatic repair couldn't repair your PC' error message.

    3.  Click the 'Advanced Options' button

    4.  Click the 'Troubleshoot' button

    5.  Click the 'Advanced options' button

    6.  Click the 'Startup Settings' button

    7.  Wait for the system to reboot into the 'Startup Settings' menu (is the same menu for safe mode)

    8.  Select the 'Disable early launch anti-malware protection' option. (Press '8')

    9.  If this worked for you, you should now boot into windows.

    1. Now you can shutdown your system and it should hopefully work first time the next time you start the system.

    Recently after getting the system to work again and completed an update that required a restart, it happened again.  The same procedure fixed it a second time.

    Please leave comments to state whether this worked or didnt please.

    Thank-You.

    Was this answer helpful?

    0 comments No comments