Deployment Solution

Hello all. I'm trying to install a win7 OS in PXE. My installation Job includes a Partition task that creates 1 partition as primary and then goes to scripted installation of the OS. Partition completes without any issues apparently. Then in the ClientSOI task things go alright upto where it maps the "package delivery" folder to Z drive and. Then, it runs "Z:\sources\setup.exe" with the command line: /noreboot /unattend:X:\<CUSTOM_ANSWER_XML>. I'm using WinPE 10.0

This returns the following: "Unable to create new process". Value of Windows error code = 6 and message is " The handle is invalid."

Anyone face this issue on 8.1 yet?

Try to map the same windows share to Z drive and try to execute the setup.exe without any switches, does it work?

A wild guess would be that we are either in 64 or 32 bit WinPe and try to execute the setup.exe of vice versa.

Try to map the same windows share to Z drive and try to execute the setup.exe without any switches, does it work?

A wild guess would be that we are either in 64 or 32 bit WinPe and try to execute the setup.exe of vice versa.

Thanks for the reply. I have ensured that we are not mixing up the 32 v 64 arch. I am new to using WinPE and the symantec solution in general. I am wondering if the WinPE being 10.0 has any bearing on the fact that I'm trying to setup a Win7? 

I tried mapping the network drive manually. From the attached screenshot, Z:\sources\ exists, but there's no setup.exe. Also I thought the line that says "OS setup is Windows XP/2k3..." was interesting. Please let me know if this gives you any ideas with what might be going on. Thanks.

Tried replying to you @Indrek_K, but can't seem to find the reply anywhere, so posting it as a comment as well.

I have ensured that I'm using x86 setup files and x86 (only) on the WInPE setup. I'm new using WinPE and the Symantec solution in general. I'm wondering if WinPE 10.0 has any affect on the fact that I"m trying to setup a Win7 OS? Thanks.

If there is no setup.exe then that is most likely the cause of our problem.

The package is corrupt to some level.

Easiest way would be to re-import the OS source package to DS.