1 Reply Latest reply on May 18, 2017 4:00 PM by Peteski

    Windows 10 Imagex Injectscripthandler fails - no C:\Windows\Panther dir

    Peteski Apprentice

      I'm just starting out with provisioning and decided to start with Win10 and Imagex.

       

      Provisioning sure is fun but now I'm stuck on InjectScriptHandler_x64.exe trying to copy my unattend file to the C drive after the image was successfully loaded with imagex. The unattend file downloads to x:\LDProvision just fine but there is no C:\Windows\Panther directory which of course causes the template to fail.That's a new one for me- I've never seen a lack of a panther directory after an image load.

       

      Has anyone run into this before? I have googled a bit and didn't come up with anything.

       

      thanks

       

      Pete

        • 1. Re: Windows 10 Imagex Injectscripthandler fails - no C:\Windows\Panther dir
          Peteski Apprentice

          I was able to determine what was going on: Windows 10 does not have a c:\windows\panther directory by default but it does get created later after the OS is deployed and the system boots the first time. Panther was also was created in c:\windows\system32\sysprep.

           

          So when building a deployment template to inject your unattend.xml file into the proper place so that Windows 10 processes it, the proper directory is c:\windows\system32\sysprep. (different from windows 7 where it is in c:\windows\panther)

           

          When windows runs through its first-boot phases it will copy the unattend.xml file only to C:\windows\panther and leave the one in the sysprep directory that you injected. So if you want to remove it, you have to delete it from both places.

           

          I also ran into an unrelated issue where the CTOS step was failing with "not able to determine sysprep drive". This will happen if you either a) did not use a BCDboot step to set your up your boot partition and make it active. b) no pause /action between the BCDBoot and CTOS. The CTOS steps happens so fast it tries to start before the partition is ready. A 5 sec wait fixes that.

           

          Enjoy.