PXE-E61 Error - But Windows Boots

So I have been looking around this thing a while.
Recently a virus got to my computer, so I just decided to just reformat and just reinstall everything.
So I wanted to boot from a Windows OS disc and to no avail, I get that dreaded error, so I can no longer install my OS back onto the CD.
I have turned off the LAN, changed the order, etc.... but no luck. I really do not want to have to replace this one when it boots perfectly fine...
Any thoughts?

Similar Messages

PXE-E61 error, but my HD is OK

My laptop is a Satellite A55-S306 which, until yesterday, has given little trouble in the past. I have not added new hardware, nor have I modified the boot order.
I am getting a PXE-E61 Media Test Failure when I power up the machine. It also says that the \WINDOWS\SYSTEM32\CONFIG\SYSTEM file is missing or corrupted, but this message only appears after the PXE-E61 failure message. The problem occurred while I was out of town and the system hibernated, but it probably came awake to service an automated JungleDisk backup. When I returned, the system was powered up with the "SYSTEM file corrupted" message on the screen.
I don't remember with certainty how to get into the boot order menu, and have not been able to. I am able to get into the pre-boot setup menu using Esc, and it has lots of options, not including boot order. I have tried various F keys, including F2, F8, F10, F12, but these seem to do nothing.
In any case, I think the boot order is working, because I am able to load a CD and boot from it.
I have SeaTools on CD, and I used this to test the hard drive (long test). It passed with no errors detected, so I believe that the disk drive is available and the formatting is OK.
I also have an Acronis recovery CD, with their Disk Director and backup applications on it. Booting from this, I am able to see the C: partition on the hard drive. Using the backup application, I am able to explore the various directories and they look normal. I even commanded a full backup of the C: partition to an external USB drive, and this completed without error.
About the only thing I can think of is that there is a problem with the boot sector on the hard drive, or the Windows system files have been corrupted somehow. I have not been able to command an fsck on the drive, because I don't have that on bootable CD and haven't been able to get far enough on the HD to do so. I tried using Acronis restore to copy the old version of the SYSTEM file, but this failed with some wierd messsage.
I can restore C: with an Acronis full backup from last month (made with the Acronis bootable CD), but is there a way to avoid rolling back that far? And I'm not positive even this will solve the problem.
Suggestions would be appreciated!
Solved!
Go to Solution.

Thank you very much, anarchy_1024, for your advice -- it was most helpful. Now for the rest of the story:
I attempted to restore the entire \WINDOWS\SYSTEM32\CONFIG folder from Acronis full backup, but it insisted (correctly) that the folder was corrupted. So I went looking for a chkdsk that I could run from CD, since I could not get XP up to command it from there.
I ended up downloading and building an Ultimate Boot CD for Windows (UBCD4WIN), and ISO Recorder to allow me to burn the resulting ISO file to CD. This took a while, but gave me an XP system on CD with lots of diagnostics, including chkdsk.
Using the A43 File Management Utility to view C:, a spot check revealed no problems *except* for the \WINDOWS\SYSTEM32\CONFIG folder, which couldn't be viewed because it was corrupted. I ran chkdsk and it found several index errors and recovered 22 "orphaned" files, which appear to be the contents of the corrupted directory. Finally, I ran MemTest86, which found no errors. After all of this, I rebooted to the hard drive and it came up fine! It has been an arduous odyssey, but the bottom line is that the system is recovered (crossing my fingers when I say that), and I did not have to fall back to a 3-week-old backup state. I still have no idea what caused the folder to be corrupted, but it probably should reinforce the notion that one should run chkdsk on the system disk periodically.
One anomaly is that the PXE-E61 error is still there, but then XP boots up fine. I expect this is because my boot device order includes some device, USB or CD, before the HD, which causes the error, but then the boot sequence finds the HD and all is well. I just never noticed this error message before, since it never caused a problem.
At this point, I would recommend anyone build and keep a UBCD4WIN CD around, just in case. I will mention 2 glitches in building it:
1. Like probably most consumers, my system didn't include a Windows Install CD. BUT all the install files are on the hard drive, in C:\I386 (this is an old Compaq system). All I had to do, in the UBCD4WIN build program, was to specify "C:\" as the Windows source directory, and all went well.
2. My first build of UBCD4WIN was too big for a CD. Since I didn't have a DVD burner handy, I did another build, disabling stuff I didn't plan on using (Firefox and Spyware software, mostly), bringing down the ISO size to under 600 MB, and that worked fine. It is very easy to do consecutive builds, customizing between builds, since the builder stays up until you close it.

