[SOLVED] Another IE 10 update failure

S

Sharktank

Member
Joined
Aug 31, 2013
Posts
5
Hi guys. Have this up on the Windows Seven forum as well, but thought I would give it a shot over here.

Ran SURT

SFC scan (Will not complete, stops @ 19%)

Error
code 9C59 when attempting to update to IE 10 ( error 0x80070643: Internet
Explorer 10 for Windows 7 for x64-based Systems.)

In addition, I have ran
chkdsk (no issues)

View attachment 5131
 
Hello Sharktank, welcome to Sysnative!

Your CheckSUR log indicates you have severe problems on your computer:

Code: 
Summary:
Seconds executed: 14968
 Found 1665 errors
 Fixed 1 errors
  CBS MUM Corrupt Total count: 1664
  CBS Catalog Missing Total count: 1
  Fixed: CBS Catalog Missing.  Total count: 1
  Fixed: CBS Paired File.  Total count: 1

All of the errors take this form:

Code: 
(f)	CBS MUM Corrupt	0x8007047F	servicing\Packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.2.6001.788.mum	servicing\Packages\WUClient-SelfUpdate-Core~31bf3856ad364e35~x86~~7.2.6001.788.cat	Package manifest cannot be validated by the corresponding catalog

A corrupt .mum file with 0x8007047F isn't something I've seen before, and as there are upwards on 1,000 files with problems, I don't think the files themselves are the problems here.

0x8007047f translates to ERROR_APP_WRONG_OS:

Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\System32>err 47f
# for hex 0x47f / decimal 1151 :
  RES_NETNAME_DNS_A_RECORD_DELETE_FAILED                        clusvmsg.h
  ecServerPaused                                                ec.h
[B]  ERROR_APP_WRONG_OS                                            winerror.h[/B]
# The specified program is not a Windows or MS-DOS program.
# 3 matches found for "47f"

C:\Windows\System32>

Did you upgrade this computer from Vista? If not, where did you get your copy of Windows from?

MGADiag

  1. Download MGADiag (by Microsoft) from the link below:

    http://go.microsoft.com/fwlink/?linkid=52012

  2. Run the tool by double clicking on the file. Press Continue when prompted
  3. When it has finished, press Copy then Paste (Ctrl+V) this into your next post

Tom
 
Last edited:
Thanks Tom,

Did you upgrade this computer from Vista? If not, where did you get your copy of Windows from?
Click to expand...

No. It's an OEM on a Gateway puter. Didn't intened to convolute matters here, but the guys on the Seven forum are recomending a repair install at this point.

A couple of things probably contributed to this: One, I have been using IObit's Advanced System Cleaner (paid for) which I'm being told is dangerous (had no clue). Secondly, Malwarebytes had a bad update several months back that I got caught in. It actually erased any number of system files ... Long story short, I was getting conflicting fixes from their tech guys at the time and I don't think it was ever repaired correctly.

So at this point I'm probably best served doing the repair\install
 
Hi Sharktank,

That's very odd indeed! The reason I asked is because if we look at your CheckSUR log, you will the KB article number in the package name which indicates what update it came from. Taking a few of these as an example to look up their web page:

KB936330 -> Learn how to install Windows Vista Service Pack 1 (SP1)
KB937286 -> Windows Vista service pack stand-alone packages do not contain the updated Windows Vista Help files
KB970430 -> Description of the update that implements Extended Protection for Authentication in the HTTP Protocol Stack (http.sys)
KB938371 -> A software update is available for the Windows Vista installation components
KB948465 -> Information about Service Pack 2 for Windows Vista and for Windows Server 2008
KB961371 -> MS09-029: Vulnerabilities in the Embedded OpenType Font Engine could allow remote code execution
KB968816 -> MS09-047: Description of the security update for Windows Media Format Runtime, Windows Media Services, and Media Foundation: September 8, 2009
KB970710 -> MS09-049: Vulnerability in Wireless LAN AutoConfig Service could allow remote code execution

And let's take some of the packages without a KB number:

Code: 
6.0.6000.16386 -> Microsoft-Windows-Anytime-Upgrade-HomePremium-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Anytime-Upgrade-HomePremium-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Backup-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Backup-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Branding-HomePremium-Client-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Branding-HomePremium-Client-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-BRCpl-Premium-LanguagePack-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-BRCpl-Premium-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-CaptureWizard-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-CaptureWizard-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-ClipsInTheLibrary-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-ClipsInTheLibrary-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-CodecPack-Basic-Encoder-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-CodecPack-Basic-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-DesktopWindowManager-uDWM-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-DFSR-ClientEdition-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-DFSR-ClientEdition-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Disk-Diagnosis-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Disk-Diagnosis-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-GPUPipeline-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-GPUPipeline-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Help-CoreClientUAHP-Package~31bf3856ad364e35~x86~en-US~6.0.6000.16386.mum
6.0.6000.16386 -> Microsoft-Windows-Help-CoreClientUAHP-Package~31bf3856ad364e35~x86~~6.0.6000.16386.mum

