Tags Tags

Windows Update KB951847 error codes 0x8070663, 0x663

January 08th, 2012 - 05:26 am ET by Greegor | Report spam
Help Create a new topic
In January of 2012 I did a reinstall of WinXP Pro SP2
from CD and updated to SP3, IE8 and all of the security
updates suggested by the Windows UPDATE site.
It's very laborious rebooting over and over as
directed but everything worked just fine until I got to
KB951847 .NET 3.5 SP1 and .NET Framework 3.5
Family Update for .NET v 2.0 through 3.5 and a
raft of other Framework UPDATES pushed after
that were failing.

They would download without any bad sectors yet
would FAIL to install, reported by an X on a red circle.
Retries and clicking on the warning x's to get the error codes
gave me errors 0x80070663, 0x663 and 0x8007064c.
I studied various cures described online including both
small MS Fixit and larger MS Fixit program that installs.
The larger one had whole major sections which would
not even run and could NOT report that failure to MS.
I noticed that various people had reported similar
Framework update failures even going back several
years and in many cases there was no report back
about what actually resolved them.

The cure that finally worked for me was described here:
http://answers.microsoft.com/en-us/...2642579e69

Get a redistributable update to Microsoft Installer 4.5!

Checking the version of windows installer

http://msmvps.com/blogs/athif/archi...99125.aspx

<html>
<head>
<script language="vbscript">
sub document_onclick()
set installer = createobject("windowsinstaller.installer")
msgbox installer.version
end sub
</script>
</head>
<body>
Click me for Windows Installer version...
</body>
</html>

Cut and paste that text into notepad, save it as a text file,
rename .txt to .html and double click to run it.
When you run it approve activex access and click the text.
The version of installer (internal code) will be revealed.
Some other methods to investigate what VERSION
you have actually report the number of a
related module but not the Windows Installer itself.
(formerly MSI, formerly MSinstall)
This short html (with approvals from operator)
apparently give a more accurate answer as to
the version of Windows Installer as it is called now.

I found that despite SP3 and ALL of the updates
the update site had pushed out to me that it had
never pushed Windows Installer 4.5 out to me.

I had 3.1.4001.5512 before the KB942288-V3-x86
redistributable installed 4.5.6001.22159 on my machine.
That's a huge jump in software revisions!

Yes, Microsoft's update site had pushed out updates
that required a newer version of INSTALLER before
pushing out the newer INSTALLER to do the job!

Note to Windows UPDATE site managers!

After I installed Windows Installer 4.5 KB942288
in the right flavor for my machine I was right
back to getting updates pushed out by the
Windows UPDATE site and rebooting and
going back to the site as directed and without
0x633, 0x80070663 or 0x8007064c error codes.

Windows Installer 4.5 had solved the update failure problem.

Installer (MSI) 4.5 for various systems

http://support.microsoft.com/kb/942288

http://www.microsoft.com/download/e...ls.aspx?id„83

http://go.microsoft.com/fwlink/?LinkId0486

Thank you to Gokul T at Microsoft!
Your 2009 pointer solved my problem in 2012.
Thanks!
Greg S. Hanson
Cedar Rapids, Iowa
email Follow the discussionReplies 14 repliesReplies Make a reply

Replies

#1 Mayayana
January 08th, 2012 - 09:48 am ET | Report spam
You realize that you probably didn't need all of that
in the first place? The .Net Framework is only needed
if you have .Net software. The 3+ versions are about
1/2 GB total size! It's basically a gigantic, bloated
Microsoft Java.

Even most people who need .Net don't need greater
than v. 2. When Microsoft came out with v. 3 it was a
problem for .Net programmers: Most people didn't have
the v. 3 runtime and dependencies half the size of the
operating system are tricky to sneak by end users who
thought they were just installing a 2 MB trinket program.
So MS designed later versions of Visual Studio (the
programming tool for .Net software) so that software
could be written in .Net v. 2 or later. Only people who
needed functionality in .Net 3+ would need to program
in .Net 3+.