PXE-E61 error

I used live update3 to update my comp's bios. It said it was succesfully flashed but when it was restarted, it gave error message:
PXE-E61 Error, Media Test Failure, check cables
Exiting PXE-Rom
All cables should be fine, since I'vent opened case and computer worked fine for couple months. According to other messages in this forum, problem might be that bios cant find my bootup-hdd, which is seagate's sata in IDE third master. However, it's unclear how to fix this as originally it found that hdd just fine. And my mainboard is neo2 platinum 54G with 939 newcastle 3500+

uuuh...traditional "it-works-5-secs-after-you-complain-to-support-forum" happened ^^;;;

OSx not recognized. Invalid node estructure error but Windows 7 partition works perfectly. All tests done but still don't know what is wrong

I have an Imac Snow Leopard 10.6.3 1TB hard drive , it has a partition of 100gb for Windows 7 using Bootcamp (only for games)
The computer was kind of slow one night. The next day it was so terrible slow that I decided to restart it, but it never showed OSX again. If I try to boot into single user mode it shows Windows Boot Manager. Even booting with alt only shows Bootcamp Windows. Is like OSX dissapeared.
I tried Disk utility and it showed an "inlavid node structure" error, "Disk Utility cannot repair this disk"
I also used Diskwarrior, the test was relatively fast and showed this at the end "Disk Warrior has successfully built a new directry for the disk. The new directory cannot replace the original because of disk Malfunction. Disk Malfunction is a failure of or damage to any mechanical component of the disk or any component connected to it"
I also did a S.M.A.R.T. test from diskwarrior which turned out ok
I used Apple Hardware test, (booting with D and the Applications DVD). It goes through several things, even logic board but when it reaches "testing in progress" almost at the end it gets stucked. I have tried the simple and complete test in many different ways, with mouse, without, everything disconnected, it doesnt matter, clicking the "Stop Testing" button or using cmd+period (as instructed on screen) doesn't stop the test. The "Total Time Testing" field also stops counting. I have to force shut down with the power button every time.
But here comes the most odd part of this story. The computer now almost always boots in the Windows 7 partition which works perfectly. I can chat, use viderocamera, save, delete, listen to music, watch videos, etc.... I even enter from Windows all my MAC Archives and backuped almost the 900Gb I had with no problem (great thing to use Bootcamp, never imagined it will be this useful).
So my question is, WHATS WRONG? The hard drive? the logic board? the fan? I need to know in order to buy the replacement. I have no warranty anymore and would like to fix it myself.
Please help me understand what is going on

RESOLUTION:
I erase the drive completely following the security measure "Zero Out Data" and then reformat the drive. According to what I read, by following the zero out data procedure, the computer checks the drive and isolates possible structural errors in the disk ( don´t know if it is true) I had everything already backup through Windows as explained originally.
After I reformat the drive everything is working OK. I have done the tests again (Disk Utility and Disk Warrior) that showed the drive to be in perfect order. So probably the error was caused by lack of sufficient free space in the disk ( 30 highly fragmented GB for a 1TB computer) that made OS X incapable of handling new information and was deleting key elements (?) in short a fragmented and saturated disk. However still do not understand why most tests could not complete or showed info relating to structural damage and now the same tests are saying everything is OK...
So if anyone goes through something similar, try erasing and formatting the drive, see how it goes.
Thank you very much baltwo!

PXE E53 error, and windows 7 start up problem error

recently, i have been getting an error called PXE E53 - no boot filename recieved. is the problem the hard drive? sometimes i get "windows 7 has failed to start. a recent hardware or software change might be the cause" and i choose start up repair, but then its just a black screen. any ideas of the problems im having?

Hi
This error comes if the OS or any boot device is not found in network boot, where the system tries to boot from Network or Boot Rom. Seems that teh BIOS setting is lost. To resolve teh issue. Enter BIOS by pressing F10 or F1 and reach the Boot tab (on the top with right arrow key). In the Boot tab there should be an option related to boot device priority, Select First Boot as HDD and then save settigs by pressing F10, select Yes for confirmation.
Now PC PC will reboot and hope the windows will boot.
Checkurtech
****Click the White Kudos star to say thanks****
****Please mark Accept As Solution if it solves your problem****

