Update KB951847 won't install after download

Hello, I am have trouble installing the update KB951847 Net framework 3.5
service pack 1 after it downloads fine.

Any suggestions?

Smile, it's contagious!!!

"TBigRagu" <> schreef in bericht
news:9879311E-D609-4CAF-918A-...
> Hello, I am have trouble installing the update KB951847 Net framework 3.5
> service pack 1 after it downloads fine.
>
> Any suggestions?
>
> Smile, it's contagious!!!

Be patient ! Here it took on 2 pc's about half an hour to actually start the
install bar and an hour to finish.
Good luck

I am also having the same probleam it's not that it's taking to long it i am
getting a installation failure error code 0x80070643 how do I get it to work?

"gigobert" wrote:

>
> "TBigRagu" <> schreef in bericht
> news:9879311E-D609-4CAF-918A-...
> > Hello, I am have trouble installing the update KB951847 Net framework 3.5
> > service pack 1 after it downloads fine.
> >
> > Any suggestions?
> >
> > Smile, it's contagious!!!
>
> Be patient ! Here it took on 2 pc's about half an hour to actually start the
> install bar and an hour to finish.
> Good luck
>
>
>

See the following and ignore the title and use method 1 and then use method 2 if
needed. Always reboot after implementing the fix

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

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"TBigRagu" <> wrote in message
news:9879311E-D609-4CAF-918A-...
> Hello, I am have trouble installing the update KB951847 Net framework 3.5
> service pack 1 after it downloads fine.
>
> Any suggestions?
>
> Smile, it's contagious!!!

Lest any have hope that this is a simple resolution, "Method 1" is to
uninstall ALL previous versions and service packs of .NET Framework, from
1.0 to 3.x, and then reinstall ALL of the previous versions, with a
"clean-up" tool thrown in for good measure, before retrying the KB951847
update. Is anybody's confidence high that this will work? Willing to take a
chance on what promises to be a time-consuming and error-prone procedure with
no guarantee that it will work? This is a typical tech support
uninstall/reinstall recommendation with the implied cross-your-fingers hope
that it will solve the problem. No, thanks.

"Peter Foldes" wrote:

> See the following and ignore the title and use method 1 and then use method 2 if
> needed. Always reboot after implementing the fix
>
> http://support.microsoft.com/kb/923100
>
> --
> Peter

TBigRagu wrote:
> I am have trouble installing the update KB951847 Net
> framework 3.5 service pack 1 after it downloads fine.
>
> Any suggestions?

Peter Foldes wrote:
> See the following and ignore the title and use method 1 and then
> use method 2 if needed. Always reboot after implementing the fix
>
> http://support.microsoft.com/kb/923100

ElderEagle wrote:
> Lest any have hope that this is a simple resolution, "Method 1" is
> to uninstall ALL previous versions and service packs of .NET
> Framework, from
> 1.0 to 3.x, and then reinstall ALL of the previous versions, with a
> "clean-up" tool thrown in for good measure, before retrying the
> KB951847 update. Is anybody's confidence high that this will work?
> Willing to take a chance on what promises to be a time-consuming
> and error-prone procedure with no guarantee that it will work?
> This is a typical tech support uninstall/reinstall recommendation
> with the implied cross-your-fingers hope that it will solve the
> problem. No, thanks.

It worked on the two cases I have had to suggest it on.

It's actually very similar to something that had to be done long ago with
another .NET Framework patch that seemed to have similar issues (when the
problems arose - although truthfully - that was few and far between - just
like this time.)

Not everything has a simple solution - and sometimes it is the individual
human factor that complicates things the most.

I definitely would not call this typical - as in most cases - the end-user
probably didn't even know they had .NET Framework (unless they had an issue
with it before) of any version as it was likely installed by some third
party utility/tool/application that required it.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

> ElderEagle wrote:
> > Lest any have hope that this is a simple resolution, "Method 1" is
> > to uninstall ALL previous versions and service packs of .NET
> > Framework, from
> > 1.0 to 3.x, and then reinstall ALL of the previous versions, with a
> > "clean-up" tool thrown in for good measure, before retrying the
> > KB951847 update. Is anybody's confidence high that this will work?
> > Willing to take a chance on what promises to be a time-consuming
> > and error-prone procedure with no guarantee that it will work?
> > This is a typical tech support uninstall/reinstall recommendation
> > with the implied cross-your-fingers hope that it will solve the
> > problem. No, thanks.
>
> It worked on the two cases I have had to suggest it on.
>
> It's actually very similar to something that had to be done long ago with
> another .NET Framework patch that seemed to have similar issues (when the
> problems arose - although truthfully - that was few and far between - just
> like this time.)
>
> Not everything has a simple solution - and sometimes it is the individual
> human factor that complicates things the most.
>
> I definitely would not call this typical - as in most cases - the end-user
> probably didn't even know they had .NET Framework (unless they had an issue
> with it before) of any version as it was likely installed by some third
> party utility/tool/application that required it.
>
> --
> Shenan Stanley
> MS-MVP

