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

[probuddha]

lol okay no issues...I'll wait for him to respond.

Thanks

 

[tom982]

Hi probuddha,

Before we continue, I would like a little more information about your system please. I know we've already had bits and bobs throughout this thread but I would prefer to work from fresh if that's okay

Export registry as hive

1. Click on the Start
   
   button and in the search box, type regedit.
2. When you see regedit on the list, right-click on it and select Run as administrator.
3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
   
   
4. Once selected, click File > Export....
5. Change the Save as type: to Registry Hive Files (*.*).
6. Name this file SideBySide (with no file extension) and save it to your Desktop.

1. Click on the Start
   
   button and in the search box, type regedit.
2. When you see regedit on the list, right-click on it and select Run as administrator.
3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
   
   
4. Once selected, click File > Export....
5. Change the Save as type: to Registry Hive Files (*.*).
6. Name this file CBSreg (with no file extension) and save it to your Desktop.

Upload a file to Dropbox

Note: If you prefer, the same techniques can be applied to your Skydrive however these instructions may not necessarily work for Skydrive.

1. If you haven't already created a Dropbox account, please do so Here
2. Although this procedure can be done directly through the website, it is much easier to do so via the Windows client which can be downloaded from the Dropbox website:
   
   https://www.dropbox.com/install
3. After you have downloaded and installed that, you should now see Dropbox in your Favourites box in Windows Explorer. This is the folder that will be synchronised with the Dropbox servers, anything that you wish to back up online can be put in here, but today we will be using it to transfer files.
   
   
   
4. To access your Dropbox folder, just click on the link in the top left hand corner of Windows Explorer (accessible from any location - Documents etc.). Alternatively, you can double click on the icon
   
   found in your system tray (next to the time). If you are still having issues locating this folder, unless otherwise specified, it can be found under this location: C:\Users\{Your username}\Dropbox
5. Copy all of the following files to the Public folder in your Dropbox:
   
   • C:\Users\{Your Username}\Desktop\SideBySide (it has no file extension)
   • C:\Users\{Your Username}\Desktop\CBSreg (it has no file extension)
   
   
6. Select all files by pressing Ctrl+A then right-click and select Send to > Compressed (zipped) folder
7. This will create a .zip
   
   file in your Public folder.
8. Right-click on this file and select Dropbox > Copy Public Link then Paste (Ctrl + V) this link into your next post for me please

Tom

 

[probuddha]

Hi Tom

Thank you so much for your detailed explanation.

I followed all your instructions but couldn't find the Dropbox > Copy Public Link option, so I selected Share Link instead and got this link.

https://www.dropbox.com/s/ur6igt1h0nqf36s/CBSreg.zip

Let me know if this helps


Thanks
Probuddha

 

[probuddha]

also FYI - I downloaded the windows6.1-KB976932-X64 file from Microsoft, but while running it got the same error (800F0818)

 

[tom982]

Hi probuddha,

Can you make sure that the file is in your Public folder before you try to copy the link please

When I click on your link I am shown this message:

Nothing Here

The file you are looking for has been deleted or moved.



Tom

 

[probuddha]

Hi Tom

Sorry it took some time for me to figure out that I have to enable the public folder first

Hope this one works - https://dl.dropbox.com/u/158559175/CBSreg.zip


Thanks

 

[tom982]

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.

You replaced the wrong files What you replaced:

package_for_kb2685811_rtm~31bf3856ad364e35~amd64~~6.1.1.11.cat
package_for_kb2685811_rtm~31bf3856ad364e35~amd64~~6.1.1.11.mum

What needed replacing:

Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat
Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum

Although these files need replacing, I'm not convinced this will fix the problem

probuddha, can you do this please:

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Please download the attached file, Packs.zip and save this to your Desktop.
2. Right-click on the file and select Extract All...
3. Tick the box labelled Show extracted files when complete then click Extract
4. A window will open showing two folders, Manifests and Packages
5. Open the Manifests folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Winsxs\Manifests
   
   
6. Open the Packages folder and copy the files into the following folder (if there are any files)
   
   C:\Windows\Temp\CheckSur\Servicing\Packages
   
   
7. Run the System Update Readiness Tool (SURT) again
8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:
   
   C:\Windows\Logs\CBS\CheckSUR.persist.log

Tom

 

[probuddha]

sure ...on it now. Will get back to you with the logs as soon as it's done

Many thanks

 

[probuddha]

Tom - the Manifests folder is empty

Also do I delete these existing files within the C:\Windows\Temp\CheckSur\Servicing\Packages folder

package_for_kb2685811_rtm~31bf3856ad364e35~amd64~~6.1.1.11
package_for_kb2685811_rtm~31bf3856ad364e35~amd64~~6.1.1.11

Kindly let me know

Thanks

 

[tom982]

Tom - the Manifests folder is empty

It's meant to be, sorry for the confusion

Also do I delete these existing files within the C:\Windows\Temp\CheckSur\Servicing\Packages folder

