After move to current branch we have got many thing as easy to drive like os upgrade or manage device with CMG or CDP but still sometimes upgrade environment may causing one and other issue. I will be sharing incident and root cause that once we have moved 1710 to 1802 all the PXE imaging is getting failed error code 0x80070057.
Error on  SMSTS.LOGS
The execution of the group (Apply Driver Packages) has failed and the execution has been aborted. An action failed.  Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Apply LatitudeE6 Driver Package x64. Execution of task sequence failed. The parameter is incorrect. (Error: 80070057; Source: Windows)  



Solutions provided. 
Point 1: We have upgraded ADK Click Here to download ADK 
Point 2:  Validate whether boot image is upgraded as per version in console found boot image is not upgraded as needed and one of the One driver Apply LatitudeE6 Driver Package x64. related folder was deleted in environment During the 1802 upgrade, Boot image upgrade was not successful.  Hence Drivers reference to boot image was missing due to new option on  SCCM  available  "Install driver package via running DISM with recurse option".
Point 3: Created new boot image. If we have integrated with MDT you can do with wizard click here for more details but if you have not integrated with MDT you can follow below steps.
Go to ADK Deployment toolkit Right Click deployment and Imaging Tools Environment Click on Run As administrator.

Command prompt will open:

Type below three command one by one or based on Image needed.
COPYPE.CMD x86 c:\WINPE86\
COPYPE.CMD amd64 c:\WINPE64\
COPYPE.CMD arm c:\WINPEARM\
Below is screen shot for reference.
Type command COPYPE.CMD amd64 c:\WINPE64\  Press Enter 

Once command executed you will see below screen:

Note: Boot image for x64 has been created now we can go to given path and import to SCCM.
Boot.wim is located inside Media directory Sources  BOOT.WIM


Point 4: Once new boot image created and copy to the source of the all the image package and import to console.
Point 5: Once Boot image copied import all the drivers which are available on old boot image.
Point 6: After map actual production task sequence to the new created boot image and deployment went smooth as normal. 
Reference:  Above issue have been identify by vendor and it has been discussed Click Here and Here for details talks.

Happy learning!!!

Haresh Hirani
Email: [email protected], [email protected]
Facebook https://www.facebook.com/Hiraniconfigmgr-120189361980772/
Follow us: https://www.linkedin.com/in/hiraniconfigmgr 
Twitter: https://twitter.com/hiraniconfigmgr