Yep... Its definately fixed now... :thumbsup: But we still have an issue, this time it seems, like something is wrong with produced file: Relevant part of DISM.log 2011-10-02 03:35:59, Error DISM DISM Unattend Manager: PID=2708 ------Unattend setting error / warning------ - CUnattendManager::UnattendDumpSetting 2011-10-02 03:35:59, Error DISM DISM Unattend Manager: PID=2708 Error code = 0x800705b9 - CUnattendManager::UnattendDumpSetting 2011-10-02 03:35:59, Info DISM DISM Unattend Manager: PID=2708 File path = [D:\Temp\Autounattend.xml] - CUnattendManager::UnattendDumpSetting 2011-10-02 03:35:59, Info DISM DISM Unattend Manager: PID=2708 Line number = 60 - CUnattendManager::UnattendDumpSetting 2011-10-02 03:35:59, Info DISM DISM Unattend Manager: PID=2708 Column number = 17 - CUnattendManager::UnattendDumpSetting 2011-10-02 03:35:59, Info DISM DISM Unattend Manager: PID=2708 -------------------------------------------- - CUnattendManager::UnattendDumpSetting 2011-10-02 03:35:59, Error DISM DISM Unattend Manager: PID=2708 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:374 - CUnattendManager::Apply(hr:0x800705b9) 2011-10-02 03:35:59, Error DISM DISM Unattend Manager: PID=2708 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:654 - CUnattendManager::InternalExecuteCmdLine(hr:0x800705b9) 2011-10-02 03:35:59, Error DISM DISM Unattend Manager: PID=2708 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:603 - CUnattendManager::ExecuteCmdLine(hr:0x800705b9)