In case you don't already know, 6.0.6000.16386 is the version number of Vista RTM. I know I've only taken a few lines as an example, but they are all Vista files.

There's a bit of a recurring theme here! Somehow you've ended up with over a thousand Windows packages on your Windows 7 computer which is something I've never seen before. This shouldn't ever have happened as Microsoft has safeguards in place to prevent users from installing incompatible updates on their computer. I had originally suspected that you had downloaded an ISO slipstreamed with the latest updates, but a few Vista ones found their way in, and had used that to install Windows, which is why I questioned your installation, but if yours is OEM then that won't be the case. So, the only other possibility as I see it (short of you modifying the updates manually!) is that a third party program installed them somehow. I've never used ASC before and am not familiar with the tools included, is there something to do with keeping Windows patched or up to date?

Now, about ASC, I have to agree with what you've already been told. Firstly, I have no respect for IObit whatsoever and could never trust their developers after what they did to Malwarebytes a few years ago:

IOBit Steals Malwarebytes' Intellectual Property - Malwarebytes News - Malwarebytes Forum

Secondly, I strongly advise you avoid all forms of system/registry optimisers/cleaners as they usually do more harm than good. They all promise such big improvements but none of them deliver, plus the registry optimisers/cleaners are usually a little over-zealous when removing the keys and a lot of legitimate keys and values are removed in the process. I personally dealt with a thread a few months ago where PC Cleaner Pro deleted ~2,000 system registry keys and completely killed Windows Update. For removing temp files, I use CCleaner:

CCleaner - PC Optimization and Cleaning - Free Download

Just stick away from the registry cleaner section - although it is considered relatively safe, it's an unnecessary risk as you won't see any improvements from using it.

Due to the scale of the problem here, and the fact that we have no idea what else ASC has messed up, I agree with the SF members that you should go ahead with the repair install:

https://www.sysnative.com/forums/wi...-install-windows-windows-7-windows-vista.html

Tom
 
Hi Tom,

It occured to me that I had done an Easy Transfer from my prior computer\hard drive that was running Vista, could that be where these were picked up from?
I'm not familar with reading these logs so I'm curious if that is the case or that the updates have somehow merged together.
In addition, I am also wondering if I need to remove anything that was brought over from that transfer before I go ahead and do a repair\install?
 
Hi Sharktank,

It should never have brought those along, but that does sound like the most feasible option at the moment.

You don't need to do anything before performing the repair install :)

Tom
 
Good to know :) It's been a looong time since I have delved into alot of this stuff so I'm feeling like a noob all over again.
Stupid question time ... My HDD is all one partition (Other than a Recovery Partition of 16GB and the SYSTEM RESERVED 100mb)

How do I create a new partition to extract the ISO download to? I'm currently looking at several different ways of going about this and I don't want to jack it up.
 
Hmm, that's far from a stupid question! :p I have no experience with that whatsoever I'm afraid. Can you not burn the ISO to a DVD or make a bootable USB? If you're limited to doing it this way then I'll find someone to help :)

Tom
 
Sharktank said:
Good to know :) It's been a looong time since I have delved into alot of this stuff so I'm feeling like a noob all over again.
Stupid question time ... My HDD is all one partition (Other than a Recovery Partition of 16GB and the SYSTEM RESERVED 100mb)

How do I create a new partition to extract the ISO download to? I'm currently looking at several different ways of going about this and I don't want to jack it up.
Click to expand...
Hi,

There is no need to create a new partition here :-) You need to burn the ISO file to a DVD, a tutorial can be found here: https://www.sysnative.com/forums/hardware-tutorials/5164-how-burn-iso-imgburn.html

You can then use this DVD to perform the repair install from.

Stephen
 
Thanks Tekno,

It took me awhile to figure that out ... I got all caught up in thinking it had to be extracted first but that was only if you were to run it within in your system.
Nevertheless, thanks to Tom and everyone else here for the help. Got through the repair install yesterday and was finally able to upgrade to IE10.

That really wasn't all that big of a deal originally, it was really more of a concern that my system had become so corrupted - It (IE10) does seem to be a lot more snappier though.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top