package_for_kb2685811_rtm~31bf3856ad364e35~amd64~~6.1.1.11
package_for_kb2685811_rtm~31bf3856ad364e35~amd64~~6.1.1.11

Kindly let me know

Thanks

Nope, just leave them be please.

 

[probuddha]

Here you go Tom:-

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-03-31 02:02

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)	CBS MUM Corrupt	0x00000000	servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum		Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~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: 568
 Found 1 errors
  CBS MUM Corrupt Total count: 1

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



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-04-01 02:55

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)	CBS MUM Corrupt	0x00000000	servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum		Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~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: 732
 Found 1 errors
  CBS MUM Corrupt Total count: 1

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



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-04-01 14:43

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)	CBS MUM Corrupt	0x00000000	servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum		Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~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: 625
 Found 1 errors
  CBS MUM Corrupt Total count: 1

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



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-04-02 23:17

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)	CBS MUM Corrupt	0x00000000	servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum		Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~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: 788
 Found 1 errors
  CBS MUM Corrupt Total count: 1

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



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-04-04 20:06

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)	CBS MUM Corrupt	0x00000000	servicing\Packages\Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum		Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name
(fix)	CBS MUM Corrupt	CBS File Replaced	Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.
(fix)	CBS Paired File	CBS File also Replaced	Package_for_KB2685811_SP1~31bf3856ad364e35~amd64~~6.1.1.11.cat from Cabinet: C:\Windows\CheckSur\v1.0\windows6.1-7601-x64-clientcab4.cab.

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 754
 Found 1 errors
 Fixed 1 errors
  CBS MUM Corrupt Total count: 1
  Fixed: CBS MUM Corrupt.  Total count: 1
  Fixed: CBS Paired File.  Total count: 1

 

[NoelDP]

Duh - sorry about that, folks
I think it was one of those days - I've had a few lately - where I have problems reading the screen

 

[tom982]

Great! The SURT log is clear now. Try to update please and if it fails, upload your CBS log:

C:\Windows\Logs\CBS\CheckSUR.persist.log

Duh - sorry about that, folks
I think it was one of those days - I've had a few lately - where I have problems reading the screen

You're not alone When we have to sift through this amount of information it's so easy to make a mistake - something I've done quite a lot too! At least this mistake is a harmless one, my last one made 39 updates fail!

 

[probuddha]

Hi Tom

The SP 1 installation seemed to proceed this time. I am running the pack that I downloaded from Microsoft instead of going through automatic updates.

However it's been close to 2 hrs now and it is still installing and seems to have a lot to cover still. Also I see that the resulotion of the screen has dropped. Is this normal to take so long? Should I cancel it now and run it through automatic updates?

Please advise

Thanks

 

[tom982]

Hi probuddha,

That's great news! I would leave it for quite a while, say 12 hours, before cancelling it. Service Pack installations usually take a long time but 2 hours is starting to push it a bit. I only want to cancel it if we're sure it's hanging.

Tom

 

[probuddha]

Okay so this is what happened in the last couple of hours or so.

I finally had to stop the installation of the SP1 since it seemed to be stuck and it had already been 2 hrs since I initiated the installation. So after I pressed cancel, the SP1 installation window wouldn't close, so I just killed the process through the task manager and went to reboot my PC. It wouldn't even shut down and was stuck at a black screen for several mins after which I reluctantly pressed the reset button on my PC and it rebooted.

It went through the "Configuring Service Pack" phase about 3-4 times and rebooted several times. Later after configuring SP for about an hour or so, I finally got to the desktop and ran the SURT again to help you see if there were any errors.

Attached is the SURT log - please check

Also when I go to the properties of Computer, I don't see Service Pack 1 mentioned under Windows Edition, so I guess it was not installed (even though it went through the Configuring Service Pack phase several times), also I couldn't see it listed under installed programs in Control Panel

Now, my question is, do I do a system restore (before SP1 started installing) and install it through Windows Update?

Also, do I keep the following files in the C:\Windows\Temp\CheckSur\Servicing\Packages folder or remove it?

package_for_kb2685811_rtm~31bf3856ad364e35~amd64~~6.1.1.11
package_for_kb2685811_rtm~31bf3856ad364e35~amd64~~6.1.1.11

Sorry if I am asking too many questions here or just being paranoid. I just want to make sure that my Windows is running error free

Kindly advise

Many thanks once again

Probuddha

 

[tom982]

Hi probuddha,

Yeah, that's made a right mess! Do a system restore to before SP1 then post your CBS log please, before trying to update to SP1. Don't install SP1 until either Noel or myself gives you the go ahead

Tom

 

[probuddha]

Absolutely - on it now

Thanks

 

[tom982]

Absolutely - on it now

Thanks

Great! Good luck

I've got an early start tomorrow so I'm off to bed now but I'll check back in the morning before work.

Tom

 

[probuddha]

Sure - no problem.

Thank you so much Tom

Good Night!