Laptop not loading Windows after last night's updates

kickling on 12/03/2015 - 17:28

Anyone else have this problem? I let windows 8.1 do it's auto updates and when i turn my laptop on it shows a black screen.

Initially i could move my mouse, and access the task manager (ctrl alt del). I went to boot into safe mode (hold shift and click restart) and went to select my option to boot into safe mode (option 4).

Now it doesn't do anything at all. Power on shows Asus logo very briefly, then that's it. No other activity. I can confirm the keyboard works because the capslock button light functions. The screen is still black, and i can move the mouse BUT cannot access task mgr.

I can't even access Bios, i think because of uefi. Tried holding /pressing F2 whilst powering, and also tried Del whilst powering… No results.

Help!?
Asus ux32vd 4002

Computing

Comments

    • kickling on 12/03/2015 - 19:21

      Thanks, but my laptop doesn't even want to boot into safe mode. Black screen even in safe mode!

      I am going to swap back to my old hard drive with working windows, then copy over some key Windows files back to my ideal hard drive (SSD) via external sata cables.

  • Riczter on 12/03/2015 - 22:43

    The way the UEFI BIOS handles user access to safe mode (or rather doesn't) is really annoying.. I hope they change it for Windows 10.

    I mean usually the only way to access safe mode is by booting into windows.. who was the genius who thought that one up!? IF I COULD BOOT INTO WINDOWS I WOULDN'T NEED SAFE MODE WOULD I!!!

    F8 never bloody works and most people don't have a windows install disc to access the repair options to get into CMD. Very frustrating.

    /rant

    • Dennis3003 on 13/03/2015 - 07:44

      Thank god Lenovo thought that through. Press enter during UEFI flash screen gives more boot options then I can select Windows Recovery Environment and then have an option for safe mode.

  • kickling on 12/03/2015 - 23:15

    Does anyone know what key files I should copy over? I have tried copying as many of the driver files it allowed me already… I'm so not used to non-XP windows!

  • Manh on 13/03/2015 - 01:27

    I recently read an article about SSD failing often. I hope Windows Update didn't kill your SSD.

    If you do have your Windows 8 installation Disc/USB, you can try to do an automatic repair as shown in the 2nd half of this video:
    https://www.youtube.com/watch?v=-s9Jd1miS_8

  • scrimshaw on 13/03/2015 - 02:37

    Appears to be an Nvidia graphics card issue. Happened to my desktop as well with nvidia card. You'll have to go into Safe Mode and remove the driver, then reinstall it again in normal mode.

    An explanation here:

    Basically, windows update attempts to install the graphics driver but it is in use so it puts it into a queue to be installed on the next reboot (not sleep). In the mean time, before you actually reboot or power cycle your machine you use the vendors update program that does not require a reboot. All is well until, some time later you reboot and windows sees that it has a update to install on the reboot and does it. Now you have a mixed build and your graphics card will not work correctly, Also, windows makes a backup copy of the drivers and puts them into its driver store for you and keeps putting it back on your system if the driver is deleted.

  • kickling on 13/03/2015 - 09:29

    Thanks… But my problem is safe mode doesn't want to display. The drivers must be so corrupted.

    I've got advice from whirlpool to remove battery. I've also copied over some fresh system32 dll files. Fingers crossed.

    • scrimshaw on 13/03/2015 - 10:37

      I'm currently using /SFC scannow to see if Windows can automatically detect inconsistencies in system files.

      My PC does not have UEFI since it's a Core 2 Duo, is there any way I can do a repair install of Windows using command line?

      The PC refuses to run Explorer.exe so I have to do everything using cmd.exe

      edit:

      The plot thickens. I can't even do a system restore because it's apparently disabled. I cannot refresh Windows 8 either from the CD because the drive is reported as 'locked'. WTH microsoft? Test your patches before you roll them out…

      • kickling on 13/03/2015 - 14:08

        So, I found out that my recovery is also not functioning (i.e. I cannot do a refresh).

        In command as administrator, when you type in "reagentc /info" it will probably show "Windows RE status" as DISABLED.

        IF you have a valid entry next to "Windows RE location" you can try typing "reagentc /enable" to see if it works/links it back.

        However, if you're like me, and I had a blank Windows RE location, you need to set the RE location manually.

        I followed this guy, look at about halfway down the page : http://www.eightforums.com/installation-setup/54058-windows-…

        1.) Find the RE partition. If you've updated to Windows 8.1 it would have created a 450mb partition (with no drive letter). Type DISKPART and then "select disk 0".

        2.) Type "list partition" to make sure you have the 450mb partition, and it is called RECOVERY (in his guide, he has Partition 7 but is called OEM. His guide is all about renaming, but it gives useful insight)

        3.) After you find your 450mb and is called RECOVERY (if not, then follow his guide) you need to set the RE Location "reagentc /setreimage /path \?\GLOBALROOT\device\harddisk0\partitionX\Recovery\WindowsRE"

        partitionX is your partition number (e.g. partition7)

        4.) After that is successful, you can enable the RE status "reagentc /enable"

        5.) Check that it worked "reagentc /info"

        HOWEVER after I got all this working, I tried to run the refresh, and it got past the error "could not find the recovery environment" … but now says "there was a problem refreshing your pc".

        So at least I got halfway there.

        My latest update posted below: I uninstalled all this week's updates and voila, back to norm.

        *In your case, maybe this will help? http://www.boyans.net/RepairWindows/The_drive_where_Windows_…

      • Dennis3003 on 13/03/2015 - 16:43

        Try a automatic repair by booting into WinRE

  • freemoneyhunter on 13/03/2015 - 10:17

    It was a weird update, 28 updates and computer restarted twice. That was for Windows 7

  • goldfox on 13/03/2015 - 11:38

    Now that F8 doesn't really exist anymore, there's another handy trick to make your way back into the boot menu if you can't reach Windows (8 and up) that doesn't need install media etc.

    Boot up the PC and wait for the Windows loading spinner. When that's there, switch it off again (pull the plug/hold power button for 4 seconds). Repeat again - boot, shut down. On the third boot, Windows' automatic recovery should kick in, I believe it'll say 'Preparing Automatic Repair' on screen. It's probably worth letting that run actually to see if it can fix things. But one (or two, going from memory here) more reboot cycles and you should get a 'Please Wait' on screen. Then, you'll get a nice panic prompt which will let you straight in to the boot options. See advanced repair -> Troubleshoot -> Advanced options -> Startup Settings -> Restart. Then you can either pick safe mode, or if the issue is indeed just flaky drivers, you may want to try the low-resolution mode first. That will boot with a bare minimum graphics driver that should let you in and uninstall the bad ones.

    A useful first step for potentially bad system files is these two commands (in order):
    dism /online /cleanup-image /restorehealth
    sfc /scannow

    That will first repair the servicing store (repairing the repair source you could say), and then repair windows itself.

    • kickling on 13/03/2015 - 12:24

      Thanks paul. Trying the Dism command. When i ran Sfc it came back with 3 errors… Something to do with Amd64 inf file.

      I might uninstall all the updates from the night of disaster too.

  • kickling on 13/03/2015 - 11:50

    Latest update: using my old hdd with original windows 8.1 i could restart my laptop into Uefi settings (so dumb that you have to have a working copy of windows 8.1 to access this option to get into your bios).

    Anyway, luckily when i installed my ssd i created a boot/repair USB. So in my uefi bios i was able to boot from the usb.

    From there, it opened the windows repair program and i got to the command prompt option. I attached my ssd via external sata cable, and I then was able to use the bootsect command on it (Bootsect.exe /nt60 f: /force) to at least make the drive boot.

    I shut down, swapped out old hdd for ssd, reboot again from usb repair. Then i could go into troubleshooting and do the advanced -> repair boot option.

    Shut down again, but this time took out the usb repair stick. It loads up into my login, but again black screen BUT at least i can Ctrl Alt Del into task Mgr AND i can open file explorer.

    Currently running SFC /SCANNOW to try repair things. Then I'm going to try rollback nvidia drivers.

    Bloody Microsoft…

  • kickling on 13/03/2015 - 12:25

    Rolling back display drivers did nothing…

  • kickling on 13/03/2015 - 13:51
    +1

    Omg, uninstalling All windows updates and a few random Office 2007 updates from this weeks auto updates has restored back to norm.

    F.U. Microsoft for wasting my time. Seriously.

    And seriously, thankyou everyone who has helped give me ideas. OzB forever.

    • scrimshaw on 13/03/2015 - 16:10

      I found the culprit of my issues to be StartisBack. Removing it allowed the computer to fully load explorer.exe.

      Didn't have to do any patch rollbacks.

      • kickling on 13/03/2015 - 16:21

        Yeah, i did read that suggestion from someone on my post on whirlpool. Did you re-install it successfully? Or are you back to using the crappy 8.1 power/charms menu?

        • Dennis3003 on 13/03/2015 - 16:45

          Its not that bad, yes it can be annoying when they randomly pop up because of your mouse, but when you understand it it isn't so bad…

Login or Join to leave a comment
Login Join