locked
Error messages in lite touch installation of windows 7 RRS feed

  • Question

  • I originally asked this in the Windows 7 Installation, Setup, and Deployment forum but was told that this would be a better place to ask it.

    We've been running lite touch installation for a while now to deploy images out to our computers, but I added a load of update packages a couple of days ago through the deployment workbench and now I'm getting an error message whenever I try to reimage a copmuter.

    I've looked in the logs (specifically cbs_unattend.log) and this looks like this is the offending part, but it doesn't seem to relate to any of the packages I've recently added.

    2013-08-22 10:30:41, Error                 CSI    000013a2 (F) STATUS_CANNOT_DELETE #12584982# from Windows::Rtl::SystemImplementation::MarkFileDeletePending(...)[gle=0xd0000121]
    2013-08-22 10:30:41, Error                 CSI    000013a3@2013/8/22:18:30:41.453 (F) d:\w7rtm\base\wcp\sil\systemisolationlayer.cpp(346): Error STATUS_CANNOT_DELETE originated in function Windows::Rtl::SystemImplementation::MarkFileDeletePending expression: (null)
    [gle=0x80004005]
    2013-08-22 10:30:48, Error                 CSI    000013a4 (F) STATUS_CANNOT_DELETE #12584981# from Windows::Rtl::SystemImplementation::CDirectory::DeleteExistingFile(...)[gle=0xd0000121]
    2013-08-22 10:30:48, Error                 CSI    000013a5 (F) STATUS_CANNOT_DELETE #12584980# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::DeleteExistingFile(flags = (MissingFileIsOk|MarkDeletePending|OpenForBackup|DeleteIfReadOnly), oa = @0x254ea28->SIL_OBJECT_ATTRIBUTES {s:40; on:"locale.nls"; a:(OBJ_CASE_INSENSITIVE)}, disp = Invalid)
    [gle=0xd0000121]
    2013-08-22 10:30:48, Info                  CSI    000013a6 Error STATUS_CANNOT_DELETE while executing operation HardLinkFile on [l:338{169}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-i..nal-core-locale-nls_31bf3856ad364e35_6.1.7601.18015_none_c8df164cbfe48d47\locale.nls, \??\C:\Windows\System32\locale.nls"

    2013-08-22 10:30:49, Error                 CSI    000013a7 (F) STATUS_CANNOT_DELETE #12410901# from Windows::COM::CComponentStore::PendActiveTransaction(...)[gle=0xd0000121]
    2013-08-22 10:30:49, Error                 CSI    000013a8 (F) STATUS_CANNOT_DELETE #12410893# from Windows::COM::CComponentStore::ApplyTransactionNow(...)[gle=0xd0000121]
    2013-08-22 10:30:49, Error                 CSI    000013a9 (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #12410885# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Apply(...)[gle=0x80070005]
    2013-08-22 10:30:49, Error                 CSI    000013aa (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #8045700# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 96 (0x00000060), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x80070005]
    2013-08-22 10:30:49, Error                 CSI    000013ab (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #8045699# 162068724 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000060, pSink = NULL, disp = 0)
    [gle=0x80070005]
    2013-08-22 10:30:49, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateResolvePending
    2013-08-22 10:30:49, Error                 CBS    Exec: Failed to commit CSI transaction to execute changes. [HRESULT = 0x80070005 - E_ACCESSDENIED]

    If anyone has any ideas I'd be really grateful.

    Friday, August 23, 2013 10:42 AM

All replies

  • Installing many updates via the Packages node is just a pain, and it's not very reliable.

    Use a WSUS instead and the built-in WindowsUpdate action in the task sequence. Works every single time!

    The only "updates" I add to the packages node in general are hotfixes not available on WSUS, and language packs (unless installed as apps later on).

    / Johan


    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

    Saturday, August 24, 2013 12:42 PM
  • As I didn't set up the initial deployment image I'm not 100% sure about how to change it over, but will give it a go.

    Thanks

    Jimi

    Friday, August 30, 2013 8:11 AM