When the computer gets stuck on the message “Start PXE over IPv4” at startup, it means that the network boot process is initiated but cannot proceed further. This phenomenon prevents the system from loading an operating system or tool via the network, often paralyzing the device. Understanding why this step is blocked and how to restore normal startup is essential, especially in professional contexts where PXE boot is frequently used.
Blockage at the start of network boot: origin of the problem
The message “Start PXE over IPv4” indicates that the computer is attempting to boot by searching for a DHCP server on the network capable of providing it with an IP address and a boot file. If this step remains frozen, it means that the PXE client is not receiving the expected response or that network communication is interrupted.
Several causes can be at the origin of this blockage, including:
- Absence or misconfiguration of a DHCP or PXE server
- Physical network connection problem (unplugged cable, defective port)
- Incorrect BIOS/UEFI settings, especially in the boot order
- Isolated network without a configured PXE boot server
Without resolution, the computer will not be able to continue its startup and will remain stuck on this message.
Network checks to perform as a priority
The first step to unblock the situation is to confirm that the network allows the necessary communication:
- Ensure that the Ethernet cable is properly connected and that the network port lights are active
- Check that the DHCP server is operational and assigning IP addresses to client stations
- Verify that a PXE server is configured to respond to requests and provide the boot file (bootloader)
In a professional environment, these elements are often managed by the network or IT team. In the absence of a PXE server, the boot order must be modified to precede network boot.
Adjusting settings in BIOS or UEFI
The BIOS or UEFI controls the computer’s boot sequence. If the PXE option is enabled and prioritized, but no server is available, blockage is inevitable.
To correct this:
- Access the BIOS/UEFI at startup (usually the F2, Delete, or Escape key)
- Change the boot order by placing the hard drive or SSD first
- Disable PXE network boot if you do not wish to use it
These simple adjustments allow the computer to boot directly on its local system, thus avoiding blockage.
Other possible causes and additional leads
Sometimes, specific settings can prevent network boot from working, such as the presence of an enabled Secure Boot mode, incompatible with certain unsigned PXE environments. It is then advisable to disable this option in the UEFI.
Another common case involves defective or poorly recognized network cards, which block the boot phase. Testing with another card or another Ethernet cable can eliminate this factor.
Finally, if the PXE server uses a protocol or version incompatible with the client machine, it will be necessary to update the firmware or configure a suitable PXE server.