OK. I'll consider it. "Method 1" lists, if I remember correctly, seven
downloads and installs to get up to .NET Framework 3.5. This had better
work. I have 44 years of IT experience and I'm not really looking forward to
this. I can't imagine what typical end-users will do.

Based on the volume of "please help me" posts about KB951847, I don't think
this is "few and far between". Usually, those who post are the tip of the
proverbial iceberg of those experiencing problems.

ElderEagle wrote:

> OK. I'll consider it. "Method 1" lists, if I remember correctly, seven
> downloads and installs to get up to .NET Framework 3.5.

It shouldn't be necessary to install .NET 2.0 or 3.0 before 3.5. At least, I'd
try jumping straight to KB951847 and see what happens before taking the long route.

Harry.

I'd skip to Method 2 myself. Yes, it works.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

ElderEagle wrote:
> Lest any have hope that this is a simple resolution, "Method 1" is to
> uninstall ALL previous versions and service packs of .NET Framework, from
> 1.0 to 3.x, and then reinstall ALL of the previous versions, with a
> "clean-up" tool thrown in for good measure, before retrying the KB951847
> update. Is anybody's confidence high that this will work? Willing to
> take
> a chance on what promises to be a time-consuming and error-prone procedure
> with no guarantee that it will work? This is a typical tech support
> uninstall/reinstall recommendation with the implied cross-your-fingers
> hope
> that it will solve the problem. No, thanks.
>
> "Peter Foldes" wrote:
>
>> See the following and ignore the title and use method 1 and then use
>> method 2 if needed. Always reboot after implementing the fix
>>
>> http://support.microsoft.com/kb/923100
>>
>> --
>> Peter

These two tools are a *primary* cause of installation failures for .NET
Frameworks, updates, and ServicePacks.

> 3. I then ran 2 different registry cleaners: Tony Arts Easy Cleaner
> and Regclean and restarted the system.

Now, I'm not saying that *you* ran them *prior* to the installation of
any of the above, what I am saying is that running *ANY* registry or
disk cleanup tool *AFTER* the installation of a .NET Framework will
*definitely* cause installation issues with updates or Service Packs
intended for those runtimes in the future.
Installation source cache databases and registry settings *will* be
affected by running those tools.

I've seen this issue on *so many client systems* now that I wish I had
just one measly buck for everytime I did.
The .NET installation sources are, to put it politely, fragile.
Supposedly, with this massive, complex KB951847, those installation
source issues will no longer be as painful as they are currently.

I'm not holding my breath, though. <w> Time will tell.


MowGreen [MVP 2003-2009]
===============
*-343-* FDNY
Never Forgotten
===============






lhgordon wrote:

> Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5
> Family Update (KB951847) x86 has been difficult to install properly. My
> solution worked the first time after several mistries.
> 1. Since I no longer trust Microsoft, before installing a patch or
> update, I always make a complete system backup to DVD using a bootable
> CD with Acronis on it.
> 2. I Downloaded and used the program dotnetfx_cleanup_tool.zip from
> http://astebner.sts.winisp.net/Tools...rm.aspx?ID=111 to
> remove all previous installed versions of dot net framework. Note I used
> the zip version because it passes my browser security settings. The zip
> file contains the cleanup tool, and 2 text files. After running the
> cleanup tool I restarted my system.
> 3. I then ran 2 different registry cleaners: Tony Arts Easy Cleaner
> and Regclean and restarted the system.
> 4. I disabled my software firewall and virus scanner, clicked on
> Start and Microsoft Update, selected Custom Install and installed Update
> (KB951847) x86, restarted the system to reactivate the firewall and
> antivirus program. I verified that everything was installed correctly
> by going to Control Panel, Add or Remove Programs to verify all versions
> of dot net were there.
> 5. I then defragmented my hard drives to keep everything compact.
>
> The only thing I do not know is what programs even use this feature. I
> wish someone would create a data base of programs that use dot net.
>
>