Error Win7 update: Code 800F081F

Page 1 of 2 12 LastLast

  1. Posts : 8
    64
       #1

    Error Win7 update: Code 800F081F


    Hi NoelDP,

    When Im trying to run Windows updates to search for new updates, Im getting the same error over again:
    Code 800F081F - There is a unknown error in Windows update.

    To fix it, I tried all sorts of things, but without luck, like:
    - Run the System Update Readiness tool (CheckSur.exe), deleting updates, manual installing updates, recovery points.

    It is a Windows 7, Home Premium with SP1, 64 bit, HP Laptop.

    My CheckSUR.txt:

    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.22471
    Package Version 26.0
    2015-02-03 14:08

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store
    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_6.1.7601.18540_en-us_d29f327284d9f088.manifest amd64_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_6.1.7601.18540_en-us_d29f327284d9f088

    Summary:
    Seconds executed: 3214
    Found 1 errors
    CSI Manifest Failed Catalog Check Total count: 1

    Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_6.1.7601.18540_en-us_d29f327284d9f088.manifest

    ------------------------------------
    My CheckSUR.persist.txt:


    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.22471
    Package Version 26.0
    2015-02-03 14:08

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store
    (f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_6.1.7601.18540_en-us_d29f327284d9f088.manifest amd64_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_6.1.7601.18540_en-us_d29f327284d9f088

    Summary:
    Seconds executed: 3214
    Found 1 errors
    CSI Manifest Failed Catalog Check Total count: 1

    Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_6.1.7601.18540_en-us_d29f327284d9f088.manifest



    Really hope you can help!
    Cheers
      My Computer


  2. Posts : 8
    64
    Thread Starter
       #2

    The update which is failing is: windows update-agent 7.6.7600.320
    Perhaps there is way to download this update manually?
    The CBS files are growing I see, I have now put the latest here: WeTransfer (.RAR 31 MB)

    Thanks
      My Computer


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

    I've uploaded a file - aqtaa.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 aqtaa in the same place.
    Open this folder - there should be one folders inside it (Manifests)

    Copy the content of the manifests folder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

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

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


  4. Posts : 8
    64
    Thread Starter
       #4

    Thanks for the package NoelDP, all the steps are done (had to create the Winsxs directory myself)
    Hotfix KB947821 was installed successfully.

    The new CheckSur files are here: WeTransfer

    Hope it can be solved!
      My Computer


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

    The good news is that CheckSUR is now happy.
    The bad news is that the Update Agent update is still not installing (as you probably noticed)

    Here's the errors from the latest attempt to install it...
    Code:
     Line 366319: 2015-02-05 14:20:04, Error                 CBS    Exec: Failed to pre-stage package: WUClient-SelfUpdate-Core-UIComp~31bf3856ad364e35~amd64~nl-NL~7.6.7600.256, file: wuaueng.dll.mui, source: \\?\C:\Windows\Servicing\Packages\amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.4.7600.226_en-us_9b0c2b484893a318\wuaueng.dll.mui, sandbox: (null) [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
     Line 366323: 2015-02-05 14:20:04, Error                 CBS    Failed to pre- stage package: WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
     Line 366326: 2015-02-05 14:20:04, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
    It looks to me as if the problem is that it's attempting to install one language, while the system is actually running a different one!

    The actual causative error here appears to be this one...
    Code:
    2015-02-05 14:20:04, Info                  CBS    Calling client to resolve source, cannot find file 'wuaueng.dll.mui' at path: \\?\C:\Windows\Servicing\Packages\amd64_microsoft-windows-w..ient-core.resources_31bf3856ad364e35_7.4.7600.226_en-us_9b0c2b484893a318\wuaueng.dll.mui
    I have no idea why it should be looking in that location for that file - it should be elsewhere...


    The problem is that this file doesn't exist after the system has been updated once - to install the version that is itself being updated now.
    I have no real idea how to work around this at present
    I suspect that it's a registry problem - but it could be very widespread...
    I don't know if this will tell me anything, but...

    I need to have a look at your COMPONENTS registry hive

    Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.
      My Computer


  6. Posts : 8
    64
    Thread Starter
       #6

    Appreciate that you are helping me Noel. Here is the file

    I spent a lot of time already on it and also tried many anti-malware progs to get it solved. It is the laptop of my parents with Dutch set as the language in Win7..

    Cheers again
      My Computer


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

    You appear to have both English and Dutch installed - Which edition of Windows is this machine? (Home Premium/Pro/Ultimate?)
      My Computer


  8. Posts : 8
    64
    Thread Starter
       #8

    That is indeed possible, it is Win7 Home Premium with SP1..
      My Computer


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

    The problem is that it isn't legal - Ultimate edition is the only one which has the capability of running more than one language, legally.
    You need to uninstall English, and with luck, this will restore the proper functionality.
    It seems that the installation method/hack missed out either a few registry entries, or a few files (or both) with the results that we're now seeing.
      My Computer


  10. Posts : 8
    64
    Thread Starter
       #10

    Okay.. well we are getting to the bottom of the problem.

    I had a look at the windows updates (the overview in installed programs - control panel), but I cannot tell which update is Dutch and/or English. So I don't know which ones I can remove.. Any idea how to remove only the English ones?
    Or perhaps remove and reinstall SP1, however I have read that it is not possible if the laptop comes with SP1 preinstalled, which was the case I believe.

    Or the long shot, I can upgrade the machine to Ultimate or Win8. You reckon that will solve this issue?

    Thanks!
      My Computer


 
Page 1 of 2 12 LastLast

  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 07:06.
Find Us