none
Windows 7 TS Install Software Updates failing 80070490 8007047f 800f0805

    Question

  • I have a task sequence that's failing on the Software Updates. I'm getting a few different errors in the CBS log but they don't seem to make sense to me.

    First off, I'm getting these errors. Now, before we start, I don't have any Vista files on this machine. The WIM ultimately came from a MSFT Win 7 SP1 disc.

    2012-04-19 11:32:16, Info                  CBS    WinVerifyTrust failed [HRESULT = 0x8007047f - ERROR_APP_WRONG_OS]

    2012-04-19 11:32:16, Error                 CBS    Failed to verify if mum file \\?\c:\40d7a35ce5a7644ff1\Sandbox\WUClient-SelfUpdate-Aux-TopLevel.cab\update.mum is vouched for by catalog \\?\c:\40d7a35ce5a7644ff1\Sandbox\WUClient-SelfUpdate-Aux-TopLevel.cab\update.cat. [HRESULT = 0x8007047f - ERROR_APP_WRONG_OS]

    These errors are followed by

    2012-04-19 11:32:16, Info                  CBS    Session: 30219849_4233735632 initialized by client WindowsUpdateAgent.

    2012-04-19 11:32:16, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

    Then later in the log, for several of the updates, I see:

    2012-04-19 11:32:22, Info                  CBS    Failed to get session package
    state for package: Package_1_for_KB2656356~31bf3856ad364e35~amd64~~6.1.1.1
    [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

    Now what makes no sense here is the ~amd64~ part. It's not an AMD machine and we have no AMD workstations in our environment.

    The updates hang on (Downloading x of x XX%) and I've already installed the KB2509007 hotfix, so that should eliminate that possibility.

    The only thing that I've seen thusfar in the WindowsUpdate.log file is the following:

    2012-04-19          11:32:15:882       2444       990         Misc         = Process: c:\40d7a35ce5a7644ff1\wusetup.exe

    2012-04-19          11:32:15:882       2444       990         Setup    Evaluating CBS package "c:\40d7a35ce5a7644ff1\WUClient-SelfUpdate-Core-TopLevel.cab"

    2012-04-19          11:32:15:992       2444       990         Handler                FATAL: UH: 0x8007047f: CreatePackage failed in CCbs::CreatePackage

    2012-04-19          11:32:15:992       2444       990         Setup    WARNING: Failed to evaluate applicability, will try to install anyway, error = 0x8007047F

    2012-04-19          11:32:15:992       2444       990         Setup    Evaluating CBS package "c:\40d7a35ce5a7644ff1\WUClient-SelfUpdate-ActiveX.cab"

    2012-04-19          11:32:16:007       2444       990         Handler                FATAL: UH: 0x8007047f: CreatePackage failed in CCbs::CreatePackage

    2012-04-19          11:32:16:007       2444       990         Setup    WARNING: Failed to evaluate applicability, will try to install anyway, error = 0x8007047F

    2012-04-19          11:32:16:007       2444       990         Setup    Evaluating CBS package "c:\40d7a35ce5a7644ff1\WUClient-SelfUpdate-Aux-TopLevel.cab"

    2012-04-19          11:32:16:038       2444       990         Handler                FATAL: UH: 0x8007047f: CreatePackage failed in CCbs::CreatePackage

    2012-04-19          11:32:16:038       2444       990         Setup    WARNING: Failed to evaluate applicability, will try to install anyway, error = 0x8007047F

    2012-04-19          11:32:16:038       2444       990         Setup    wusetup has finished.  Exit code is 47f. Reboot is NOT needed

    2012-04-19          11:32:33:599       268        7cc          Agent    WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013

    Any thoughts would be greatly appreciated.

    Thursday, April 19, 2012 5:46 PM

Answers

  • All Win 7 clients being imaged were failing, it wasn't just one.

    What ended up happening was that someone I work with had deployed the Office 2010 SP1 update to an empty collection and the updates that were getting caught up and failing the process (we found the GUIDs for the failing updates finally in WUAHandler.log and were able to track them back using a report that I created) were two updates that were superseded by Office SP1. Even though SP1 wasn't being advertised or installed, the update process still failed. The updates were yellow and I hadn't deleted them because as far as I knew, we weren't yet deploying SP1, which was sort of true as the deployment was pointing to an empty collection. Unfortunately the update process isn't the smartest and it caused the whole thing to hang and fail.


    • Marked as answer by WBrady1965 Tuesday, May 01, 2012 4:25 PM
    • Edited by WBrady1965 Tuesday, May 01, 2012 4:26 PM
    Tuesday, May 01, 2012 4:25 PM

All replies

  • It sounds like it can't find the update(s) and location(s). Did you check if the client is connected to a site, part of boundary, etc?

    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

    Thursday, April 19, 2012 7:23 PM
  • The client is getting some updates successfully and is showing a connecting to the WSUS server in WindowsUpdate.log and the site server in the smsts.log as well, so I don't think this is an issue.

    Friday, April 20, 2012 12:48 PM
  • Just one client failed?

    If so, you need to check this client to see if it is the issue on the client side.


    Sabrina

    TechNet Community Support

    • Marked as answer by Sabrina Shen Monday, April 30, 2012 5:40 AM
    • Unmarked as answer by WBrady1965 Tuesday, May 01, 2012 4:09 PM
    Thursday, April 26, 2012 9:31 AM
  • All Win 7 clients being imaged were failing, it wasn't just one.

    What ended up happening was that someone I work with had deployed the Office 2010 SP1 update to an empty collection and the updates that were getting caught up and failing the process (we found the GUIDs for the failing updates finally in WUAHandler.log and were able to track them back using a report that I created) were two updates that were superseded by Office SP1. Even though SP1 wasn't being advertised or installed, the update process still failed. The updates were yellow and I hadn't deleted them because as far as I knew, we weren't yet deploying SP1, which was sort of true as the deployment was pointing to an empty collection. Unfortunately the update process isn't the smartest and it caused the whole thing to hang and fail.


    • Marked as answer by WBrady1965 Tuesday, May 01, 2012 4:25 PM
    • Edited by WBrady1965 Tuesday, May 01, 2012 4:26 PM
    Tuesday, May 01, 2012 4:25 PM