Windows 7 SP1: Windows could not apply unattend settings during pass [offlineServicing]

Home  >>  Microsoft Deployment Toolkit  >>  Windows 7 SP1: Windows could not apply unattend settings during pass [offlineServicing]

Windows 7 SP1: Windows could not apply unattend settings during pass [offlineServicing]

Using the Unattend.xml (e.g. while deploying with MDT 2010) can lead into the followig error after slipstreaming Service Pack 1 for Windows 7:
Windows could not apply unattend settings during pass [offlineServicing]

This might happen because the Foundation Package Version Number in your Unattend.xml file has not been adjusted automatically.
To fix this, find the following line in your Unattend.xml file (for MDT this is located under %DistributionShare%\Control\%TaskSequenceID%)

assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="6.1.7600.16385" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language=""

and change it to

assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="6.1.7601.17514" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language=""

You can get the correct version number by checking the properties of the Setup.exe in the Slipstreamed Windows 7 SP1 directory.

12 Comments so far:

  1. JJ says:

    I can’t find that line ind the %DistributionShare%\Control\%TaskSequenceID% folder…

  2. microtom says:

    Hey Jay, can you post your Unattend.xml File content here? @JJ

  3. Adriano says:

    Hi there,

    Having the same issue. Just download SP1 for Win 7, extracted the files with /extract switch, performed a “Package Import”, pointed to the folder with all the extracted SP1 files, imported ok.
    Now performing a deployment, getting the same error “Windows could….”.
    Looked for the statements you mention in the unattend.xml and they ara not there.

    What am I missing?

  4. Micky says:

    The same is true for Windows 2008 R2 Service Pack 1

  5. Ross says:

    Hey thanks alot. Simple version change and we can now successfully deploy Win7SP1 using our existing XML.

  6. Band says:

    Works like a charm !!

  7. Rajeev says:

    it really saved my 3-4 hours of re-creating the answer file :)

  8. HayDOS says:

    @microtom
    Same issue as JJ.
    Which Unattend.xml are you referring to?
    – WDSClientUnattend
    – ImageUnattend
    Noone of these contain the lines you are referring to.
    I assume this is for MDT only?

  9. HayDOS says:

    @microtom
    Thanks for the reply TinyTim! JK MicroTom, I so missed my calling as a comedian ;-)

    It seems in my case the OfflineServicing error was due to trying to deploy a 2 partition image. The data partition has now been has been “Appended” via imagex & deploys OK however machines fail to join the domain although pre-staged naming is working fine. Machines end up in a netBIOS domain name Workgroup.even though the WDS server & user account have write permissions on computer objects. I miss the simplicity of Ghost although I appreciate the benefits M$ wim deployment once one has waded through the Swamp of Sadness that is WDS Config… where’s my Luck Dragon!?
    Thanks again Tom.

    • microtom says:

      Hey HayDos
      Ghosting is ugly man! :)
      The problem sounds a bit strange to me.. have you checked %systemroot%\debug\Netsetup.log?
      There must be a simple explanation.
      Tom

Leave a Reply