Windows 10: Boot Failure tp 9879

I just installed this upgrade. and found that at the end when it did a reboot that the screen ended with a flashing cursor in the upper left of the screen. I waited for some time and finally did a reboot and held the F12 key and then moved down to boot from the hard drive. It worked and have since been doing it.
Has this happened to anyone else? not sure how I will resolve it for future. had thought that the next update may fix it. I am running 8.1 Pro then did the update to 9841 then to 9860 and then today did 9879.
Larry

:)

 

How to: 10 Tips before installing the latest Windows 10

Successfully updated from 9860 to 9879 on 12/01/14. Don't know why it worked this time, since Win10 has not been booted since the failure on 11/25/14.

BTW, after the failure, it automatically reverted back to 9860.

 

Can't install windows 10 insider preview

When i upgraded from windows 8.1 pro x64,
the same thing happened (BOOT LOOP)

I tried:

-Updating from Windows 8.1 Pro x64 (9879) TO 10 Technical Preview (9926):
WORKED

-Updating from Windows 10 TP (9926) TO 10 Insider Preview (10049, 10074, 10136, and 10147):
BOOT LOOP (after first restart while installing)

-Updating from Windows 8.1 Pro x64 (9879)
TO Windows 10 IP (10147): BOOT LOOP (after first restart while installing)

-Fresh install Windows 10 IP (10049 and 10147) by making a bootable SD Card: BOOT LOOP (after first restart while installing)

-Fresh install Windows 10 IP (10147) INSIDE VIRTUALBOX IN LINUX MINT 17.2 MATE: Enters windows setup wizard, reaches "Please Wait" (after selecting Express
settings) and, pop! RESTARTING, again again again and again...

 

Wait, you were running 8.1 Pro, then you updated to Windows 10 Enterprise 9841, 9860, 9879 through updates ?

Why not clean install 9879 ?

Please explain exactly what you did, Why would you wipe out your 8.1 Pro ?

So now you`re running Windows 10 Enterprise Build 9879 ?

 

this is a spare machine I picked up. So I had 8 pro that I got way back for 39 dollars when testing 8. so I installed it updated to 8.1 pro. then I had the idea to upgrade it. worked so far except for the problem in booting up.
Larry

 

My upgrade to 9879 initially went well. It went through numerous reboots & setting up procedures before finishing with something that resembled exactly what I had before, apart from the Windows.old directory.

I checked for further upgrades & there was just one marked as important which I installed; on completion prompted me that reboot was required being scheduled for the next day.

I duly switched on the PC the next day & all was well but was again reminded that a reboot was required. The PC was rebooted & all appeared to go well with the usual blue Windows 'flag' & circulating dots but the screen then went completely black with virtually no HD activity whatsoever. I waited what seemed to be an age with still no activity, or indication as to what might be happening. The PC was left for several more minutes before CTRL, ALT. DEL was pressed with no response. I rebooted the PC & the same process encountered yet again.

By this time I was beginning to think that something had gone disastrously wrong with the upgrade & reverted back to my Windows 7 build to search for any clues & decided to download the new ISO build with the prospect of doing a re-install. Time prevented me from completing the download & decided to reboot into Windows 10T 9879 just one more time & after several minutes on the black screen, it suddenly burst into life.

Thankfully, all is now OK but lack of information during the reboot when the screen went black is just not good!

 

This is why I would make the DVD or flash installer so there is easy independent access to Startup Repair and other Advanced Boot options. It's also a better install, worth comparing to see the difference.

ESD to ISO - Create Bootable ISO from Windows 10 ESD File

 

You need to check the Bios and make sure the correct boot device is listed first in Boot Priority.

Some folks have seen some strange activity regarding hard drives and another drive or device may have been placed in front of the correct boot device.