The whole .Net mess was originally designed to compete
with Java in writing quickie applets on corporate intranet
servers. Microsoft pretends it's also the tool of choice for
writing Windows software because they want to get away
from allowing 3rd-party programmers free rein on Windows.
.Net, like Java, is designed for sandboxed, "safe" software.
The .Net runtime is one gigantic wrapper running on top of
the operating system.

One can see Microsoft's general
direction in their plans for Metro software on Win8. Metro
software will be controlled. It will have to go through the MS
store. (And MS gets a cut of sales.) And from reports it sounds
like it will be little more than glorified webpages - written in
.Net or javascript! Windows software will still be possible
Windows, and Metro software cannot be written as compiled
Windows software.

If you need .Net and don't mind the bloat then there's
no problem installing it, but it is *not* a part of Windows.
(I have XP SP3 and have no .Net files at all. As with Java,
if I come across software that needs .Net I find different
software to serve my needs.)

"Greegor" wrote in message
news:
| In January of 2012 I did a reinstall of WinXP Pro SP2
| from CD and updated to SP3, IE8 and all of the security
| updates suggested by the Windows UPDATE site.
| It's very laborious rebooting over and over as
| directed but everything worked just fine until I got to
| KB951847 .NET 3.5 SP1 and .NET Framework 3.5
| Family Update for .NET v 2.0 through 3.5 and a
| raft of other Framework UPDATES pushed after
| that were failing.
|
| They would download without any bad sectors yet
| would FAIL to install, reported by an X on a red circle.
| Retries and clicking on the warning x's to get the error codes
| gave me errors 0x80070663, 0x663 and 0x8007064c.
| I studied various cures described online including both
| small MS Fixit and larger MS Fixit program that installs.
| The larger one had whole major sections which would
| not even run and could NOT report that failure to MS.
| I noticed that various people had reported similar
| Framework update failures even going back several
| years and in many cases there was no report back
| about what actually resolved them.
|
| The cure that finally worked for me was described here:
|
http://answers.microsoft.com/en-us/...2642579e69
|
| Get a redistributable update to Microsoft Installer 4.5!
|
| Checking the version of windows installer
|
| http://msmvps.com/blogs/athif/archi...99125.aspx
|
| <html>
| <head>
| <script language="vbscript">
| sub document_onclick()
| set installer = createobject("windowsinstaller.installer")
| msgbox installer.version
| end sub
| </script>
| </head>
| <body>
| Click me for Windows Installer version...
| </body>
| </html>
|
| Cut and paste that text into notepad, save it as a text file,
| rename .txt to .html and double click to run it.
| When you run it approve activex access and click the text.
| The version of installer (internal code) will be revealed.
| Some other methods to investigate what VERSION
| you have actually report the number of a
| related module but not the Windows Installer itself.
| (formerly MSI, formerly MSinstall)
| This short html (with approvals from operator)
| apparently give a more accurate answer as to
| the version of Windows Installer as it is called now.
|
| I found that despite SP3 and ALL of the updates
| the update site had pushed out to me that it had
| never pushed Windows Installer 4.5 out to me.
|
| I had 3.1.4001.5512 before the KB942288-V3-x86
| redistributable installed 4.5.6001.22159 on my machine.
| That's a huge jump in software revisions!
|
| Yes, Microsoft's update site had pushed out updates
| that required a newer version of INSTALLER before
| pushing out the newer INSTALLER to do the job!
|
| Note to Windows UPDATE site managers!
|
| After I installed Windows Installer 4.5 KB942288
| in the right flavor for my machine I was right
| back to getting updates pushed out by the
| Windows UPDATE site and rebooting and
| going back to the site as directed and without
| 0x633, 0x80070663 or 0x8007064c error codes.
|
| Windows Installer 4.5 had solved the update failure problem.
|
| Installer (MSI) 4.5 for various systems
|
| http://support.microsoft.com/kb/942288
|
| http://www.microsoft.com/download/e...ls.aspx?id„83
|
| http://go.microsoft.com/fwlink/?LinkId0486
|
| Thank you to Gokul T at Microsoft!
| Your 2009 pointer solved my problem in 2012.
| Thanks!
| Greg S. Hanson
| Cedar Rapids, Iowa

Similar topics

Make your own search :