I got error during install: "Windows could not apply unattend settings during pass [offlineServicing]. " What's the problem?

It's possible to remove Unattend from image if applyed by "Full" method?

Edited September 12, 201212 yr by Edvardas Po

What Windows are you integrating the unattended file to? WinVista, Win7 or Win8?

Is it possible you can attach the unattended file? But please remember to change serial keys or personal information to XXXXX.

Win7x64 SP1

It's possible to remove Unattend from image if applyed by "Full" method? (as I understood from boot.wim ?)

my file:

<?xml version="1.0" encoding="utf-8"?>

<!--Created by Win Toolkit v1.4.0.70-->

<unattend xmlns="urn:schemas-microsoft-com:unattend">

<settings pass="windowsPE">

<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...fig/2002/State" xmlns:xsi="http://www.w3.org/20...hema-instance">

<UserData>

<AcceptEula>true</AcceptEula>

<ProductKey>

<Key>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</Key>

<WillShowUI>Always</WillShowUI>

</ProductKey>

</UserData>

</component>

<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...fig/2002/State" xmlns:xsi="http://www.w3.org/20...hema-instance">

<UserData>

<AcceptEula>true</AcceptEula>

<ProductKey>

<Key>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</Key>

<WillShowUI>Always</WillShowUI>

</ProductKey>

</UserData>

</component>

</settings>

<settings pass="specialize">

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...fig/2002/State" xmlns:xsi="http://www.w3.org/20...hema-instance">

<ProductKey>W9DBJ-QF796-RRKPG-VVQFW-JVDY3</ProductKey>

<ComputerName>server</ComputerName>

</component>

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...fig/2002/State" xmlns:xsi="http://www.w3.org/20...hema-instance">

<ProductKey>W9DBJ-QF796-RRKPG-VVQFW-JVDY3</ProductKey>

<ComputerName>server</ComputerName>

</component>

<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...fig/2002/State" xmlns:xsi="http://www.w3.org/20...hema-instance">

<SkipAutoActivation>true</SkipAutoActivation>

</component>

<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...fig/2002/State" xmlns:xsi="http://www.w3.org/20...hema-instance">

<SkipAutoActivation>true</SkipAutoActivation>

</component>

</settings>

<settings pass="oobeSystem">

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...fig/2002/State" xmlns:xsi="http://www.w3.org/20...hema-instance">

<Display>

<ColorDepth>32</ColorDepth>

</Display>

<OOBE>

<HideEULAPage>true</HideEULAPage>

<NetworkLocation>Work</NetworkLocation>

<ProtectYourPC>3</ProtectYourPC>

</OOBE>

<RegisteredOwner>GP</RegisteredOwner>

<RegisteredOrganization>Dature</RegisteredOrganization>

<UserAccounts>

<AdministratorPassword>

<Value>mukas_2044</Value>

<PlainText>true</PlainText>

</AdministratorPassword>

<LocalAccounts>

<LocalAccount wcm:action="add">

<Name>Master</Name>

<Group>Administrators</Group>

<Password>

<Value>mukas_2044</Value>

<PlainText>true</PlainText>

</Password>

<DisplayName>Master</DisplayName>

<Description>Master</Description>

</LocalAccount>

</LocalAccounts>

</UserAccounts>

<AutoLogon>

<Password>

<Value>mukas_2044</Value>

<PlainText>true</PlainText>

</Password>

<Enabled>true</Enabled>

<LogonCount>5</LogonCount>

<Username>Administrator</Username>

</AutoLogon>

<TimeZone>FLE Standard Time</TimeZone>

</component>

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.micro...fig/2002/State" xmlns:xsi="http://www.w3.org/20...hema-instance">

<Display>

<ColorDepth>32</ColorDepth>

</Display>

<OOBE>

<HideEULAPage>true</HideEULAPage>

<NetworkLocation>Work</NetworkLocation>

<ProtectYourPC>3</ProtectYourPC>

</OOBE>

<RegisteredOwner>GP</RegisteredOwner>

<RegisteredOrganization>Dature</RegisteredOrganization>

<UserAccounts>

<AdministratorPassword>

<Value>mukas_2044</Value>

<PlainText>true</PlainText>

</AdministratorPassword>

<LocalAccounts>

<LocalAccount wcm:action="add">

<Name>Master</Name>

<Group>Administrators</Group>

<Password>

<Value>mukas_2044</Value>

<PlainText>true</PlainText>

</Password>

<DisplayName>Master</DisplayName>

<Description>Master</Description>

</LocalAccount>

</LocalAccounts>

</UserAccounts>

<AutoLogon>

<Password>

<Value>mukas_2044</Value>

<PlainText>true</PlainText>

</Password>

<Enabled>true</Enabled>

<LogonCount>5</LogonCount>

<Username>Administrator</Username>

</AutoLogon>

<TimeZone>FLE Standard Time</TimeZone>

</component>

</settings>

</unattend>

Edited September 12, 201212 yr by Edvardas Po

Does you install work without an unattended file?

I'm not sure if it can be removed, worse case scenario is you can just extract a new boot.wim from an iso and just replace that file.

Does you install work without an unattended file?

I'm not sure if it can be removed, worse case scenario is you can just extract a new boot.wim from an iso and just replace that file.

if I will replace boot.wim in my AIO integrator prepared disk will it damage changes I made?

UPDATE

I made new disk with AIO Integrator with one difference: skipped Updates, added the same Unattend file, but with Quick method Onot Full).

Installed Win7x64 without problems.

So, looks like problem is with updates from Update Catalog (SoLoR)? I suggest that not adding Unattend file to the boot.wim in this situation isn't problem?

Edited September 12, 201212 yr by Edvardas Po

No, the majority, if not all of those changes are made to the install.wim.