Win7 can't boot in USB hard drive blue screen 7b error,but can boot when use PD8

Install Win7 64bit in a USB hard drive through some tools,when start windows the microsoft logo appear,get blue screen.
***stop:0x0000007B(0x80786B58,0xC0000034,0x00000000,0x00000000)
problem has been detected and windows has been shut down to prevent damage to your computer.If this is the first you've seen this stop error screen restart your computer .If this screen appears again.follow these steps:Check for viruses on your computer.Remove any newly hard drives or hard drive controllers.Check your hard drive to make sure it is properly.Configured and terminated.Run DCHKDSK/F to check for hard drive corrption,and then restart your computer.
Technical:
***stop:0x0000007B(0x80786B58,0xC0000034,0x00000000,0x00000000)
But when use Parallels Desktop 8 My boot camp ,the win7 can boot normally.
Any solution?
Thank you.

Hi,
If this issue is related with firmare, then it's recommend to contact the vender\manufacture, if you got any update of this issue, we'd be appreciate that you could share your experience with us.
Regards
Yolanda Zhu
TechNet Community Support

Partition is there, but Windows boot option is gone?

Hey folks, I'm having a small issue with bootcamp.
Not too long ago did I have Windows running just fine on my Mac; everything was up to date, I managed to install 7 and upgrade to 8.1 just fine. Everything was good until one evening I open my Mac up, there is a command line that states "no bootable device." I don't believe I had installed Yosemite because last time I shut the Mac it was in Windows. I found a thread from another user here, and followed LonerT's suggestions and managed to get Windows back as a boot option, but the command line still pops up with "non-system disk."
The bootcamp partition is still on my HD with everything installed, so if there's some way I could get this back to how it was without having to go through the hassle of erasing the partition and starting anew I would be greatly appreciative.
Thanks!

Whoa, LonerT!?
Certainly, here are the results of the commands:
joshuas-mbp:~ joshua$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            394.4 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data MAC TO PC               5.0 GB     disk0s4
   5:       Microsoft Basic Data BOOTCAMP                100.0 GB   disk0s5
joshuas-mbp:~ joshua$
joshuas-mbp:~ joshua$ diskutil cs list
No CoreStorage logical volume groups found
joshuas-mbp:~ joshua$
joshuas-mbp:~ joshua$ sudo gpt -vv -r show /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 977105059
      start       size index contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6
         40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640 770347720      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
