The rescue desktop is up, the client's data is visible - and there is no network at all. No WiFi icon, no shares, no remote tool. On a network rescue job, that is the whole job blocked.
A WinPE only carries the network drivers its author packed into it. If your laptop's WiFi chip is not in that pack, the PE boots perfectly and still shows no wireless adapter - a very different situation from Windows, where the driver was installed long ago. NHV Boot treats WiFi as a headline feature, while Sergei Strelec expects you to preload drivers for odd hardware. Here is the working order, from the fastest cable to the permanent fix.
Both builds carry wide wired LAN driver support, so an Ethernet cable - through a USB-to-LAN adapter if the laptop has no port - works in almost every case. For a paid rescue, plug in, copy the data over the network or start the remote session, and solve the WiFi question later at your desk. The fastest fix is the one that ends the client's downtime.
NHV Boot advertises support for most WiFi and LAN adapters and ships a fast, modern WiFi connection interface plus touchpad support, so on the majority of laptops you simply click the network icon, pick the network and connect - like normal Windows. If your adapter is missing even here, update to the newest NHV build first; its driver pack is one of the most frequently refreshed parts of the project.
Strelec's answer is its user driver folder. On a working PC, download your WiFi driver from the laptop maker, extract it to raw INF form, and copy it into SSTR\USER\MY_DRIVERS_x64 on the USB. It loads while the PE boots, and the adapter appears like it was always there.
If you are already booted, Strelec's included network manager PENetwork can detect hardware and attempt driver installation, and a command prompt can load an INF live with drvload - worth one try before rebooting with the folder prepared.
Guessing drivers wastes the whole visit. In the PE, open Device Manager, find the network controller with the warning mark, open its Properties and read the Hardware Ids - the VEN and DEV numbers identify the exact chip. Search those numbers on a working machine and you will land on the correct driver family in one step, for either build.
Some brand-new or exotic WiFi chips have no usable driver in either PE today - that is a fact of PE life, not a fault of your USB. The professional fallbacks are a second USB disk for data copy, a phone hotspot only if the adapter itself works, or completing the rescue offline and handling updates after Windows is repaired. The full video shows the network behaviour of both builds so you can plan which USB to reach for.
Boot speed, tools, drivers and the final verdict - the complete Strelec vs NHV Boot comparison, step by step.
▶️ Watch Full VideoWindows has the driver installed permanently. A WinPE is a fresh mini-Windows on every boot - it only knows the adapters whose drivers the build author packed in, plus any you preload in Strelec's MY_DRIVERS folder.
Often yes. With the extracted INF files on a disk the PE can see, Device Manager or the drvload command can load many adapters live. If it refuses, prepare the MY_DRIVERS folder and reboot - the driver then loads during startup.
NHV Boot, for most laptops - its WiFi support and connection interface are headline features, and once the network is up both builds carry AnyDesk-class remote tools anyway.