F5F Stay Refreshed Software Operating Systems Issues starting Windows 10

Issues starting Windows 10

Issues starting Windows 10

Pages (2): 1 2 Next
B
barangaog
Member
50
08-27-2016, 02:29 PM
#1
I just upgraded my computer and moved everything into a new case. I installed a fresh power supply and added a crucial SSD. I transferred important files from the old hard drive to the SSD. Then I used Windows Media Creation Tool to install the operating system onto a USB drive, which I mounted on the SSD. Once Windows was running, I began installing drivers and other updates. I also performed a disk cleanup by using the admin command prompt, DiskPart, and the "clean" command. After that, I turned off the computer overnight and came back the next morning. That’s when issues started. When I restarted, the screen showed a black message: “Intel UNDI, PXE-2.0 (build 083) Copyright © 1997-2000 Intel Corporation for Atheros PCIE Ethernet Controller v2.1.0.9(08/12/11) Check cable connection! PXE-M0F: Exiting Intel PXE ROM ERROR: No boot disk has been detected or the disk has failed.” I spent a few hours trying to figure it out. I verified the BIOS, and both the HDD and SSD were listed in their SATA slots. Yet the USB drive remained plugged in but wasn’t being recognized as a boot device, even though it worked last night. What caused this? Why did the computer start up before but not now? Why isn’t the USB drive listed as a bootable option? Should I need to purchase a new Windows installation?
B
barangaog
08-27-2016, 02:29 PM #1

I just upgraded my computer and moved everything into a new case. I installed a fresh power supply and added a crucial SSD. I transferred important files from the old hard drive to the SSD. Then I used Windows Media Creation Tool to install the operating system onto a USB drive, which I mounted on the SSD. Once Windows was running, I began installing drivers and other updates. I also performed a disk cleanup by using the admin command prompt, DiskPart, and the "clean" command. After that, I turned off the computer overnight and came back the next morning. That’s when issues started. When I restarted, the screen showed a black message: “Intel UNDI, PXE-2.0 (build 083) Copyright © 1997-2000 Intel Corporation for Atheros PCIE Ethernet Controller v2.1.0.9(08/12/11) Check cable connection! PXE-M0F: Exiting Intel PXE ROM ERROR: No boot disk has been detected or the disk has failed.” I spent a few hours trying to figure it out. I verified the BIOS, and both the HDD and SSD were listed in their SATA slots. Yet the USB drive remained plugged in but wasn’t being recognized as a boot device, even though it worked last night. What caused this? Why did the computer start up before but not now? Why isn’t the USB drive listed as a bootable option? Should I need to purchase a new Windows installation?

N
179
08-31-2016, 12:46 PM
#2
Access your BIOS settings, turn off RAID configuration, and configure Intel Rapid Storage Technology. Change the boot device to the USB drive.
N
NicknameNumber
08-31-2016, 12:46 PM #2

Access your BIOS settings, turn off RAID configuration, and configure Intel Rapid Storage Technology. Change the boot device to the USB drive.

T
Tuly
Member
77
08-31-2016, 03:16 PM
#3
Consider using another PC to test the SSD connection and see if it becomes corrupted. Alternatively, perform a Windows repair using a USB drive connected to a different port.
T
Tuly
08-31-2016, 03:16 PM #3

Consider using another PC to test the SSD connection and see if it becomes corrupted. Alternatively, perform a Windows repair using a USB drive connected to a different port.

C
Chromels
Member
197
09-01-2016, 06:15 PM
#4
Your device is attempting to connect to the network.
C
Chromels
09-01-2016, 06:15 PM #4

Your device is attempting to connect to the network.

B
Brudora
Senior Member
726
09-01-2016, 10:46 PM
#5
They used the OS from another Windows 10 machine via the media recovery tool. After turning off Network Boot, only the error message appeared. Attempts to boot in AHCI, IDE, and RAID also failed. Disabling all drives except SATA 0 (SSD) and then SATA 1 (HDD) didn’t help. The BIOS DPS Self Test passed for the SSD. It seems the system didn’t start with the SSD even though a verified Windows copy was present.
B
Brudora
09-01-2016, 10:46 PM #5

They used the OS from another Windows 10 machine via the media recovery tool. After turning off Network Boot, only the error message appeared. Attempts to boot in AHCI, IDE, and RAID also failed. Disabling all drives except SATA 0 (SSD) and then SATA 1 (HDD) didn’t help. The BIOS DPS Self Test passed for the SSD. It seems the system didn’t start with the SSD even though a verified Windows copy was present.

M
MegaDisco
Senior Member
352
09-16-2016, 10:01 PM
#6
Install a Linux distro on a flash drive and start from there. Another option is to fix the master boot record, though this often results in errors if it's damaged or absent. You might also attempt to reset the SSD, then reinstall Windows.
M
MegaDisco
09-16-2016, 10:01 PM #6

Install a Linux distro on a flash drive and start from there. Another option is to fix the master boot record, though this often results in errors if it's damaged or absent. You might also attempt to reset the SSD, then reinstall Windows.

A
audi497mks
Senior Member
601
09-17-2016, 04:54 AM
#7
I created another Windows USB using the media creation tool, but my computer doesn’t detect it as a bootable drive. I tested it in several USB ports, yet it still works on other computers.
A
audi497mks
09-17-2016, 04:54 AM #7

I created another Windows USB using the media creation tool, but my computer doesn’t detect it as a bootable drive. I tested it in several USB ports, yet it still works on other computers.

M
Mrcreeper574
Junior Member
19
09-17-2016, 10:09 AM
#8
Do you have a SATA DVD drive that can be connected and used to start a Windows recovery installation? Are other USB devices functional, or would this indicate issues with your BIOS or motherboard? Would it be possible to transfer Linux onto an SSD from another computer and attempt booting there temporarily?
M
Mrcreeper574
09-17-2016, 10:09 AM #8

Do you have a SATA DVD drive that can be connected and used to start a Windows recovery installation? Are other USB devices functional, or would this indicate issues with your BIOS or motherboard? Would it be possible to transfer Linux onto an SSD from another computer and attempt booting there temporarily?

M
Matke04
Posting Freak
825
09-21-2016, 05:41 AM
#9
It seems the issue might be related to the motherboard rather than just the Linux disk. The USB ports behaving unpredictably also point toward a hardware concern.
M
Matke04
09-21-2016, 05:41 AM #9

It seems the issue might be related to the motherboard rather than just the Linux disk. The USB ports behaving unpredictably also point toward a hardware concern.

S
Sindyion
Member
203
09-21-2016, 08:15 AM
#10
Likely the internal USB hub is unstable. The BIOS shouldn’t be the issue since a local repair shop could diagnose the parts accurately and pinpoint the cause.
S
Sindyion
09-21-2016, 08:15 AM #10

Likely the internal USB hub is unstable. The BIOS shouldn’t be the issue since a local repair shop could diagnose the parts accurately and pinpoint the cause.

Pages (2): 1 2 Next