770757360    1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
772026896       1520
772028416    9762816      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
781791232       2048
781793280 195311616      5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
977104896        131
977105027         32         Sec GPT table
977105059          1         Sec GPT header
joshuas-mbp:~ joshua$
joshuas-mbp:~ joshua$ sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [    409640 - 770347720] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 770757360 -    1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 772028416 -    9762816] HPFS/QNX/AUX
joshuas-mbp:~ joshua$
I thought the corestorage command was a bit odd so I looked around the web to find out what it means. It doesn't sound promising.
As for you question on "what modifications were made to get [the drive] bootable again:"
I followed these instructions you gave in that thread listed above...
Here is an example.
sudo fdisk -e /dev/disk0
Password:
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> p
Disk: /dev/disk0 geometry: 121643/255/63 [1954210120 sectors]
Offset: 0 Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [    409640 - 1452530904] HFS+
3: AB 1023 254 63 - 1023 254 63 [1452940544 -    1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [1454211072 - 499998720] HPFS/QNX/AUX
fdisk: 1> setpid 4
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
*4: 07 1023 254 63 - 1023 254 63 [1454211072 - 499998720] HPFS/QNX/AUX
Partition id ('0' to disable) [0 - FF]: [7] (? for help)
fdisk: 1> flag 4
Partition 4 marked active.
Saying the Windows is bootable may be a bit subjective; the option appeared after this example you gave, but it won't boot into Windows.

Cannot boot from Recovery CD - Error: PXE-E61: Media test failure

Recovery CD ( winXP home edtion ) can't boot the Toshiba satellite A40 Model# PSA40E-0EWDE-AR (SA40-261) Whenever I try to Boot From recovery cd I get this Error :
PXE-E61: Media test failure, check cable
PXE-M0F: Exiting Intel Boot Agent.
but when I boot from any other cd (windows ME, WIN 2K, WIN XP Pro...) everything is ok.
Any Clue? Help me please
Thanks
Mesha

Hi
It seems the drive cannot boot up from the CD recovery and switch to the LAN boot.
The PXE-E61 error message appears because the LAN cable was not connected and the notebook is not able to find a network boot source
I think you should check the recovery CD and maybe you will need a new one

PXE E61 / PXE MOF

Hi, I upgraded my K210 system to W7 and installed a 2nd 500HDD late last year and usually don't pay attention to the Windows Start screen (since I usually put the system is "sleep" mode) but when I rebooted the system a little while ago I noted a PXE E61 error message followed by a PXE MOF error message.
I went into BIOS after doing a little research on this problem and changed the system startup options to HDD, CD-ROM Drive and where appropriate, floppy disk as the 1st option, but when I restarted the system the same PXE E61 - PXE MOF error messages appeared. The HDD appear to work fine and am not sure what may be causing this problem and would appreciate H-E-L-P!
Thanks,
Bob

There is a possible sollution within this link,you can have a look
http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/1d6f3458-9156-4dc4-a701-535e959d746b...
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Error Message: PXE-E61 media test failure, check cable

Hi,
Recently when I have loaded up my laptop one of two things has happened:
1) I am taken to Windows error recovery and told that I can either launch windows boot repair or start windows normally. Both lead to a screen which says 'Status: 0xc00000e9, Info: An unexpected I/O error has occurred. It also says that 'windows has experienced a problem communicating with a device connected to your computer. This error could be caused by unplugging a removable storage device, or by faulty hardware such as a HDD or CD-ROM drive'.
2) I am greeted by a black screen with a lot of text, but one line in particular says : 'PXE-E61 Media test failure, check cable'
Having read some forums online I have checked the BIOS and the Hard Drive is being detected sometimes, but other times is 'not present'. On examining the boot order the HDD is registered as the first thing to boot.
I was hoping that some of you would be able to help me out a bit more here, because I'm a bit of a novice when it comes to repairing computers! Any advice that you can give would be appreciated.
My computer is a Toshiba Sattelite-C660D-102
Thanks !

Your hard drive is more than likely failing and will need replaced. You can also check to make sure your hard drive is properly seated and has a good connection.

PXE-E61: Media test failure, check cable Error Message

My wife’s Satellite L505 (PULU0U-03C003) with Windows 7 Home Premium has started faulting out to this message on a regular basis, at least once a day or more:
Realtek PCI Express Fast Ethernet Controller Series v1.15 (090224)
PXE-E61: Media test failure, check cable
PXE-M0F: exiting PXE ROM
No bootable device – insert boot disk and press any key
I can power down the laptop and then turn it back on again. After going through the “did not start (I think its called that) window, then computer boots successfully and everything works fine for a time. I have attached a photo of the error message.
I checked as many of the messages as I could but didn’t find anything that seemed quite the same. Any suggestions or thoughts?
Thanks - Chet
Attachments:
Error Message - Delores Toshiba Laptop (2).jpg ‏433 KB

A PXE error typically means that the Boot Priority in the Bios is set incorrectly and the computer is trying to boot from the LAN port. Make sure that the hard drive (HDD) is the first boot device and the LAN port is the last boot device.

Error message when trying to recover HD: PXE-E61 Media test failure

Hi all, new to forums, lots of good info and support here.
Got the BSOD last week. Have been trying all of the various fixes mentioned on the board, to no avail. I went back multiple pages looking for alternatives to try. After stepping away for a few days, I got farther today than I did when I was frustrated. F12, chose to boot HDD, and got the following LOOPING error message:
PXE-E61 Media test failure check cable
PXR-MDF exiting PXE rom
Which gives me hope that I may not have to replace my hard drive.
I have a satellite L455-5975, and have ordered recovery disc from acclaim ('0' option didn't work for me, which makes me wonder if Toshiba time limits that support, but that's off topic)
So it looks to me like my RealTek Ethernet Controller might be the problem? Any thoughts or suggestions? Anything I can do or should I wait for recovery disk to arrive? I worry that the recovery disk isn't going to do what I need. Do I need to replace the ethernet controller, or is this a sign of a hard drive issue? I consider myself 'fairly' tech savvy, but I've never taken a computer apart/put one together myself. It would definitely cost less for me to replace HD myself than putting it in the shop. So I'm willing to try that option if need be.
I appreciate any help/support! Reading some of the previous posts make me wonder if rather than investing more money in the satellite, if I shouldn't instead be saving up to buy a new(er) model.

