Your USB-C dock's Ethernet works perfectly after Windows starts.

The laptop receives an IP address. Internet access works. File transfers are stable. The RJ45 connection appears completely normal.

Then you restart the laptop and try to PXE boot.

The network boot option may be missing, Start PXE over IPv4 may time out, or the deployment may begin only to lose Ethernet after Windows PE loads.

The key point is:

Ethernet working inside Windows does not prove that the same USB Ethernet controller is available before Windows starts.

PXE boot depends on a sequence of events that begins before the operating system exists:

Firmware → USB Ethernet Detection → Network Link → DHCP/PXE → Network Boot Program → WinPE

Instead of changing every BIOS and network setting at once, replay that sequence and identify exactly where it stops.

Replay the PXE Boot Chain

A useful PXE diagnosis starts with what you actually see on screen.

This distinction prevents a common mistake:

Treating every PXE failure as an Ethernet failure.

00:00 — Can the Firmware See USB-C Ethernet?

Begin at the moment the laptop powers on.

Connect:

Laptop → USB-C Dock → Ethernet

before turning the computer on.

Enter the BIOS/UEFI boot menu and look for options such as:

UEFI Network

PXE IPv4

Network Boot

or a similar entry.

If PXE is available when using built-in Ethernet but disappears when networking comes through the dock, the problem occurs before DHCP or the PXE server becomes relevant.

The firmware may simply not be initializing the USB Ethernet controller.

Depending on the computer manufacturer, BIOS options may include:

• UEFI Network Stack
• USB Boot Support
• Thunderbolt Boot Support
• Pre-Boot Thunderbolt Modules
• Network/PXE Boot
• Fast Boot settings

For example, Dell's current USB-C and Thunderbolt PXE boot documentation shows that supported systems may require specific BIOS settings before USB-C or Thunderbolt Ethernet becomes available during pre-boot. The exact names and behavior vary by computer model, so treat manufacturer instructions as model-specific rather than universal settings.

If the firmware never exposes the dock's network adapter, changing Windows Ethernet drivers will not fix this stage because Windows has not loaded yet.

00:05 — Does the Ethernet Link Exist Before Windows?

Next, look at the physical network connection.

If the dock and switch provide Ethernet LEDs, watch them during startup.

If the link remains off until Windows loads

The USB Ethernet controller may not be initialized during pre-boot.

Return to:

BIOS/UEFI → USB/Thunderbolt pre-boot settings → firmware compatibility

If the link becomes active before Windows starts

That is useful evidence.

You have likely passed:

Firmware detection → Ethernet controller initialization → physical link

and can move forward to PXE discovery.

If Ethernet also fails after Windows starts, fix that basic connection first using the USB-C hub Ethernet troubleshooting guide.

PXE troubleshooting becomes much harder if ordinary RJ45 connectivity is already unstable.

00:10 — Does the Client Receive an IP Address?

Now watch what happens after:

Start PXE over IPv4

appears.

Microsoft's PXE boot process documentation describes the basic sequence: the client broadcasts for network information, receives an address from DHCP, discovers a PXE server, receives the path to a Network Boot Program, and then downloads and runs that program.

This gives you an important diagnostic boundary.

No IP address

Investigate:

• DHCP availability;
• switch port/VLAN;
• routing;
• PXE IP Helpers;
• network access controls.

Do not immediately replace the dock.

If possible, place the test laptop temporarily on the same subnet as the PXE server or deployment point.

If PXE suddenly works, pre-boot Ethernet may be functioning correctly and the real issue is the routed network path.

For Configuration Manager environments spanning different networks, Microsoft recommends using IP Helpers to forward the appropriate traffic and warns against treating DHCP Options 66 and 67 as the general solution for routed PXE deployments.

00:15 — The Laptop Gets an IP Address but Still Does Not Boot

This changes the diagnosis significantly.

If the PXE client has already obtained an IP address, then several earlier layers are functioning:

Firmware

✓

Dock Ethernet

✓

Physical link

✓

DHCP

✓

The failure has moved farther down the chain.

The next question is:

Did the client receive and download the correct Network Boot Program?

Check:

• UEFI vs. legacy architecture;
• x64 vs. other boot architecture;
• deployment availability;
• PXE server configuration;
• Network Boot Program;
• boot-image assignment.

Microsoft's documented PXE process shows that after discovery, the PXE server supplies the NBP path and the client downloads and runs it before continuing into the Windows deployment environment.

So if an IP address appears but the boot program does not load, this is no longer primarily a USB-C Ethernet detection problem.

00:20 — WinPE Loads, Then Ethernet Disappears

This is one of the most misleading PXE failures.

The sequence may look like:

PXE starts

→ Boot file downloads

→ Windows PE appears

→ Network disappears

→ Deployment fails

At first glance, it looks as though the USB-C dock suddenly stopped working.

But another environment change has occurred.

During the first phase, the laptop's firmware handled network access.

Once Windows PE loads, WinPE needs a compatible network driver for the dock's USB Ethernet controller.

If that driver is missing, firmware-level PXE can succeed while the deployment environment has no Ethernet.

In that case:

1. Identify the USB Ethernet controller used by the dock.
2. Obtain the appropriate OEM-approved network driver.
3. Verify that it supports your WinPE architecture.
4. Add the required network driver to the boot image.
5. Update or redistribute the boot image.
6. Retest on one affected laptop before broader deployment.

