Possibly a windows update error preventing boot up to desktop?

Page 1 of 2 12 LastLast

  1. Posts : 12
    Windows 10 64-bit
       #1

    Possibly a windows update error preventing boot up to desktop?


    I read the sticky on what to do before posting but unfortunately I can't get to my desktop to get the info. I figured I would just list my specs.

    Gigabyte Z77-DS3H
    Intel core i3 2120
    Nvidia GTX 560 Ti
    8 GB RAM
    Crucial 128 GB SSD (drive with the OS files)
    Seagate 2 TB Hard Drive
    Windows 10 64-bit

    I was using my computer like normal, I walked out of the room for about an hour and when I walk back in I see the automatic repair and diagnosing screens loop on my computer. I had not installed any new drivers for any of my devices recently either, the only thing I could think of is a windows automatic update. I tried most of the alternative startup methods from the options. Tried system restore, it kept giving me errors. Tried to refresh it and it gave me an error. I am getting the error message of Automatic Repair could not repair your computer and it displays the log file "E:\WINDOWS\System32\LogFiles\Srt\SrtTrail.txt"
    I found this odd because my E: drive does not contain my OS files, my C: drive does. I go to the command prompt from the recovery console and open up the log file srttrail.txt it shows one error (0x490) a recent driver installation or upgrade may be preventing the system from starting. I open up bcdedit and it shows that none of my defaults are to my C: drive like they should be. Again odd, I change them to the C: drive, close out of the command prompt and restart again. Still doesn't work. I check in my bios, my C: drive is no longer listed in the boot priority options but is listed in the section where I can manually select a drive to boot from. Again, very odd. What should I do?
      My Computer


  2. Posts : 4,734
    Windows 11 Pro 64 Bit 22H2
       #2

    In the RE (Recovery Environment) Windows will many times not be on the C: drive like it is in Windows.
    There are at least one maybe two Hidden Partitions that are labeled System that have no drive letter in Windows, these partitions hold the Boot information.
    In the RE they may be given a Drive letter and push the OS partition to a lower drive letter (ie) E:
    In the RE Command Prompt type the drive letter E: and press enter. Type DIR and press enter, to confirm that there is a Windows directory in the E: drive. Now type chkdsk /R and press enter. Now type a Y for Yes and restart the computer. Check Disk should run at next bootup. It will take a while. Try starting normally. If that fails back in the RE run the BCEdit commands from the E: drive.
      My Computer


  3. Posts : 12
    Windows 10 64-bit
    Thread Starter
       #3

    spunk said:
    In the RE (Recovery Environment) Windows will many times not be on the C: drive like it is in Windows.
    There are at least one maybe two Hidden Partitions that are labeled System that have no drive letter in Windows, these partitions hold the Boot information.
    In the RE they may be given a Drive letter and push the OS partition to a lower drive letter (ie) E:
    In the RE Command Prompt type the drive letter E: and press enter. Type DIR and press enter, to confirm that there is a Windows directory in the E: drive. Now type chkdsk /R and press enter. Now type a Y for Yes and restart the computer. Check Disk should run at next bootup. It will take a while. Try starting normally. If that fails back in the RE run the BCEdit commands from the E: drive.
    Alrighty, it is running the check disk now. I'll keep you posted
      My Computer


  4. Posts : 12
    Windows 10 64-bit
    Thread Starter
       #4

    Alright, the e: drive listed in RE contains the windows files. I ran bcdedit and the bootmgr section has the d: partition is default. Should that be changed to e:?

    EDIT: I tried that method and it didnt fix the problem.
    Last edited by Onehotelfoxtrot; 17 Nov 2016 at 22:24.
      My Computer


  5. Posts : 12
    Windows 10 64-bit
    Thread Starter
       #5

    Also, it ran the disk check and found no errors.
      My Computer


  6. Posts : 4,734
    Windows 11 Pro 64 Bit 22H2
       #6

    At the E:\Prompt type bootrec /rebuildbcd and press enter restart computer
      My Computer


  7. Posts : 12
    Windows 10 64-bit
    Thread Starter
       #7

    spunk said:
    At the E:\Prompt type bootrec /rebuildbcd and press enter restart computer
    Did that, still nothing.
      My Computer


  8. Posts : 12
    Windows 10 64-bit
    Thread Starter
       #8

    Something that I thought was odd I figured I would add. Prior to this I was unable to access my bios/uefi screen and since this happened I am now able to. Don't know if that adds any pertinent info to the situation.
      My Computer


  9. Posts : 12
    Windows 10 64-bit
    Thread Starter
       #9

    I've also tried reverting back to old registry files and it hasn't helped.
      My Computer


  10. Posts : 12
    Windows 10 64-bit
    Thread Starter
       #10

    Go ahead and close this. I went ahead and reinstalled windows.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:30.
Find Us




Windows 10 Forums