AOMEI PXE Boot Free Review: Features & Limitations

Top Tips for Troubleshooting AOMEI PXE Boot FreeAOMEI PXE Boot Free is a useful utility for network-based system deployment and maintenance, allowing you to boot multiple client machines from a single Windows PE image over LAN. While generally straightforward, PXE boot environments can fail for many reasons: network configuration, server setup, client hardware, firewall rules, or boot image issues. This article collects practical, action-oriented troubleshooting tips to help you diagnose and fix common problems quickly.

1. Verify basic prerequisites

• Confirm network connectivity. Ensure both server and clients are on the same layer-2 network (same switch/VLAN) if you’re not using DHCP relay/boot helpers.
• Check DHCP presence. PXE requires DHCP to provide an IP and optionally the boot file information. Make sure a DHCP server is running and reachable from clients.
• Use the right Windows PE image. A corrupted or mismatched WinPE image can fail to boot clients. Test the WinPE ISO in a VM first.
• Match architecture. Use x86 WinPE for 32-bit clients and x64 WinPE for 64-bit clients; mismatches may prevent booting or cause instability.

2. Confirm AOMEI PXE Boot Free server configuration

• Run AOMEI PXE Boot Free as Administrator. Elevated privileges are required to bind to network services and write temporary files.
• Check the boot folder path. In the AOMEI GUI, verify that the folder containing your boot.wim (or AOMEI image files) is correct and accessible.
• Ensure the listening interface is correct. If the server has multiple NICs, explicitly select the NIC that serves the client subnet.
• Verify port usage. PXE uses UDP ports 67 (DHCP), 68 (DHCP client), and 69 (TFTP). If AOMEI uses its own service for boot file delivery, ensure those ports aren’t blocked or in conflict with another DHCP server.

3. Diagnose DHCP and TFTP issues

• Look for DHCP responses. Use a packet sniffer (Wireshark/tcpdump) on the server or a client to confirm DHCP DISCOVER and OFFER packets. If there’s no OFFER, the client won’t proceed to PXE.
• Check PXE-related DHCP options. Some environments require DHCP Option ⁄₆₇ (TFTP server name and boot file filename). AOMEI can work without these only if it’s running on the same machine as DHCP or if it handles PXE itself—confirm your setup.
• Test TFTP manually. Use a TFTP client to request the boot file from the server. If the boot file (e.g., pxelinux.0 or boot.wim) fails to transfer, the problem is TFTP-related (permissions/firewall).
• Increase TFTP timeout/retries. Slow networks or large WIM files can time out. If possible, compress the WIM or use a smaller PE image for testing.

4. Address firewall and antivirus blockers

• Temporarily disable Windows Firewall on the server for testing. If disabling allows PXE to work, add specific inbound rules for UDP 67, 68, and 69 and the AOMEI executable instead of leaving firewall off.
• Whitelisting AOMEI services. Many antivirus suites block unknown network services. Add AOMEI PXE Boot Free to exclusions or create rules to allow its network activity.
• Check network access control (NAC). Some managed switches or NAC systems block unknown clients until approved; ensure clients are allowed to obtain DHCP and TFTP.

5. Fix client-side issues

• Enable network/PXE boot in BIOS/UEFI. On many systems you must enable PXE or set network as a higher boot priority than local disk.
• Switch between UEFI and Legacy modes. If the server provides a legacy PXE boot file but the client is in UEFI mode (or vice versa), the client will not boot. Match the mode or provide both boot files.
• Update network adapter drivers/firmware. Very old NIC firmware or odd OEM PXE ROMs can cause failures—update firmware if possible.
• Test with another client. This distinguishes server-side problems from a single faulty client.

6. Reduce image size and complexity

• Use a minimal WinPE for initial testing. Large custom WinPE images with many drivers or software can introduce errors. Start with a plain AOMEI or Microsoft WinPE build to verify PXE basics.
• Split very large images. If delivering very large WIMs causes timeouts, consider using smaller images or a multicast option (if supported) to reduce per-client transfer load.

7. Check logs and error messages

• AOMEI logs. Look for logs in the AOMEI installation folder or temporary directories—these often record file path or permission errors.
• Windows Event Viewer. On the server, check System and Application logs for service start/permission or network binding errors.
• Client error codes. PXE firmware often shows error codes (e.g., “PXE-E53: no boot filename received”). Search those exact messages — they’re specific pointers to DHCP/TFTP/filename issues.

8. Use alternative delivery methods for troubleshooting

• Boot from USB. If network boot fails, boot a client from a USB WinPE to confirm the WinPE image itself works.
• Set up a temporary DHCP/TFTP on another machine. Running a known-good PXE stack (like a simple TFTP+DHCPOFFER test server) isolates whether AOMEI’s server is the issue.
• Use multicast or lightweight file share. For many clients, using a network share and local bootable USB to load the image can be a fallback.

9. Network infrastructure checks

• Check switch settings for PXE traffic. Ensure switches allow DHCP broadcasts and aren’t blocking TFTP or specific UDP ports.
• VLAN and routing. If clients are on different VLANs, you’ll need DHCP relay/bootp-helper on routers to forward broadcasts. Confirm option ⁄₆₇ behavior with your router.
• MTU and fragmentation. Large UDP packets (rare for PXE/TFTP) may be dropped if MTU mismatches exist; ensure consistent MTU across the path.

10. Common specific error fixes

• PXE client hangs at “Start PXE over IPv4”: Usually DHCP not reachable — check cabling, DHCP server, or VLAN.
• PXE-E53 (no boot filename): DHCP didn’t provide filename/option 67 — configure DHCP or AOMEI to supply the filename.
• TFTP timeout or file not found: File path incorrect, TFTP permissions, or firewall blocking UDP/69.
• WinPE starts but AOMEI tools crash: Corrupt WIM, missing drivers, or incompatible WinPE architecture — test in VM and recreate the WIM.

Quick troubleshooting checklist (summary)

• Ensure server and clients are on the same network or proper DHCP relay exists.
• Run AOMEI as Administrator and select the correct NIC and boot folder.
• Verify DHCP offers and TFTP transfers with packet capture.
• Temporarily disable firewalls/AV to test, then create specific allow rules.
• Match UEFI/Legacy modes and WinPE architecture to clients.
• Test the WinPE image locally (USB/VM) to rule out image problems.
• Consult AOMEI logs and Windows Event Viewer for specific errors.

Troubleshooting PXE is often a process of elimination: verify basic connectivity, confirm DHCP/TFTP behavior, check server and client settings, then test components in isolation. Following the steps above will resolve most issues with AOMEI PXE Boot Free and help you identify whether the problem lies in the network, server, image, or client hardware.