• Hi, I tried to setup the PXE with WinPE. Now my environment is the latest clonedeploy with version 1.3.5 and PE builder wtih 1.2.1. I can successfully build the Win10 PE wim and I also merged the tftpboot folder to clonedeploy and restart the tftp service. Everything thing is ok to boot the client. But the client is stucked at this step "wpeinit". You can refer to the attached picture. What should I do next step?[img][/img]

  • This seems to be more of an issue with WinPE than CloneDeploy, none of the CloneDeploy scripts have even started yet. Perhaps it's driver related, missing storage driver or nic? How much ram is in this machine? Have you tried it on any other models?

  • I created the WINPE on a virtual machine with 8G memory and then I delivered the WINPE to client for both Virtual machine with 8G memory and a physical machine with 4G memory. Do I need to create the WINPE with physical machine? I will try it today.

  • Hi, Clonedeply,

    Today, I tried again on the phsical PC to create the tftp image but no luck.

    I find there are some erros when excuting "Section Install-Drivers".
    The errors are like:
    Searching for driver packages to install...

    error: 2

    No driver packages were found on the specified path.
    Verify that the driver .INF files are in the specified location and try the command again.

    I also searched the dism.log. I can find the command line:
    DISM.EXE: Executing command line: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\dism.exe" /Image:"C:\Users\DILLON~1\AppData\Local\Temp\WinPE" /Add-Driver /Driver:"c:\Users\Dillon Feng\Desktop\CloneDeployPE Builder-1.2.1\CloneDeployPE Builder-1.2.1\Optional\Drivers\WinPE 10 x64" /Recurse /ForceUnsigned

    There are also some errors in the dism.log like:
    DISM DISM Provider Store: PID=9668 TID=13008 Failed to load the provider: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    Finally, it complains:
    DISM DISM FFU Provider: PID=9668 TID=13008 [C:\Users\DILLON~1\AppData\Local\Temp\WinPE] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
    [9668] [0x80070002] FIOReadFileIntoBuffer:(1381): System can not find files
    [9668] [0xc142011c] UnmarshallImageHandleFromDirectory:(641)
    [9668] [0xc142011c] WIMGetMountedImageHandle:(2897)
    2018-06-08 15:22:15, Info DISM DISM WIM Provider: PID=9668 TID=13008 [C:\Users\DILLON~1\AppData\Local\Temp\WinPE] is not a WIM mount point. - CWimMountedImageInfo::Initialize
    2018-06-08 15:22:15, Info DISM DISM VHD Provider: PID=9668 TID=13008 [C:\Users\DILLON~1\AppData\Local\Temp\WinPE] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
    2018-06-08 15:22:15, Info DISM DISM FFU Provider: PID=9668 TID=13008 [C:\Users\DILLON~1\AppData\Local\Temp\WinPE] is not recognized by the DISM FFU provider. - CFfuImage::Initialize
    2018-06-08 15:22:15, Info DISM DISM Imaging Provider: PID=9668 TID=13008 The provider FfuManager does not support CreateDismImage on C:\Users\DILLON~1\AppData\Local\Temp\WinPE - CGenericImagingManager::CreateDismImage
    2018-06-08 15:22:15, Info

    Do you know how I can fix this issue?

  • BTW, when i finished the WINPE build, i can see the drivers directory in options are empty.
    C:\Users\Dillon Feng\Desktop\CloneDeployPE Builder-1.2.1\CloneDeployPE Builder-1.2.1\Optional\Drivers\WinPE 10 x64

  • The drivers directory is supposed to be empty. That is where you add your own drivers if necessary. Someone told me once the build fails if any of the directories have a space in them.

    Try making a folder directly on 😄 Maybe something like c:\pebuilder and put the scripts directly there.

  • You know what, it's quit strange. I just changed the script to a new directory and even the same error is still there. It looks like it's working now. so magic. But originally, I also try to delete all of the other directory in the "CloneDeployPE Builder-1.2.0", but it is still no lucky. I suspect it is caused by the space in the "Clone...." directory.

    Thanks a lot for your timely support.

  • I am almost creasy today. I can not make the PE build again. It is still the same errors like the begining and I try to create a new directory and put the scripts there but still no lucky. I still can not figure out why I ever made the build ok on June 9. Confusing. the good thing is I have a good one, the bad thing is I don't know how to make a good one again.

  • Eventually, I figured out the root cause. Once I copy the scripts to a new folder I also need to copy the options\extra files. Now it is ok to boot into WINPE and with clonedeploy login. But it looks like there is no 3 options (boot to local, clonedeploy, shell) like linux in the beginning of winpe boot menu.

  • Winpe doesn't have the boot options, it always boots to winpe.

  • The issue is once I finished the deploy via winpe, the system will reboot to WinPE environment again even I set the image to shutdown. I suppose once the system had been deployed it should go into the deployed environment be default. (Just like linux the default option will be booted to local, with that I don't even need to plug out the network cable after deployment.

  • Pxe should not be your first startup option.