none
Error : Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [Specialize].

    Question

  • Hi,


    I am attempting to install vista enterprise VL with WDS. I have set up WDS, created a capture image, captured an image, and created an answer file. When I attempt to install with the image an answer file, I receive the following message.

    Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [Specialize].


    I have tried with different cd's and even with Windows 2008 i have the same problem.

    OS= Windows 2003 Sp2 + WDS + MDT

    REgards
    Sharath

    Wednesday, July 09, 2008 12:10 PM

Answers

  • I had this same problem installing Windows Server 2008 and found the problem to be the computer name in AD. I removed the computer name and ran the intall again. It worked form me. 

    Tuesday, September 30, 2008 4:13 PM

All replies

  • You will need to look in the c:\windows\panther\unattendgc\setupact.log or setuperr.log to determine exactly what is failing in your unattend.xml

     

    Wednesday, July 09, 2008 11:34 PM
  • Thanks for the reply.

     

    After installing the client from the WDS & MDT server. It pops the above error and does not allow me to get into the machine. So checking this logs is not possible. Any other guidelines?

     

    Thursday, July 10, 2008 3:12 AM
  • Hi,

     

    I just connected the existing Windows 2008 HDD to another machine and got the files...

     

    Setupact.log

     

    2008-07-09 05:49:21, Info                         [windeploy.exe] ------------------------------------------------
    2008-07-09 05:49:21, Info                         [windeploy.exe] WinDeploy.exe launched with command-line []...
    2008-07-09 05:49:22, Info                         [windeploy.exe] Setup has not completed, adding pending reboot.
    2008-07-09 05:49:22, Info                         [windeploy.exe] UnattendSearchExplicitPath: Found unattend file at [C:\Windows\Panther\unattend.xml]; examining for applicability.
    2008-07-09 05:49:22, Info                         [windeploy.exe] UnattendSearchExplicitPath: Found usable unattend file for pass [oobeSystem] at [C:\Windows\Panther\unattend.xml].
    2008-07-09 05:49:22, Info                         [windeploy.exe] Found unattend file: [C:\Windows\Panther\unattend.xml]
    2008-07-09 05:49:22, Info                         [windeploy.exe] Found generalization state [0x4], setup.exe completion flag [False] --> launching setup.exe.
    2008-07-09 05:49:22, Info                         [windeploy.exe] Launching [C:\Windows\system32\oobe\setup.exe]...
    2008-07-09 21:17:31, Info                         [windeploy.exe] Process exited with exit code [0x1f]
    2008-07-09 21:17:31, Error                        [windeploy.exe] Setup.exe failed, returning exit code [0x1f]
    2008-07-09 21:17:31, Error                        [windeploy.exe] Failure occured during online installation.  Online installation cannot complete at this time.; hr = 0x80004005
    2008-07-09 21:17:31, Info                         [windeploy.exe] Flushing registry to disk...
    2008-07-09 21:17:31, Info                         [windeploy.exe] Flush took 172 ms.
    2008-07-09 21:17:31, Info                         [windeploy.exe] WinDeploy.exe exiting with code [0x80004005]

     

    setuperr

     

     

    2008-07-09 21:17:31, Error                        [windeploy.exe] Setup.exe failed, returning exit code [0x1f]
    2008-07-09 21:17:31, Error                        [windeploy.exe] Failure occured during online installation.  Online installation cannot complete at this time.; hr = 0x80004005

     

     

    Thursday, July 10, 2008 4:03 AM
  • That looks like the setupact.log and setuperr.log from c:\windows\panther.  You need the one from c:\windows\panther\unattendgc.  You should be able to boot up into Windows PE and access the disk.

     

    Thursday, July 10, 2008 11:05 PM
  •  

    Hi Tim,

     

    The previously posted log is from "c:\windows\panther\unattendgc"

     

    If you want me to post the logs from here "c:\windows\panther\"

     

    I can do so?

     

     

    Friday, July 11, 2008 5:04 AM
  •  

    Sure it might be helpful.
    Friday, July 11, 2008 11:09 PM
  • Tim

     

    The log size is very huge

     

    I think here max of 50000 letters can be placed...

     

    Please suggest....
    Saturday, July 12, 2008 12:34 PM
  •  

    Anyone has a solution for this please...
    Sunday, July 27, 2008 2:29 PM
  • I had this same problem installing Windows Server 2008 and found the problem to be the computer name in AD. I removed the computer name and ran the intall again. It worked form me. 

    Tuesday, September 30, 2008 4:13 PM
  • I had same error "Process exited with exit code [0x1f]" and computer name was set in customsettings.ini, taken from vbs script which take Application preselected based on Company internal SQL server with orders. After below lines has been removed all went OK.

    cs.ini:

    UserExit=jApplications.vbs

    ComputerName=#jComputerName#

    Applications001=%BBAPP001%

    ...

     

    Still investigate, any thought are welcome.

    Thursday, September 29, 2011 9:17 AM
  • FYI

    customsettings.ini has been changed to:

    UserExit=jApplications.vbs

    OSDComputerName=#jComputerName#

    Applications001=%BBAPP001%

    ...

    Now works fine, Application are correctly preselected and Computer name is set as should be, no any errors.

    Thursday, September 29, 2011 10:43 AM
  • I just noticed the very same issue. But in my mase case it was the following.

    In WDS I have configured the Client Naming Policy:

    From: %61Username%#
    To: WDS-%61Username%#

    This results in a hostname like WDS-Administrator1. Apparantly this error occurs because the hostname is too long. Although it is created in Active Directory without any problem, the unattend script halts. After correcting the Client Naming Policy everything was back to normal.


    Boudewijn Plomp, BPMi Infrastructure & Security




    Thursday, October 31, 2013 12:52 PM