Windows Server 2008 R2 - SP1 wont install - 0x800f0818


  1. Posts : 1
    Windows 7 64bit
       #1

    Windows Server 2008 R2 - SP1 wont install - 0x800f0818


    Hello out there!
    A few Days ago, i installed a "fresh" Windows 2008 R2 Server standard and waited a long time for all those updates out there.

    Now my little HP Microserver NL 40 is stucked with the SP1 Package!

    What i've already tried:

    Checkdisk - No Errors
    Check Windows Files - No Errors

    Then ran the "Windows6.1-KB947821-v32-x64" file and loked into the error Logs.

    The CheckSUR.persist File:

    Checking System Update Readiness.
    Binary Version 6.1.7601.22471
    Package Version 23.0
    2014-04-16 14:26

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.mum Expected file name Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~de-DE~6.1.7600.16385.mum does not match the actual file name

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 1382
    Found 1 errors
    CBS MUM Corrupt Total count: 1

    Unavailable repair files:
    servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.mum
    servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.cat
    I found those Errors also in the CheckSUR File

    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.22471
    Package Version 23.0
    2014-04-16 14:26

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs
    (f) CBS MUM Corrupt 0x00000000 servicing\Packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.mum Expected file name Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~de-DE~6.1.7600.16385.mum does not match the actual file name

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 1382
    Found 1 errors
    CBS MUM Corrupt Total count: 1

    Unavailable repair files:
    servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.mum
    servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.256.cat
    There are a few hint's out there to repair "broken" Updates but without knowing which update these files belong to, its impossible to fix!
    The Errorlist is not too long, so i hope someone can help me without spending to long of his time?
    Last edited by Revox; 16 Apr 2014 at 09:42.
      My Computer


  2. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #2

    The affected update here is one which isn't publicly (officially) available - it's the Windows Update Agent update.

    This looks to me rather as if you've already attempted a fix, and it's failed because you simply renamed an existing file?

    Let's see if the standard fix works - but we may have to get creative.


    I've uploaded a file - rvxaa.zip - to my OneDrive at Noel's OneDrive

    Please download and save it.

    Right-click on the downloaded file, and select Extract all…

    Extract to the default location - which will create a new folder rvxaa in the same place.

    Open this folder - there should be one folder inside it ( Packages)



    Copy the content of the Packages folder to the folder

    C:\Windows\Temp\CheckSur\Servicing\Packages




    Now run the CheckSUR tool again (it may take a while)



    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

    Then,


    SFC -System File Checker - Instructions

    Click on Start > All Programs > Accessories

    Right-click on the Command Prompt entry

    Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

    At the Command prompt, type

    SFC /SCANNOW

    and hit the Enter key



    Wait for the scan to finish - make a note of any error messages - and then reboot.



    Upload the CBS.log file (compressed, please!) to your reply - if it's bigger than 8MB compressed, then upload it to a fileshare site, and post a link (preferably DropBox or OneDrive).
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:55.
Find Us