Mất cả buổi để tìm hiểu và sửa lỗi này trong khi triển khai WDS Server, giờ post một bài để chia sẻ cho mọi người đỡ mất công tìm.

1, Giải pháp từ Bill Shelnutt trên diễn đàn Technet. Mình theo cách này và đã fixed được lỗi.

The problem:
Even though the PC seems to be booting via PXE boot from BIOS and connecting to the WDS server to run the WDS CAPTURE BOOT IMAGE applet, when you are prompted to CONNECT to the WDS SERVER you get the error “NETWORK PATH CAN NOT BE FOUND“. The issue here is that the network driver, although loading in PXE, is not loading in the 32bit Windows PE environment.

The Solution:
When you get to the initial screen prompting you to enter the image name and select the WDS server, (hit SHIFT + F10 BEFORE TRYING TO CONNECT TO THE WDS SERVER!!!)
SHIFT+F10 will bring up an [X:\windows\system32] prompt.

Drop a CD with the network driver installation EXE or MSI kit in the CD ROM (assuming D:\ is your CD-ROM).
At the command prompt, type: D: (or whatever your CD-ROM drive letter is) and launch the NIC CARD DRIVER INSTALLER. (NOTE: Since WindowsPE is 32 bit, even though you are launching from a DOS prompt, you can run 32 bit applications – This can be really helpful running other utilities (disk dioagnostics, as well!)

Drop a CD with the network driver installation INF file in the CD ROM (assuming D:\ is your CD-ROM).
From the X:\windows\system32> prompt, type in DRVLOAD {inf path} (ex. DRVLOAD d:\e1000.inf )
Once your NIC CARD DRIVER is installed, you’ll need to go back to the [X:\windows\system32>] prompt. From [D:] type X:
Now that you are back at the Windows PE [X:] prompt, run the following application:
This applet will initialize the new driver and startup the network in the Windows PE environment.

Verify that this worked by:
a) getting a SUCCESS message for starting the network as WPEUTIL INITIALIZENETWORK finishes running..
b) Do an IPCONFIG and you should now see the full load of IP address information for your PC’s adapter on the network.

Once you see that you have an IP ADDRESS assignment, you can close the DOS windows (“X” out in the upper right of the DOS window), and then PROCEED with entering the WDS SERVER NAME and click “CONNECT“.

You will then be prompted to provide logon credentials to your WDS server. Once you successfully connect to the WDS server, you can then place the image in the desired WDS image share folder (SVR (server) , WS (workstation), LT (Laptop) , etc.) When you continue from here, you should see a continuous count up of percentage loaded of your image to the server.

2, Giải pháp từ Chris Gralike

Caution, when imaging with Windows 7 and the KB3AIK_EN.iso the peimg command is no longer available. Instead you should use the dism command. You can find a manual how to add drivers using dism here.

In short;
+ Mount the boot.wim image.
dism /Mount-wim /WimFile:c:\wim\x64\boot.wim /index:2 /MountDir:c:\wim\x64\mount

+ Add a single driver (prev with peimg)
Dism /Image:c:\wim\x64\mount /Add-Driver /Driver:c:\drivers\mydriver.INF

+ Or recursive if you have a directory full of drivers
Dism /Image:c:\wim\x64\mount /Add-Driver /Driver:c:\drivers /Recurse

+ For unsigned drivers
Dism /Image:c:\wim\x64\mount  /Add-Driver /Driver:c:\drivers\mydriver.INF /ForceUnsigned

+ Save the changes to boot.wim.
Dism /Unmount-Wim /MountDir:c:\wim\x64\mount  /Commit

— Not sure what driver is needed? Then boot the machine using PXE untill the boot.wim holds with the error stating that a driver is missing. From this point you are able to press [shift-F10] to launch a commandpromt. In this commandprompt do the following.

+ open the setupapi.app.log
notepad x:\windows\INF\setupapi.app.log

+ Search this document for “FAILED” to locate the problem driver. (This might also be an registry error) and search for the device description. Usually something like.


+ Using this string in google will resolve most drivers. If non is returned try only the vendor etc till you find the approp. driver.

+ A different aproach (if the driver is known) is to search the document based on vendor ID. Sometimes (in my case) the driver was loaded succesfully but for some reason couldnt be initialized. Re-loading the driver gave more insight into the problem.

+ If the driver is found, download and copy it to a USB device and plug it into the client that has the missing driver to test it using the following commands inside the previously opend commandpromt.

drvload f:[yourdriver].inf
wpeutil Initializenetwork
ipconfig /all

If the driver works proceed with the previous steps to load the driver into the boot.wim.