New laptops hide their drives behind controllers your WinPE has never met. A well-planned drivers folder — storage first, network second — turns that dead end into a two-minute fix.
The classic modern repair scene: your toolkit boots perfectly, opens its disk tools — and shows no drive at all. The SSD is fine; the laptop's storage controller (often Intel RST with VMD) simply has no driver inside your WinPE. The same story repeats with Wi-Fi and ethernet on new models. The answer is not a bigger toolkit — it is a drivers folder strategy: the right driver families, carried as clean INF packs, with a loading routine you have practised.
Priority one is storage, because without the drive there is no repair at all. Carry the current Intel RST / VMD driver pack (the usual suspect on 11th-generation and newer Intel laptops), and the common AMD and generic NVMe alternatives your market actually sells. Download them from the chip maker or the laptop maker's support page — never from driver-aggregator sites — and extract them to raw driver files: the .inf, .sys and .cat files, not a setup EXE. WinPE cannot run a glossy installer; it loads INF files.
When a booted WinPE shows no drive, load the pack from the command line: drvload E:\Drivers\Storage\irst\iaStorVD.inf — adjust the path to your stick's letter. Seconds later the SSD appears in your disk tools. Practise this once at your desk; at a customer's home is the wrong time to learn the command.
A repair environment without network is half-blind: no fresh drivers, no cloud backup target, no remote help. Carry wired and wireless packs for the common chip families — Intel, Realtek, Qualcomm — again as extracted INF folders. Load them the same way with drvload, then confirm the adapter appears and picks up an address before blaming the router.
Honesty note: brand-new Wi-Fi chips sometimes have no WinPE-friendly driver at all. Your fallback kit matters — a cheap USB ethernet adapter with a universally supported chip, carried in the bag, has rescued more repairs than any single driver pack.
Inside Drivers, sort by job — Storage, Network, Chipset — and inside each, by family with the version and date in the folder name: Intel_RST_19.5_2026-08. When a newer pack arrives, the new folder lands beside the old; the old one is deleted at the quarterly review, not in a panic mid-repair.
Skip the giant all-in-one driver packs for the boot environment. They are built for installing Windows drivers in bulk, they weigh gigabytes, and their useful WinPE content is the same few storage and network families you can carry in a few hundred MB — hand-picked, current, and known to load.
Sometimes the storage driver loads and the drive still hides, because the laptop's BIOS has the controller in a RAID/RST mode your PE struggles with, or the drive is behind a mode the vendor locks down. The service-manual answer on some models is switching the storage mode to AHCI — but be honest with the customer first: changing storage mode on a machine whose Windows was installed in the other mode can stop that Windows from booting until it is prepared for the switch.
The technician's order of operations: try the driver, try a second PE, explain before touching BIOS settings, and never leave a machine in a changed mode without noting it in your job log and the stick's changelog. The drivers folder solves most of these cases — the rest are judgement calls, and judgement is the job.
See the toolkit approach in the video — then build your drivers folder before the next new laptop teaches you this lesson the hard way.
▶️ Watch Full VideoYes — DISM can inject drivers into boot.wim so they load automatically, and your most-used storage pack deserves that treatment. Keep the folder method as well: injected drivers help only until a newer controller appears, while a folder on the stick can be updated with a file copy in the field.
Either official source works. The laptop maker's pack is tested for that model; the chip maker's pack is usually newer and covers more models. For a general repair folder, chip-maker packs are the practical choice, with model-specific downloads fetched when a known laptop is booked in.
Only if you still service very old 32-bit-only machines with a 32-bit PE. Most technicians now carry a 64-bit WinPE, and modern laptops are 64-bit only. If your market includes genuinely old hardware, that is a separate legacy stick — do not bloat the main toolkit for it.