Solved KB2813430, KB2862966 and KB2808679 update failed.

[Warkris]

View attachment 284956

 

[NoelDP]

Great - just the one error left now.
Unfortunately, I'm having problems with that one, as it's corrupted outside my experience.
I've called for reinforcements, so hopefully rescue will be at hand

 

[Warkris]

Woohoo! Well thanks for your help. I was looking at my old Checksur logs and I didn't realise how many errors I had at the start! So you think it was that bad Ram that caused this?

 

[tom982]

Hi Warkris,

I have repaired the error listed in your CheckSUR log, as well as over 100 more that weren't logged by any of the tools It's quite interesting actually, if you look at the screenshot of my fix:

The red characters are my repairs (there are many, many pages of these!), but look at the pattern of the corrupt characters and you'll see it's the same bytes each time.

Here is the repaired components hive, replace your one with this in the same fashion as last time please, then run the System Update Readiness Tool and post the CheckSUR log again.

https://dl.dropboxusercontent.com/u/16537616/Fixes/COMPONENTS/Warkris/COMPONENTS.zip

This is definitely a hardware fault as nothing else could cause this scale of damage. Let's see what Memtest thinks of your RAM:

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Tom

 

[Warkris]

Ok i'll start doing that now. I was getting BSoD's on the 11 June this year and I ran some mem checks and it was the Ram so I replaced it. I will do the Mem test if you think it'll help though

 

[Warkris]

View attachment 284973

 

[tom982]

Hi Warkris,

Looks like I missed two. Try this one: https://dl.dropboxusercontent.com/u/16537616/Fixes/COMPONENTS/Warkris/COMPONENTS.zip

Yeah, scanning with Memtest would be a good idea - it won't fix anything, but it will let us know if the RAM is bad.

Tom

 

[Warkris]

View attachment 284980

 

[tom982]

Hi Warkris,

The remaining errors in your CheckSUR log are nothing to worry about

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 20.0
2013-09-07 16:50

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f)	CBS MUM Corrupt	0x00000000	servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum		Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f)	CBS MUM Corrupt	0x00000000	servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum		Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 879
 Found 2 errors
  CBS MUM Corrupt Total count: 2

Unavailable repair files:
	servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
	servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
	servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
	servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat

Is Windows Update working now?

Tom

 

[NoelDP]

Thanks for coning to the rescue, Tom!

 

[Warkris]

So I went to check for new updates so I could test to see if it was working now and this happened when searching.
View attachment 285100

So I was like hmm, I'll check my installed updates to see if any have been installed recently and I saw this.
View attachment 285101

So to answer your question no I can't update windows now because it won't search and all my updates aren't appearing in the list haha

 

[Warkris]

Also this update is keep repeating it's update

View attachment 285102

 

[tom982]

Can you zip up and attach your CBS folder please?

Tom

 

[Warkris]

https://skydrive.live.com/redir?resid=67E890C7F7EDBFED!377&authkey=!AM8Rv2zcTw5ZUKg

 

[tom982]

Hi Warkris,

Your CBS log is full of this error, repeated over and over again:

2013-09-08 12:36:13, Error                 CSI    000005d9 (F) STATUS_OBJECT_NAME_NOT_FOUND #424561792# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xe3d040->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[136]"\Registry\Machine\COMPONENTS\DerivedData\Components\x86_microsoft-windows-getuname_31bf3856\u00dcd364e35\u00d76.1.760\u00ae.16385_pone_2d37ee8fae\ead3"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14930952 (0x00e3d408))[gle=0xd0000034]
2013-09-08 12:36:13, Error                 CSI    000005da@2013/9/8:11:36:13.983 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2013-09-08 12:36:14, Error                 CSI    000005db (F) STATUS_OBJECT_NAME_NOT_FOUND #424561791# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 0, da = (KEY_READ), oa = @0xe3d770, key = NULL, disp = (null))[gle=0xd0000034]
2013-09-08 12:36:14, Info                  CBS    Failed to get CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2013-09-08 12:36:14, Error                 CBS    Failed to initialize store parameters with boot drive:  and windows directory:  [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2013-09-08 12:36:14, Info                  CSI    000005dc@2013/9/8:11:36:14.931 PopulateComponentFamiliesKey - Begin

Looking at the registry path, we can see how screwed your components hive is:

x86_microsoft-windows-getuname_31bf3856\u00dcd364e35\u00d76.1.760\u00ae.16385_pone_2d37ee8fae\ead3

That should be:

x86_microsoft-windows-getuname_31bf3856ad364e35_6.1.7600.16385_none_2d337ee8fae2ead3

We could fix this, but I fear we'll just run into another error, and so on. A repair install would be sensible at this point:

http://www.sevenforums.com/tutorials/3413-repair-install.html

It may well fail though, in which case you'd have to do a clean install:

http://www.sevenforums.com/tutorials/1649-clean-install-windows-7-a.html

Tom

 

[Warkris]

Guess i'll have to do a clean install then which is what I really didn't want to do

Well guess this is the end of my help from you guys. Thanks for all the help and time you both have put in

 

[tom982]

It's worth giving a repair install a go, that way there's a chance you won't have to reinstall all of your programs and drivers as well

You're most welcome, give us a shout if you have any problems with the reinstallation.

Tom

 

[NoelDP]

Good luck, whichever way to end up going!

Sorry we couldn't get it fixed the other way

 

[Warkris]

I'm just going to wipe it. It started off just an update problem and now it's loads! I don't want to find more errors down the line with something else so it's probably for the best.

Don't be sorry you didn't fix it, you did an amazing job Anyway's shall I mark this a solved or not?

 

[tom982]

I'm just going to wipe it. It started off just an update problem and now it's loads! I don't want to find more errors down the line with something else so it's probably for the best.

Don't be sorry you didn't fix it, you did an amazing job Anyway's shall I mark this a solved or not?

Oh, all of this corruption is related to Windows Update, but it will cause all sorts of other problems like not being able to run SFC, so a clean install is probably sensible.

I'd wait until you've reinstalled Windows before you mark it as solved

Tom