[Solved] Fix PXE-E53 No Boot Filename Received Error

Wednesday, 18 February 2015

[Solved] Fix PXE-E53 No Boot Filename Received Error

Posted by Rahul Gupta
Recently my friend's computer stopped working suddenly and showed an error PXE-E53: No boot filename received on his computer screen. My friend was not having any type of technical skills so he asked me to solve this problem on my own or contact any professional technician. It was a little bit difficult task for me because this error was new for me. But before contacting to any professional I tried to search for this bug on my own. And finally at the end I was able to fix it just because of Internet.
I searched for all the possible ways that can cause this error or bug and then started applying them one by one and then one of them worked for me. So I thought to write about this error so that people are easily able to find its solution at a single place. 

Let me make you sure one thing that it's a very difficult task to tell that what's the main reason of this error. There can be several type of issues that can make this error to arise. But in this guide I have covered almost all the errors and their solution.

Why I Am Seeing PXE-E53 No Boot Filename Received Error?

If you are a little bit expert in technical skills then you can answer it very easily. The reason is simple. your PC or Laptop was unable to find any boot device so it started showing this error no boot filename received. As there was no boot device so it stuck with last option that is PXE server as you are not using it. 

How To Fix PXE-E53 No Boot Filename Received Error

As I said above that we can't exactly tell what's the main reason behind this error. We will have to check all the possible issues one by one that can cause this problem to occur. And don't think that your hard drive is crashed and your whole data will be lost. There can be dust in your hard drive which can force this error to occur. 

1. Check Your Hard Drive
In most of the cases you will be able to find the solution of this error in your hard drive only. Sometime due to dust, your hard drive stops working then your computer doesn't get any boot device. Due to it monitor shows this error. 

First of all open your CPU and check whether your hard drive is working or dead. If it's dead then sorry to say but this was the problem. If it's not dead then now remove your hard drive and connect it to another computer and if it's showing hard drive in that computer then there should be dust in your hard drive. Remove all the dust and start diagnosis test. If it will be successful then your data is not lost, it's safe.

2. Check Boot Settings
Sometime your boot drive option can be changed. Go to your boot menu by pressing F1 or F8 or ESC depending on your manufacturer and then check whether your first boot device is hard drive or not. If its' not then change the order. Remember first boot device is hard drive. Say first boot is now CD drive then change it to hard drive otherwise you will need a disk in your CD drive to take boot from CD drive.

3. Check All Connections
If there will be any loose connection then fix it tightly otherwise your hardware devices will not work properly. Check all the connection between your hard drive and mother board and make ensure that there is not any short circuit. It is recommend to check all the connections by using new cables.

4. Look For Dust
Search for a blower and then clean the dust wherever your see such as mother board, hard drive etc.

5. Check Mother Board
If nothing worked from all the above mentioned tips then there should be problem in your mother board. Try to clean dust properly from your mother board and check all the cable connections properly. Hope this will work for you.


  1. I found out that when ever I have my two external drives plug in to the usb 3 would cause that problem to shop up and so I needed to remove the external drives in order for my lap top to boot, this only just started happening after I replace the main drive and have to reload all of the drivers and windows again, but yes needed to go into my boot line up and made sure that it was my hard drive that boots up first. Thanks for the tips

  2. i am having same issue while runnig debian on VM ware ?

  3. Thanks for your informative piece. I was able to solve my issue by a thorough dusting of my PC internals.


  4. add a password for your administrator account. it works for me