How to Fix "Start PXE over IPv6" on Windows: 6 Easy Methods

What Does "Start PXE over IPv6" Mean?

PXE stands for Preboot Execution Environment. It allows a computer to start from a network server instead of a local drive. Businesses, schools, repair shops, and IT departments often use PXE boot to install or manage Windows across many computers.

On a normal home or office PC, however, you usually want Windows to boot from your internal SSD or hard drive. If the computer shows "Start PXE over IPv6", it is often saying, “I tried the usual boot device, but I could not find something usable, so now I am checking the network.”

Sometimes the message appears briefly and Windows still starts after a delay. Other times the computer gets stuck, repeats the same boot message, or shows related messages such as "Start PXE over IPv4", "Checking media presence", "No bootable device", or "Boot device not found."

Common causes include:

• The BIOS or UEFI boot order is wrong.
• Windows Boot Manager is not first in the boot list.
• PXE boot or network boot is enabled when it should not be.
• The SSD or hard drive is not detected.
• The boot configuration data, also called BCD, is damaged.
• A Windows update, BIOS update, power failure, or drive issue disrupted startup.
• The internal storage drive is failing or disconnected.

Before You Start: A Quick Safety Check

Before diving into BIOS settings and recovery commands, do two simple things. First, unplug unnecessary external devices such as USB drives, external hard drives, memory cards, docking stations, and Ethernet cables. Second, restart the computer once.

Why? Because a connected USB drive or network cable can sometimes influence the boot path. Your PC may be trying to boot from something that was never invited to the party. If Windows starts normally after removing extra devices, you have found the easiest fix of the day. Go celebrate with coffee. You earned it.

Method 1: Change the Boot Order in BIOS or UEFI

The most common fix for Start PXE over IPv6 is to make sure your internal Windows drive is listed before network boot. On modern Windows systems, the correct entry is often called Windows Boot Manager. On some PCs, it may show the SSD or hard drive brand name instead.

How to change boot order

1. Turn off your computer completely.
2. Turn it on and immediately press the BIOS key repeatedly.
3. Common keys include F2, F10, F12, Esc, or Delete, depending on the brand.
4. Look for a menu named Boot, Boot Order, Boot Sequence, or Startup.
5. Move Windows Boot Manager or your internal SSD/HDD to the top.
6. Move PXE IPv6, PXE IPv4, Network Boot, or Onboard NIC lower in the list.
7. Save changes and exit. Usually this is done with F10.

If Windows starts after this change, the issue was simply a boot priority problem. This can happen after a BIOS reset, motherboard battery issue, firmware update, accidental setting change, or a laptop deciding to be dramatic before breakfast.

Brand-specific hints

On Dell computers, look under sections such as General > Boot Sequence. On HP systems, the BIOS is often opened with F10. On Lenovo laptops, F1, F2, Enter, or the Novo button may open startup settings. The names vary, but the goal is the same: put Windows Boot Manager first.

Method 2: Disable PXE Boot or Network Boot

If you do not use network boot, you can often disable it. This prevents the computer from trying to start through IPv6 or IPv4 PXE when the normal Windows boot option is available.

Steps to disable PXE boot

1. Enter BIOS or UEFI setup.
2. Open the Boot, Advanced, Network, or Integrated NIC section.
3. Find options such as PXE Boot, Network Boot, UEFI Network Stack, PXE IPv6, or PXE IPv4.
4. Disable PXE boot, or disable only PXE over IPv6 if you still need IPv4 network boot.
5. Save and restart.

For most personal computers, disabling PXE boot is safe. However, if the device belongs to your workplace, school, or IT-managed environment, do not change this setting without permission. Your IT team may use PXE for deployment, recovery, or remote management. Nobody wants to explain, “I disabled the company imaging system because a blog told me to.” That is a meeting you can avoid.

When this method works best

This method is ideal when Windows still boots after a delay, but the PXE message appears every time. In that case, the internal drive may be fine, but the computer checks network boot before Windows. Disabling PXE or lowering it in the boot order should remove the annoying startup pause.

Method 3: Check Whether the SSD or Hard Drive Is Detected

If Windows Boot Manager is missing from BIOS, or your SSD/HDD does not appear at all, the computer may not be seeing the internal drive. That is more serious than a simple boot-order mistake, but it is still diagnosable.

How to check drive detection

1. Enter BIOS or UEFI setup.
2. Look for Storage, Information, System Information, NVMe Configuration, or SATA Configuration.
3. Check whether your internal SSD, NVMe drive, or hard disk appears.
4. If the drive appears, continue with Windows repair methods below.
5. If the drive does not appear, shut down the PC and investigate the hardware.

