Win 7 64bit SP 1 installation error - Code 800F0818

[probuddha]

Hello

This is my first post at the sevenforums.com even though I have been a lurker for several years.

I upgraded my PC and installed Win 7 64bit professional (earlier was using 32 bit) and proceeded with the automatic updates. I ran into occasional errors from time to time but mostly they were due to connectivity issues (undersea cable cut...duh!) but those were resolved on repeated attempts

Now, it seems I am stuck on the Windows 7 SP 1 update for x64-based systems. I have tried innumerable times to get it installed, but half way during the installation, it would stop and throw me this error - Code 800F0818

I read some old threads in this forum and ran the SFC Scan and it came out clean. My PC also has just been formatted and adequately secured by Avast and MBAM and now I am in the process of downloading the System Update Readiness Tool

Please advise on how to proceed from here on.


Thank you very much!

 

[NoelDP]

http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html

 

[probuddha]

Thanks Noel. I will wait for the System Readiness Tool to complete download and then get back with all the relevant results and logs

 

[probuddha]

Here is the required information

Error Code 800F0818

CBS Folder attached

Let me know if you need any further information


Thanks!

 

[NoelDP]

Unavailable repair files:
 servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat

This relates to the following errors in the CBS log (but not in the SFC scan)

2013-03-31 02:41:22, Info                  CBS    Archived backup log: C:\Windows\Logs\CBS\CbsPersist_20130330211111.cab.
2013-03-31 02:41:39, Info                  CBS    Mark store corruption flag because there is a mismatch between package identity and its content on package: Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11. [HRESULT = 0x00000000 - S_OK]
2013-03-31 02:41:39, Info                  CBS    Identity mismatch: Specified Identity: Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11, actual package Identity: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385 [HRESULT = 0x800f0818 - CBS_E_IDENTITY_MISMATCH]
2013-03-31 02:41:39, Info                  CBS    Failed to resolve package [HRESULT = 0x800f0818 - CBS_E_IDENTITY_MISMATCH]
2013-03-31 02:41:39, Info                  CBS    Failed to populate children. [HRESULT = 0x800f0818 - CBS_E_IDENTITY_MISMATCH]

there is also a similar error - for KB976932for which there is no related error in CheckSUR

I'll provide a fix protocol for the KB2685811 error first - and we'll see how that works before attempting to fix the KB976932 error.


I've uploaded a file - pbdaa.zip - to my SkyDrive at Noel's SkyDrive
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 pbdaa in the same place.
Open this folder - there should be one folders 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.

 

[probuddha]

Hi Noel

The log files are attached.

Thank you so much

 

[NoelDP]

Hmm - something went wrong there - the errors are still present.

Please run the following command - it may give us a clue.

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

post the results

 

[probuddha]

C:\>DIR C:\Windows\Temp\CheckSur\Servicing\Packages
 Volume in drive C has no label.
 Volume Serial Number is 56E0-F1FC

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

01/04/2013  02:39 PM    <DIR>          .
01/04/2013  02:39 PM    <DIR>          ..
17/08/2012  06:44 AM             7,388 package_for_kb2685811_rtm~31bf3856ad364e3
5~amd64~~6.1.1.11.cat
17/08/2012  06:37 AM            54,402 package_for_kb2685811_rtm~31bf3856ad364e3
5~amd64~~6.1.1.11.mum
               2 File(s)         61,790 bytes
               2 Dir(s)  46,387,027,968 bytes free

 

[NoelDP]

Ah.
I suspect I know what the problem is - there's a registry error, rather than a file error.
This will take me a little time to track down and test.

If you don't hear from me by this time tomorrow, shout!

 

[probuddha]

Sure - thanks a lot for your help so far Noel

 

[probuddha]

Hey Noel

Any update on this?

Thanks

 

[NoelDP]

Not yet - I got side-tracked (Sorry!).
Top of the list, now!

 

[NoelDP]

Hmmm - I think this may tell us something.

Please run the following command, and post the results.

REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385" /S
 
.

 

[probuddha]

Here you go:-

C:\>REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Comp
onent Based Servicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad36
4e35~amd64~~6.1.7600.16385" /S

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1
.7600.16385
    InstallClient    REG_SZ    DISM Package Manager Provider
    InstallName    REG_SZ    Microsoft-Windows-Foundation-Package~31bf3856ad364e
35~amd64~~6.1.7600.16385.mum
    InstallLocation    REG_SZ    \\?\X:\Packages\
    CurrentState    REG_DWORD    0x70
    SelfUpdate    REG_DWORD    0x0
    Visibility    REG_DWORD    0x1
    InstallTimeHigh    REG_DWORD    0x1ca0440
    InstallTimeLow    REG_DWORD    0x249c687d
    InstallUser    REG_SZ    S-1-5-18
    Trusted    REG_DWORD    0x1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1
.7600.16385\Owners
    Microsoft-Windows-UltimateEdition~31bf3856ad364e35~amd64~~6.1.7600.16385
REG_DWORD    0x20040
    Microsoft-Windows-EnterpriseEdition~31bf3856ad364e35~amd64~~6.1.7600.16385
  REG_DWORD    0x20000
    Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~6.1.7600.16385
    REG_DWORD    0x20070
    Microsoft-Windows-HomePremiumEdition~31bf3856ad364e35~amd64~~6.1.7600.16385
   REG_DWORD    0x20000
    Microsoft-Windows-HomeBasicEdition~31bf3856ad364e35~amd64~~6.1.7600.16385
 REG_DWORD    0x20000
    Microsoft-Windows-StarterEdition~31bf3856ad364e35~amd64~~6.1.7600.16385    R
EG_DWORD    0x20000

 

[NoelDP]

Hmmm - maybe I'm reading it the wrong way around....

try this one...

REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11"
 
.

 

[probuddha]

C:\Windows\system32>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Co
mponent Based Servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd6
4~~6.1.1.11"

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11
    InstallClient    REG_SZ    WindowsUpdateAgent
    InstallName    REG_SZ    Microsoft-Windows-Foundation-Package~31bf3856ad364e
35~amd64~~6.1.7600.16385.mum
    InstallLocation    REG_SZ    \\?\C:\Windows\Servicing\Packages\
    CurrentState    REG_DWORD    0x40
    SelfUpdate    REG_DWORD    0x0
    Visibility    REG_DWORD    0x2
    Trusted    REG_DWORD    0x1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
vicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11\Owner
s

 

[NoelDP]

Very strange - I wonder how that could have happened??

We need to change permissions on that key, and then correct the error.
Unfortunately, the registry is a pain to change permissions in, so we have to do it manually.

Please first create a System Restore point - in case things go wrong!

Now open Regedit
Navigate to the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\
key and find the
Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11
key, and right-click on it

(note: accept warnings as appropriate)
Select Permissions
Click on the Advanced button
Click on the Owner tab, and highlight Administrators
click Apply
put a tick in the 'Replace owner...' box, and click Apply
Click on the Permissions tab
Highlight the Administrators entry, and click Edit
put a tick in the Allow/Full control box, and click OK
put a tick in the 'Replace all child...' box, and click OK out (twice)
Close Regedit

In an Elevated Command Prompt, run the following command

REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11" /v InstallName /t REG_SZ /d Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
 
.

then reboot, and run another CheckSUR scan.

 

[probuddha]

Unable to find Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11 in the specified registry location

Screenshot attached

Thanks

 

[probuddha]

Oh okay...found it...editing it now

 

[probuddha]

Hi Noel

I followed your instructions but found that the Allow/ Full Control boxes in the Administrators entry were already checked and grayed out

Attached are the updated logs


Thanks