Do not add large collections of unrelated drivers “just in case.” Keep the boot environment as controlled as possible.

00:25 — Is PXE Seeing the MAC Address You Expect?

USB-C docking adds another variable that matters to enterprise deployment:

the Ethernet MAC address.

The dock's Ethernet controller may present its own MAC rather than the laptop's built-in Ethernet identity.

Some business laptops also support manufacturer-specific:

MAC Address Pass-Through

which can cause a supported dock to present a system-associated address instead.

This matters when your deployment infrastructure identifies machines by:

• MAC address;
• known/unknown computer records;
• deployment collections;
• NAC rules;
• asset database entries.

A common IT mistake is to assume:

The MAC recorded for the laptop is automatically the MAC PXE sees through every USB-C dock.

Do not assume.

Record the actual address presented during the deployment process.

Separate PXE Boot From Two Similar Ethernet Problems

PXE, normal Ethernet, and Wake-on-LAN all use networking, but they test different parts of the system.

Normal Ethernet

Tests whether networking works after the operating system loads.

Wake-on-LAN

Tests whether the network path can receive a wake event from a supported power state.

PXE Boot

Tests whether the firmware can initialize Ethernet before the operating system loads.

That means a dock can:

Pass Windows Ethernet

but:

Fail PXE

without contradicting itself.

Similarly, a Gigabit Ethernet specification does not automatically mean:

UEFI PXE compatible

or:

WinPE driver ready

If your deployment concern is waking already-installed machines rather than loading an OS image, the Wake-on-LAN through a USB-C docking station guide covers that separate workflow.

Record Five Checkpoints Instead of “PXE Failed”

For IT teams, this is one of the most useful changes you can make.

Instead of recording:

Laptop X + Dock Y = PXE Fail

record:

Now the help desk can immediately see where the problem starts.

For example:

Fail at UEFI option

→ Firmware/pre-boot support.

Pass UEFI, fail DHCP

→ Network infrastructure.

Pass DHCP, fail boot file

→ PXE server/deployment.

Pass boot file, fail WinPE network

→ Driver.

This type of test record also fits naturally into an existing USB-C hub compatibility matrix for an IT team.

Add columns for:

PXE Firmware Detection

PXE DHCP

WinPE Ethernet

rather than simply writing:

Network = Pass

Where USB-C Hardware Fits Into PXE Testing

For a permanent desk where deployment testing also includes 4K display output, charging, audio, and multiple USB peripherals, a USB-C docking station with Gigabit Ethernet, 4K@60Hz HDMI, and 100W Power Delivery provides a fuller workstation candidate. The current CB-D53s specification includes Gigabit Ethernet, three USB 3.0 ports, two USB 2.0 ports, separate audio connections, 4K@60Hz HDMI, and up to 100W power pass-through.

However, this distinction is essential:

Neither product should be described as a guaranteed PXE solution simply because it has Gigabit Ethernet.

Their current product specifications do not explicitly claim PXE boot support.

PXE must be validated with the actual:

Laptop + BIOS/UEFI + USB-C controller + dock Ethernet + network + boot environment

before enterprise deployment.

The Fastest Way to Diagnose PXE Through a Dock

When a deployment fails, ask these questions in this exact order:

1. Does the UEFI network/PXE option appear?

If no → investigate firmware and pre-boot USB Ethernet support.

2. Does the Ethernet link come up before Windows?

If no → investigate USB Ethernet initialization.

3. Does PXE receive an IP address?

If no → investigate DHCP, VLANs, routing, and IP Helpers.

4. Does the client receive the Network Boot Program?

If no → investigate the PXE server and deployment configuration.

5. Does Ethernet survive after WinPE loads?

If no → investigate the WinPE network driver.

Each answer eliminates an entire category of unnecessary troubleshooting.

Quick Answers

Why does dock Ethernet work in Windows but not PXE?

Because Windows has its own USB and network drivers, while PXE initially depends on firmware-level support for the USB Ethernet controller.

Does Gigabit Ethernet mean a USB-C dock supports PXE?

No. Gigabit Ethernet describes network capability and speed, not guaranteed BIOS/UEFI PXE support.

Why does PXE start but lose Ethernet in WinPE?

The firmware may support the Ethernet controller while the WinPE image lacks the required network driver.

Should I change DHCP settings if the PXE option is missing from BIOS?

No. If firmware does not expose the network adapter for PXE, the client has not reached DHCP yet.

Why does PXE work on one laptop but not another with the same dock?

Laptop models can differ in firmware, USB-C architecture, security settings, and pre-boot support.

Final Takeaway

When PXE boot fails through USB-C dock Ethernet, do not troubleshoot the whole process as one problem.

Replay the boot chain:

Firmware

→ USB Ethernet

→ Network Link

→ DHCP/PXE

→ Network Boot Program

→ WinPE

Then fix the first stage that fails.

The most important rule is:

Ethernet working in Windows does not prove that the USB Ethernet controller is available during pre-boot.

And equally important:

A Gigabit Ethernet port does not automatically guarantee PXE boot support.

PXE compatibility belongs to the complete environment:

Laptop + Firmware + USB-C Dock + Ethernet Controller + Network + Deployment Image

Once IT records where that sequence stops, “PXE does not work through the dock” becomes a much more precise—and much easier to solve—deployment problem.