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 responses to Windows 7 SP1: Windows could not apply unattend settings during pass [offlineServicing]

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?

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?

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?

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.

Leave a Reply