Stand by...

 Print This Post

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.

This post was written by microtom and has 30,980 views in total

(13 votes, average: 4.62 out of 5)
Loading ... Loading ...

12 Comment(s). Add a comment or Trackback

  • microtom  10:12 Feb 28, 2013 

    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.

  • HayDOS  01:28 Feb 28, 2013 

    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  10:34 Feb 06, 2013 

    Hello HayDOS,
    No, not necessarily MDT only. Without using MDT, this would be the AutoUnattend.xml. It is used to control the Configuration Passes of Windows.
    You’ll have to use Windows System Image Manager (From WAIK or ADK) to configure it properly (you can also do this manually, but SIM is more convenient)
    With MDT, this file is located here “yourdeploymentshare\Control\TaskSequenceID\unattend.xml” and will be re-generated with values you specify in the CustomSettings.ini, the Deployment Wizard etc.

    Here’s some more information on that:
    And a nice Video:

    How are you deploying Windows?

  • HayDOS  01:22 Feb 06, 2013 

    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?

  • Rajeev  17:54 Sep 14, 2011 

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

  • Band  16:31 Jun 30, 2011 

    Works like a charm !!

  • Ross  01:06 Jun 09, 2011 

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

  • Micky  14:37 Jun 07, 2011 

    The same is true for Windows 2008 R2 Service Pack 1

  • microtom  18:03 Jun 03, 2011 

    Hey Adriano

    What is the path to the unattend.xml file you were checking?


  • Adriano  15:38 Jun 03, 2011 

    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?

  • microtom  17:41 Mar 10, 2011 

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

  • JJ  14:59 Mar 10, 2011 

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

Leave a comment ↓

Welcome back, (change)