update fails

[shakey]

Every time I try to install KB979906 a MS update for net framework 1.1 sp1
it gets half installed then I hear the HD growl and it fails to install.
Keeps coming back as a needed update.
Any thoughts?
SG

 

[shakey]

Should have mentioned this: running XPpro sp3 with manual update install.
This update comes back almost immediately as "updates are ready for your
computer" message.

 

[Peter Foldes]

From a post by
Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002

<snip>

See the "How to obtain help" section of
http://support.microsoft.com/kb/979906

For home users, no-charge support is available by calling 1-866-PCSAFETY
(1-866-727-2338; and/or 1-866-234-6020 and/or 1-800-936-5700) in the United
States and in Canada or by contacting your local Microsoft subsidiary.
There is no-charge for support calls that are associated with security
updates. When you call, clearly state that your problem is related to a
Security Update and cite the update's KB number (e.g., KB979906).

Or you can...

Start a free Windows Update support incident email request:
https://support.microsoft.com/oas/default.aspx?gprid=6527

Customers who experience issues installing Microsoft security updates also
can visit the following page for assistance:
https://consumersecuritysupport.microsoft.com/

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.

OPTION B:

See:

When installing updates using Windows update or Microsoft Update you may
receive Error 0x643 or 0x80070643 (23 Oct-09)
http://support.microsoft.com/kb/976982

Then proceed per the following:

=====================

Step #1 => Before doing anything else, write down what .NET Framework
versions are currently installed:

How to determine which versions of the .NET Framework are installed and
whether service packs have been applied
http://support.microsoft.com/kb/318785

[As of this post, KB318785 hasn't been revised since November 2008 so you
may not find the pertinent information in it.]

Step #2 => Now see Resolution Method 2 in this related KB article:
http://support.microsoft.com/kb/923100