On a desktop, a SATA cable or power cable may be loose. On a laptop, the drive may have shifted, failed, or developed a connector issue. On an NVMe system, the drive may need to be reseated. If the computer is under warranty, contact the manufacturer before opening the case.

Warning signs of drive failure

• Windows was freezing or crashing before the PXE message appeared.
• The computer sometimes detects the drive and sometimes does not.
• You hear clicking or unusual noise from a hard drive.
• BIOS shows no internal storage device.
• Startup repair repeatedly fails.

If you suspect drive failure and the data is important, stop experimenting and consider professional data recovery. Repeated repair attempts on a dying drive can make recovery harder. In plain English: do not keep poking the bear if the bear contains your only copy of tax files, family photos, or that novel draft you swear you are going to finish.

Method 4: Reset BIOS or UEFI Settings to Default

If the PXE over IPv6 problem started after changing BIOS settings, updating firmware, replacing hardware, or clearing CMOS, resetting BIOS to default can help. This restores the motherboard’s standard configuration and may bring back the correct Windows boot entry.

How to reset BIOS settings

1. Enter BIOS or UEFI setup.
2. Find an option such as Load Setup Defaults, Restore Defaults, Optimized Defaults, or Factory Defaults.
3. Apply the default settings.
4. Check the boot order again and make sure Windows Boot Manager is first.
5. Save changes and restart.

This method is useful when BIOS settings are tangled like headphone wires in a drawer. Resetting defaults gives you a cleaner starting point. Afterward, you may need to re-enable a few custom settings, such as virtualization, XMP memory profiles, TPM, or secure boot settings, depending on your setup.

UEFI vs. Legacy boot mode

Most modern Windows 10 and Windows 11 systems use UEFI with a GPT-formatted drive. If your system was installed in UEFI mode, switching to Legacy or CSM mode can prevent Windows from booting. If you are unsure, leave the system in UEFI mode and look for Windows Boot Manager. Randomly switching boot modes is like randomly flipping breakers in your house because one lamp blinked. It might work, but it is not a strategy.

Method 5: Use Windows Startup Repair

If the drive is detected and boot order looks correct, Windows boot files may be damaged. In that case, use Windows Recovery Environment, also known as WinRE, to run Startup Repair.

If Windows sometimes starts

1. Open Settings.
2. Go to System > Recovery.
3. Next to Advanced startup, select Restart now.
4. Choose Troubleshoot > Advanced options > Startup Repair.

If Windows does not start

1. Create a Windows installation USB on another computer.
2. Boot the problem PC from the USB drive.
3. Select your language and keyboard layout.
4. Choose Repair your computer, not Install now.
5. Go to Troubleshoot > Advanced options > Startup Repair.

Startup Repair checks for common startup problems and tries to fix them automatically. It may repair missing boot files, incorrect boot configuration, or other issues preventing Windows from loading. Sometimes it works beautifully. Sometimes it says it could not repair your PC, which is Windows-speak for “I tried, but please bring stronger tools.”

After Startup Repair

Restart the PC and check whether Windows loads normally. If the PXE message returns, go back into BIOS and confirm that Windows Boot Manager is still first. If Startup Repair fails repeatedly, move to the next method and rebuild boot files manually.

Method 6: Rebuild Windows Boot Files and Check the Disk

When automatic repair is not enough, you can use Command Prompt from Windows Recovery Environment to repair boot files and check the disk. This method is more advanced, but it is often effective when the computer sees the drive but cannot boot Windows.

Open Command Prompt from recovery

1. Boot into Windows Recovery Environment.
2. Select Troubleshoot.
3. Select Advanced options.
4. Open Command Prompt.

Check drive letters first

In recovery mode, Windows may not use the same drive letters you see inside normal Windows. Your Windows installation might be on C:, D:, or another letter. Use these commands carefully:

Look for the volume that contains the Windows folder. Once you know the correct drive letter, you can continue.

Run CHKDSK

To check the file system and repair logical errors, run:

Replace C: with the correct Windows drive letter if needed. The /f option fixes file system errors, while /r looks for bad sectors and attempts to recover readable information. This can take a long time on large or damaged drives, so be patient. Yes, “be patient” is the least satisfying computer advice ever, but this is one of those moments where it applies.

Rebuild boot files with BCDBoot

On many UEFI systems, BCDBoot is the cleanest way to recreate boot files. A common command looks like this:

Again, replace C: with the correct Windows partition letter. This command copies boot files from the Windows folder and creates or repairs the boot configuration needed to start the operating system.

Optional Bootrec commands

In some recovery cases, especially older BIOS/MBR installations, technicians may use:

These commands are useful in certain startup repair scenarios, but modern UEFI/GPT systems often respond better to BCDBoot. If you are not comfortable using recovery commands, ask a technician for help. A typo in recovery tools can turn a small boot issue into a larger headache with a side of regret.