Creedym...
I have a very similar problem with my mini-notebook model NB305.
I'm getting the same message and can't get past F2 or F12.
Bottom line; I ordered the recovery data from Toshiba on-line by model number ---not by type. They sent two DVDs. My unit doesn't have an optical drive.
First call to "John"---yes, you can copy the data to a thumb drive and use that.
Almost two hours of transferring --- the NB305 did not respond to the thumb drive.
Second call to "Paul". After some consultation on his part with someone else he told me that they don't make a thumbdrive (USB) recovery disk for my model, that's why I received two DVDs. ! I would have take it to a shop where they etc...
I haven't decided what to do next. Maybe purchase an external drive rather than take it to a repair shop where it will probably cost more than buying an inexpensive external drive.
t.

Error called pxe-e61 media not loaded

Greetings
Just got this mb tried to load os and I keep gettting this message which causes a windows protect error.Has anyone come across this problem?
Tanks

vcman,
Please go through the forum posting guidelines and the infamous MOAN guide... : https://forum-en.msi.com/index.php?topic=38822.0
which mobo are you talking about? ... pxe-e61 media? and then windows protection error? I see 2 as different issue. pxe-e61 is LAN boot ROM, disable Boot from LAN in your BIOS. Windows Protection Error? Are you still using Win9x?!

Satellite Pro L10: PXE-E61 - Media test failure check cable error message

I recently bought an L10 laptop without the hard drive and everytime i try to boot it with a newly installed hard drive i get this message .
PXE-E61 :MEDIA TEST FAILURE CHECK CABLE
PXE-MOF: EXITING PXE ROM
OPERATING SYSTEM NOT FOUND.
CAN SOMEONE MAKE SENSE OUT OF THIS AND EXPLAIN IT TO ME AND ALSO HOW CAN I GET RECOVERY SOFTWARE AS I DO NOT HAVE THE TOSHIBA RECOVERY CD BUT I DO HAVE THE CoA STICKER ON LAPTOP.
IM DESPERATE PLESE HELP

Hi Nash,
Your problem is quite straightforward and can be summarised as follows.
1. You bought a notebook without a hard drive and presumably installed a new hard drive.
2. You then tried to boot the system from the new hard drive.
The problem here is that there is not yet an operating system installed on the hard drive and as a result the BIOS will try to find an operating system in other places, such as your CD drive, your floppy drive (if you have one), and finally a network connection to a local LAN. If none of these are successful you will receive the error message that you reported.
The obvious solution here would be to install an operating system on your hard drive and you can choose either an original Toshiba recovery disc (obtainable from your local Authorised Service Partner) or you can opt to buy an original Microsoft XP disc in which case you will need to download and install the Toshiba utilities and drivers from the Toshiba web site. My preference would be to get a recovery CD from Toshiba since this will install a guaranteed system with all the necessary utilities and drivers.
Your BIOS will normally be set to search for an operating system on your FDD/CD-ROM, then your HDD and finally on a network lan connection. Once you obtain a recovery CD just load it into your CD-ROM and power on your notebook. The system should find it and then start the installation process. Just follow the on-screen instructions and you should have a valid operating system on your hard drive in about 20-30 minutes.
best of luck,

PXE-E61: media test failure on Portgege 3500 but can't enter the BIOS

I canot enter my BIOS menu.
I tried all the keys ( ESC, F1, F2, Delete..etc) but then i get message :" PXE-E61: media test failure, check cable
PXE-M0F:exiting PXE ROM". I tried everything but i still cannot enter the BIOS menu.

Turn the laptop On and hold ESC, then press F1 when prompted. Pressing F12 on power-up should give you a boot menu. (This is in the Users Manual)
The PXE error means its trying to boot off the Network, because it cannot find an OS on the HDD.
Test the HDD using a HDD test. The Advanced test in Hitachi DFT is good. (google is your friend)

PXE-E61 Error - But Windows Boots

Similar Messages

Maybe you are looking for