After running the .NET Framework Cleanup Tool (not the Windows Installer
Cleanup utility!), reinstall all .NET Framework versions (but only the ones
you wrote down in #1 above) manually using the download links on the page
then run Windows Update manually to install security updates for same.

Download links for .NET Framework Cleanup Tool:

..
http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip

..
http://blogs.msdn.com/cfs-file.ashx...-90-44-93/dotnetfx_5F00_cleanup_5F00_tool.zip

NB: If you remove .NET Framework 3.5 (SP1) using the tool, reinstalling .NET
Framework 3.5 will also install .Net Framework 2.0 SP2 and 3.0 SP2; then
Windows Update will offer .NET Framework 3.5 SP1.

IMPORTANT! => If you remove .NET Framework 3.5 (SP1), reinstall your .NET
Framework versions in the following order:

1. .Net Framework 3.5, then...
2. .Net Framework 1.1, then...
3. .Net Framework 1.1 SP1

NB: KB923100 references this page:
http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx. Please read
ALL of it as well as the related page
http://blogs.msdn.com/astebner/pages/8904493.aspx before using the .NET
Framework Cleanup Tool.

Step #3 => Check-in at Windows Update and install any critical security
updates offered.

<end snip>

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
http://www.microsoft.com/protect

 

[shakey]

Thank you Peter - Looks like I have a good sized job to do this but I will
do so.
SG

From a post by
Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002

<snip>

See the "How to obtain help" section of
http://support.microsoft.com/kb/979906

For home users, no-charge support is available by calling 1-866-PCSAFETY
(1-866-727-2338; and/or 1-866-234-6020 and/or 1-800-936-5700) in the
United
States and in Canada or by contacting your local Microsoft subsidiary.
There is no-charge for support calls that are associated with security
updates. When you call, clearly state that your problem is related to a
Security Update and cite the update's KB number (e.g., KB979906).

Or you can...

Start a free Windows Update support incident email request:
https://support.microsoft.com/oas/default.aspx?gprid=6527

Customers who experience issues installing Microsoft security updates also
can visit the following page for assistance:
https://consumersecuritysupport.microsoft.com/

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available
through
your usual support contacts.

OPTION B:

See:

When installing updates using Windows update or Microsoft Update you may
receive Error 0x643 or 0x80070643 (23 Oct-09)
http://support.microsoft.com/kb/976982

Then proceed per the following:

=====================

Step #1 => Before doing anything else, write down what .NET Framework
versions are currently installed:

How to determine which versions of the .NET Framework are installed and
whether service packs have been applied
http://support.microsoft.com/kb/318785

[As of this post, KB318785 hasn't been revised since November 2008 so
you
may not find the pertinent information in it.]

Step #2 => Now see Resolution Method 2 in this related KB article:
http://support.microsoft.com/kb/923100

After running the .NET Framework Cleanup Tool (not the Windows Installer
Cleanup utility!), reinstall all .NET Framework versions (but only the
ones
you wrote down in #1 above) manually using the download links on the page
then run Windows Update manually to install security updates for same.

Download links for .NET Framework Cleanup Tool:

.
http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip

.
http://blogs.msdn.com/cfs-file.ashx...-90-44-93/dotnetfx_5F00_cleanup_5F00_tool.zip

NB: If you remove .NET Framework 3.5 (SP1) using the tool, reinstalling
.NET
Framework 3.5 will also install .Net Framework 2.0 SP2 and 3.0 SP2; then
Windows Update will offer .NET Framework 3.5 SP1.

IMPORTANT! => If you remove .NET Framework 3.5 (SP1), reinstall your .NET
Framework versions in the following order:

1. .Net Framework 3.5, then...
2. .Net Framework 1.1, then...
3. .Net Framework 1.1 SP1

NB: KB923100 references this page:
http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx. Please
read
ALL of it as well as the related page
http://blogs.msdn.com/astebner/pages/8904493.aspx before using the .NET
Framework Cleanup Tool.

Step #3 => Check-in at Windows Update and install any critical security
updates offered.

<end snip>

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
http://www.microsoft.com/protect

Every time I try to install KB979906 a MS update for net framework 1.1
sp1 it gets half installed then I hear the HD growl and it fails to
install. Keeps coming back as a needed update.
Any thoughts?
SG

 

[kraut]

Every time I try to install KB979906 a MS update for net framework 1.1 sp1
it gets half installed then I hear the HD growl and it fails to install.
Keeps coming back as a needed update.
Any thoughts?
SG

Retrieve some of the older headers / posts to see what has been going
on as far as these updates. You are not the only one to have problems
with them. I personally think it is an Microsoft screw-up but ----

I think after a while most of the people that had trouble have done as
I have and just ignore those problem updates. Even the so called MVPs
have kind of stopped posting their supposed solutions because from
what I read in the groups they have not helped the majority of people
including me.

 

[123Jim]

Retrieve some of the older headers / posts to see what has been going
on as far as these updates. You are not the only one to have problems
with them. I personally think it is an Microsoft screw-up but ----

I think after a while most of the people that had trouble have done as
I have and just ignore those problem updates. Even the so called MVPs
have kind of stopped posting their supposed solutions because from
what I read in the groups they have not helped the majority of people
including me.

Trouble is people don't follow instructions )) did you try removing the
..net frameworks by using the net fix utility and then re-installing them? I
didn't think so )

 

[kraut]

Trouble is people don't follow instructions )) did you try removing the
.net frameworks by using the net fix utility and then re-installing them? I
didn't think so )

Yes I did and ended up in the same place I was before.

Thanks for asking.

 

[Shenan Stanley]

<snipped>

Yes I did and ended up in the same place I was before.

Thanks for asking.

Obviously something else is wrong with your system that will be diffficult
to troubleshoot remotely and without access to the machine.

I say this because although there may be many people with the problem - in
relative terms - there are very few of the TOTAL who could have the problem
with it. I have not seen it myself - and manage several thousand machines
that could be affected by it.

If the normal means of repairing the issue do not fix it for you but has
worked for others - then the problem you have is more unique than you may
have first thought and the best solution for you may be to start over.

Clean Install Windows XP
http://michaelstevenstech.com/cleanxpinstall.html

Be sure your backups are complete before you do this. ;-)

 

[123Jim]

Yes I did and ended up in the same place I was before.

Thanks for asking.

Did the uninstall succeed? I'm baffled I must say ....
<thinks> How about some process is using the .net framework and not allowing
the update in the normal way .. (the process would then make use of .net
framework as soon as it is re-installed) .... Did you go through your
running processes and kill as many as possible before trying to update?