What If None of the 6 Methods Works?

If the computer still shows Start PXE over IPv6 after all six methods, narrow the problem into one of three categories: firmware settings, storage hardware, or Windows installation damage.

Try these next steps

• Update BIOS or UEFI firmware from the PC manufacturer’s official support page.
• Run built-in hardware diagnostics if your computer offers them.
• Test the SSD or hard drive in another compatible computer or external enclosure.
• Create Windows installation media and attempt a repair install.
• Back up files from the drive using another PC before reinstalling Windows.
• Replace the drive if diagnostics show failure.

If your data matters, focus on backup before reinstalling. A clean Windows installation may fix the boot issue, but it can erase files depending on the choices you make. Read every setup screen carefully. Windows installation screens are not thrilling literature, but they are important literature.

How to Prevent "Start PXE over IPv6" in the Future

Once your PC boots again, take a few preventive steps. Make sure Windows Boot Manager remains first in BIOS. Disable network boot if you do not use it. Keep BIOS firmware and storage drivers updated through trusted manufacturer tools. Avoid interrupting Windows updates, especially during restart phases. And most importantly, maintain a reliable backup.

A good backup turns a boot failure from a five-alarm panic into a manageable repair. Use File History, OneDrive, an external drive, dedicated backup software, or a full system image. The best backup is the one you actually use. The second-best backup is the one you start creating immediately after reading this sentence.

Real-World Experience: What This Error Usually Looks Like in Practice

In real repair situations, Start PXE over IPv6 usually shows up in a few predictable ways. The easiest case is the “wrong boot order” case. Someone updates BIOS, replaces a CMOS battery, resets firmware settings, or accidentally changes a startup option. Suddenly, PXE IPv6 is above Windows Boot Manager. The computer pauses at the PXE screen, waits, then eventually boots. This is annoying but usually simple. Put Windows Boot Manager first, disable network boot, save, restart, and the machine behaves again.

The second common case is the “drive temporarily disappeared” case. This happens more often on older laptops, desktops that were recently moved, or machines with aging SATA cables. The BIOS looks for the internal drive, does not see it, and goes searching for a network boot option. If the drive reappears after reseating cables or restarting, do not ignore it. A drive that disappears once may disappear again. Back up your files while the computer is cooperating. Computers are like cats: when they are being cooperative, take advantage quickly.

The third case is boot file damage. The SSD appears in BIOS, Windows Boot Manager may still exist, but startup fails. This can follow a power outage, interrupted update, failed clone, partition resizing mistake, or dual-boot experiment that went sideways. Startup Repair may fix it. If not, rebuilding boot files with BCDBoot often helps, especially on UEFI systems. The key is identifying the correct Windows partition before running commands. In recovery mode, drive letters can shift, and assuming C: is always Windows can cause confusion.

The fourth case is the one nobody loves: failing storage. If BIOS does not detect the SSD or hard drive at all, and reseating does not help, the PXE message may be a symptom rather than the disease. The computer is not choosing network boot because it loves networking. It is choosing network boot because the local boot device is missing. In this situation, repeated boot repair is not the answer. Diagnostics, backup attempts, data recovery, or drive replacement are the better path.

One practical example: a desktop shows "Checking media presence… Start PXE over IPv6" after being moved to another room. The owner assumes Windows broke. In BIOS, the SSD is missing. Opening the case reveals a loose SATA cable. After reconnecting it and moving Windows Boot Manager to the top, Windows starts normally. Another example: a laptop shows PXE after a failed Windows update. BIOS detects the NVMe drive, but Windows will not boot. Startup Repair fails, but BCDBoot recreates the boot files and the system starts again.

The biggest lesson is simple: do not treat the PXE message as one single problem. Treat it as a clue. If the drive is detected and Windows Boot Manager exists, focus on boot order and repair tools. If the drive is missing, focus on hardware. If the issue happens only when Ethernet is connected, check network boot settings. This calm, step-by-step approach saves time, protects data, and keeps you from reinstalling Windows when all you needed was one BIOS setting and a tiny bit of patience.

Conclusion

The "Start PXE over IPv6" message looks technical, but the meaning is usually straightforward: your PC is trying to boot from the network because it cannot start from the expected Windows drive. Start with the easy fixes. Remove external devices, correct the boot order, disable PXE boot, and confirm that your SSD or hard drive appears in BIOS. If the drive is detected but Windows still refuses to load, use Startup Repair, CHKDSK, and BCDBoot to repair startup files.

If the internal drive is not detected, pause before making software changes. Check connections, run diagnostics, and protect your data. The best fix depends on what the BIOS sees. Once you know that, the scary PXE message becomes much less mysteriousand much more fixable.

SEO Tags