The most common causes of this problem are:
1) The boot image may not contain the correct network driver for the client computer. To resolve this, on the client computer, press SHIFT+F10 to open a command prompt and run IPConfig. If an IP address and subnet mask are not reported in the output, this indicates that networking has not been started and it is likely that a network driver is not present. To fix this, add the driver from the hardware manufacturer to the image by using the tools in the Windows AIK.
2) The account whose credentials were entered on the credential screen of Windows Deployment Services client does not have permissions to read the install .wim file. These images are located at\\<WDSServer>\RemoteInstall\Images\<Image Group>. For more information, please refer to the following article:
3) The boot image you use does not support this install image. A client booting into an x86-based boot image will only be able to view x86-based install images on the image selection page. Are you booting into an x86-based boot image to deploy x64-based install images?