RE: .Net Framework 1.0 SP 3 & .Net Framework 1.1 SP1 Updates

Yes I get exactly the same problem please advise if somebody know how to
solve this issue.

Thanks, Sam

"Captain" wrote:

> I recently installed SP2 after which I was informed through the wu site to
> install these updates, but they fail to install no matter what I do. I tried
> renaming/deleting catroot 2. Is it that after microsoft introduced the new
> update site, the catroot 2 folder has also been renamed; like previously
> there was a wutemp folder but now there is none. Can someone guide me as to
> where the temp downloads now reside? The following is the message that is
> contained in the new WindowsUpdate.log (previously it was Windows Update.log)
> :-
>
> 2004-09-07 04:00:12+0500 868 3f8 WU client is installing update
> {AFCFDECF-2B9F-4881-8CFE-F56ED0DD81AF}.100
> 2004-09-07 04:00:16+0500 868 798 REPORT EVENT:
> {23A2AEB2-8E0F-4F39-9FD0-0EDDF214CBB8} 111 2004-09-07
> 04:00:11+0500 1 182 101 {EC9E6BF6-0733-4064-A23D-08E58427E553} 100 80070643 WindowsUpdate Failure Content
> Install Installation Failure: Windows failed to install the following update
> with error 0x80070643: Microsoft .NET Framework 1.0 Service Pack 3, English
> Version.
> 2004-09-07 04:00:16+0500 868 798 REPORT EVENT:
> {DF7DE8D7-1106-49C2-AF1F-EFCC459662B4} 112 2004-09-07
> 04:00:11+0500 1 182 101 {8D85DEE0-C2D2-4421-A893-8F0CCACA001C} 100 80070643 WindowsUpdate Failure Content
> Install Installation Failure: Windows failed to install the following update
> with error 0x80070643: Microsoft .NET Framework 1.0 Service Pack 3, English
> Version.
> 2004-09-07 04:00:57+0500 868 3f8 WU client finishes installing update
> {AFCFDECF-2B9F-4881-8CFE-F56ED0DD81AF}.100 with result 0x8024200b
> 2004-09-07 04:00:57+0500 868 3f8 system restore point set
> 2004-09-07 04:00:57+0500 868 3f8 Agent state changed, signalling AU to
> redetect with NO delay
> 2004-09-07 04:00:57+0500 868 3f8 WU client finished installing updates
> 2004-09-07 04:00:57+0500 868 3f8 WU client calls back to install call
> {F3D6BD8A-B0EA-405D-973E-C020103871D6} with code Call complete and error 0
> 2004-09-07 04:00:57+0500 868 3f8 WU client completed and deleted call
> {F3D6BD8A-B0EA-405D-973E-C020103871D6}
> 2004-09-07 04:00:58+0500 868 79c ISusInternal API failed
> CClientCallRecorder:isconnectCall with error 0x8024000c
> 2004-09-07 04:00:58+0500 996 aa4 ISusInternal:isconnectCall failed,
> hr=8024000C
> 2004-09-07 04:01:02+0500 868 3f8 REPORT EVENT:
> {633EAD65-1B7D-4625-90B9-78E3C3BC2C4B} 113 2004-09-07
> 04:00:57+0500 1 182 101 {6F5DC828-0F05-4577-9A8A-74AB1CBE00A9} 100 80070643 WindowsUpdate Failure Content
> Install Installation Failure: Windows failed to install the following update
> with error 0x80070643: Microsoft .NET Framework 1.1 Service Pack 1.
> 2004-09-07 04:01:02+0500 868 3f8 REPORT EVENT:
> {867B7F37-1323-41BB-BCAE-92D2AB4F779C} 114 2004-09-07
> 04:00:57+0500 1 182 101 {AFCFDECF-2B9F-4881-8CFE-F56ED0DD81AF} 100 80070643 WindowsUpdate Failure Content
> Install Installation Failure: Windows failed to install the following update
> with error 0x80070643: Microsoft .NET Framework 1.1 Service Pack 1.
>
>
> Someone please guide me..
>

Well the problem has been long resolved, I did post the solution to
different newsgroups, I had the same issue and somehow resolved it after
visiting a couple of newsgroups and through my own experiments. I am pasting
the contents of one of my posts that I posted a few days back in this
newsgroup. Regarding the update successfully installing on windows 2000; the
problem is not with the update but with sp2 which you must have installed
before trying to upgrade .net. Do ask if there's any need for further
clarification/help......Here is my post: -

After encountering an update problem relating to both versions of Microsoft
..net framework, I happened to visit windows update newsgroup and dotnet
newsgroup and found every other person was having this problem. Incidentally
this problem had happened with them after they had installed xp sp2. After a
lot of browsing on Google and Microsoft knowledge base articles, I found the
only solution to the problem was uninstalling both versions of .net and
reinstalling them again. Interestingly sp2 had done enough damage to not
allow repair of these programs. Now uninstall was another bigger problem,
but thanks to the following knowledge base articles: -

1) Microsoft Knowledge Base Article - 320112 --- For removing Microsoft
..NET Framework 1.0.3705
2) Microsoft Knowledge Base Article - 824643 --- For removing Microsoft
..NET Framework 1.1

And then I got stuck on using Msizap.exe utility, which wanted me to
download Microsoft Windows Installer Software Development Kit (SDK). I
accordingly went to the site for the download but found out that it was a
pretty big job as it included other compulsory downloads. I failed after
numerous tries to download as the site didn't allow using any download
managers and using dial-up for huge downloads is definitely a problem. And
then I searched for Msizap.exe utility on the net after I found out that sp2
supported this tool. I found it here: -

Referrer
http://www.google.com.pk/search?q=ca...zap.exe+&hl=en

I then used it separately for both the versions of .net (as you can also
find different commands for both versions in the above referred knowledge
base articles)

A reboot and again the installation failed (I was attempting install
from the newly downloaded redistributables)

And then I attempted a repair from the run command also mentioned in
these knowledge base articles, after which, interestingly enough, the
installs (both) succeeded.

Another visit to the windows update site followed and the updates
completed successfully. I am happy that I am out of this quagmire but I
wonder how many other problems sp2 will unfold in future.

For those who are prompted for the location of netfx.msi after trying to
install .net, they can extract it from dotnetfx.exe and then browse to that
location. To do this, download dotnetfx.exe or locate it on your local hard
drive or a CD. Then, from a command prompt run the following:
c:\dotnetfx.exe/t:c:\temp /c. You can substitute any folder you want for
the "c:\temp" parameter. This will extract netfx.msi to c:\temp if
dotnetfx.exe resides in c:\

I hope this helps solve the problem of all those who have failed to
update their .nets.

Thank you for your post. This problem is also plaqueing me.
I followed your procedure and got to this point:

KB 824643 - How to troubleshoot Microsoft .NET Framework 1.1 installation
issues section "Mnually remove and then reinstall the .NET Framework 1.1"
item 1e. I have 5 lines to Uninstall. When I attempt to uninstall them I
get "Internal Error 2711. S867460". I was hesitant to go any farther.

Any thoughts?

Dean

"Usman" <> wrote in message
news:...
> Well the problem has been long resolved, I did post the solution to
> different newsgroups, I had the same issue and somehow resolved it after
> visiting a couple of newsgroups and through my own experiments. I am
> pasting the contents of one of my posts that I posted a few days back in
> this newsgroup. Regarding the update successfully installing on windows
> 2000; the problem is not with the update but with sp2 which you must have
> installed before trying to upgrade .net. Do ask if there's any need for
> further clarification/help......Here is my post: -
>
> After encountering an update problem relating to both versions of
> Microsoft .net framework, I happened to visit windows update newsgroup and
> dotnet
> newsgroup and found every other person was having this problem.
> Incidentally this problem had happened with them after they had installed
> xp sp2. After a
> lot of browsing on Google and Microsoft knowledge base articles, I found
> the only solution to the problem was uninstalling both versions of .net
> and
> reinstalling them again. Interestingly sp2 had done enough damage to not
> allow repair of these programs. Now uninstall was another bigger problem,
> but thanks to the following knowledge base articles: -
>
> 1) Microsoft Knowledge Base Article - 320112 --- For removing Microsoft
> .NET Framework 1.0.3705
> 2) Microsoft Knowledge Base Article - 824643 --- For removing Microsoft
> .NET Framework 1.1
>
> And then I got stuck on using Msizap.exe utility, which wanted me to
> download Microsoft Windows Installer Software Development Kit (SDK). I
> accordingly went to the site for the download but found out that it was a
> pretty big job as it included other compulsory downloads. I failed after
> numerous tries to download as the site didn't allow using any download
> managers and using dial-up for huge downloads is definitely a problem. And
> then I searched for Msizap.exe utility on the net after I found out that
> sp2 supported this tool. I found it here: -
>
> Referrer
> http://www.google.com.pk/search?q=ca...zap.exe+&hl=en
>
> I then used it separately for both the versions of .net (as you can
> also find different commands for both versions in the above referred
> knowledge
> base articles)
>
> A reboot and again the installation failed (I was attempting install
> from the newly downloaded redistributables)
>
> And then I attempted a repair from the run command also mentioned in
> these knowledge base articles, after which, interestingly enough, the
> installs (both) succeeded.
>
> Another visit to the windows update site followed and the updates
> completed successfully. I am happy that I am out of this quagmire but I
> wonder how many other problems sp2 will unfold in future.
>
> For those who are prompted for the location of netfx.msi after trying
> to install .net, they can extract it from dotnetfx.exe and then browse to
> that
> location. To do this, download dotnetfx.exe or locate it on your local
> hard drive or a CD. Then, from a command prompt run the following:
> c:\dotnetfx.exe/t:c:\temp /c. You can substitute any folder you want for
> the "c:\temp" parameter. This will extract netfx.msi to c:\temp if
> dotnetfx.exe resides in c:\
>
> I hope this helps solve the problem of all those who have failed to
> update their .nets.
>
>
>

Hi Dean,
This is what the actual problem is. On most systems, this installer
would no be present and where it is present, it is corrupted for I don't
know what reasons.(That is why probably we are going through this hassle).
Don't worry, proceed to the next section, it will manually uninstall/delete
the remnants of dot net from your pc. Remember what you are doing here is
1) You are manually removing the dot net (which has been corrupted) from
your system, and
2) You are installing it again afresh to enable the upgrades to install
successfully.


"Dean H. Owens" <> wrote in message
news:vsRed.300$HA.64@attbi_s01...
> Thank you for your post. This problem is also plaqueing me.
> I followed your procedure and got to this point:
>
> KB 824643 - How to troubleshoot Microsoft .NET Framework 1.1 installation
> issues section "Mnually remove and then reinstall the .NET Framework 1.1"
> item 1e. I have 5 lines to Uninstall. When I attempt to uninstall them I
> get "Internal Error 2711. S867460". I was hesitant to go any farther.
>
> Any thoughts?
>
> Dean
>
> "Usman" <> wrote in message
> news:...
>> Well the problem has been long resolved, I did post the solution to
>> different newsgroups, I had the same issue and somehow resolved it after
>> visiting a couple of newsgroups and through my own experiments. I am
>> pasting the contents of one of my posts that I posted a few days back in
>> this newsgroup. Regarding the update successfully installing on windows
>> 2000; the problem is not with the update but with sp2 which you must have
>> installed before trying to upgrade .net. Do ask if there's any need for
>> further clarification/help......Here is my post: -
>>
>> After encountering an update problem relating to both versions of
>> Microsoft .net framework, I happened to visit windows update newsgroup
>> and dotnet
>> newsgroup and found every other person was having this problem.
>> Incidentally this problem had happened with them after they had installed
>> xp sp2. After a
>> lot of browsing on Google and Microsoft knowledge base articles, I found
>> the only solution to the problem was uninstalling both versions of .net
>> and
>> reinstalling them again. Interestingly sp2 had done enough damage to not
>> allow repair of these programs. Now uninstall was another bigger problem,
>> but thanks to the following knowledge base articles: -
>>
>> 1) Microsoft Knowledge Base Article - 320112 --- For removing
>> Microsoft .NET Framework 1.0.3705
>> 2) Microsoft Knowledge Base Article - 824643 --- For removing
>> Microsoft .NET Framework 1.1
>>
>> And then I got stuck on using Msizap.exe utility, which wanted me to
>> download Microsoft Windows Installer Software Development Kit (SDK). I
>> accordingly went to the site for the download but found out that it was a
>> pretty big job as it included other compulsory downloads. I failed after
>> numerous tries to download as the site didn't allow using any download
>> managers and using dial-up for huge downloads is definitely a problem.
>> And
>> then I searched for Msizap.exe utility on the net after I found out that
>> sp2 supported this tool. I found it here: -
>>
>> Referrer
>> http://www.google.com.pk/search?q=ca...zap.exe+&hl=en
>>
>> I then used it separately for both the versions of .net (as you can
>> also find different commands for both versions in the above referred
>> knowledge
>> base articles)
>>
>> A reboot and again the installation failed (I was attempting install
>> from the newly downloaded redistributables)
>>
>> And then I attempted a repair from the run command also mentioned in
>> these knowledge base articles, after which, interestingly enough, the
>> installs (both) succeeded.
>>
>> Another visit to the windows update site followed and the updates
>> completed successfully. I am happy that I am out of this quagmire but I
>> wonder how many other problems sp2 will unfold in future.
>>
>> For those who are prompted for the location of netfx.msi after trying
>> to install .net, they can extract it from dotnetfx.exe and then browse to
>> that
>> location. To do this, download dotnetfx.exe or locate it on your local
>> hard drive or a CD. Then, from a command prompt run the following:
>> c:\dotnetfx.exe/t:c:\temp /c. You can substitute any folder you want for
>> the "c:\temp" parameter. This will extract netfx.msi to c:\temp if
>> dotnetfx.exe resides in c:\
>>
>> I hope this helps solve the problem of all those who have failed to
>> update their .nets.
>>
>>
>>
>
>

Hi!

Worked fine! All is well.

Thanks for helping,

Dean


"Usman" <> wrote in message
news:%...
> Hi Dean,
> This is what the actual problem is. On most systems, this installer
> would no be present and where it is present, it is corrupted for I don't
> know what reasons.(That is why probably we are going through this hassle).
> Don't worry, proceed to the next section, it will manually
> uninstall/delete the remnants of dot net from your pc. Remember what you
> are doing here is
> 1) You are manually removing the dot net (which has been corrupted)
> from your system, and
> 2) You are installing it again afresh to enable the upgrades to install
> successfully.
>
>
> "Dean H. Owens" <> wrote in message
> news:vsRed.300$HA.64@attbi_s01...
>> Thank you for your post. This problem is also plaqueing me.
>> I followed your procedure and got to this point:
>>
>> KB 824643 - How to troubleshoot Microsoft .NET Framework 1.1 installation
>> issues section "Mnually remove and then reinstall the .NET Framework 1.1"
>> item 1e. I have 5 lines to Uninstall. When I attempt to uninstall them
>> I get "Internal Error 2711. S867460". I was hesitant to go any farther.
>>
>> Any thoughts?
>>
>> Dean
>>
>> "Usman" <> wrote in message
>> news:...
>>> Well the problem has been long resolved, I did post the solution to
>>> different newsgroups, I had the same issue and somehow resolved it after
>>> visiting a couple of newsgroups and through my own experiments. I am
>>> pasting the contents of one of my posts that I posted a few days back in
>>> this newsgroup. Regarding the update successfully installing on windows
>>> 2000; the problem is not with the update but with sp2 which you must
>>> have installed before trying to upgrade .net. Do ask if there's any need
>>> for further clarification/help......Here is my post: -
>>>
>>> After encountering an update problem relating to both versions of
>>> Microsoft .net framework, I happened to visit windows update newsgroup
>>> and dotnet
>>> newsgroup and found every other person was having this problem.
>>> Incidentally this problem had happened with them after they had
>>> installed xp sp2. After a
>>> lot of browsing on Google and Microsoft knowledge base articles, I found
>>> the only solution to the problem was uninstalling both versions of .net
>>> and
>>> reinstalling them again. Interestingly sp2 had done enough damage to not
>>> allow repair of these programs. Now uninstall was another bigger
>>> problem,
>>> but thanks to the following knowledge base articles: -
>>>
>>> 1) Microsoft Knowledge Base Article - 320112 --- For removing
>>> Microsoft .NET Framework 1.0.3705
>>> 2) Microsoft Knowledge Base Article - 824643 --- For removing
>>> Microsoft .NET Framework 1.1
>>>
>>> And then I got stuck on using Msizap.exe utility, which wanted me to
>>> download Microsoft Windows Installer Software Development Kit (SDK). I
>>> accordingly went to the site for the download but found out that it was
>>> a pretty big job as it included other compulsory downloads. I failed
>>> after
>>> numerous tries to download as the site didn't allow using any download
>>> managers and using dial-up for huge downloads is definitely a problem.
>>> And
>>> then I searched for Msizap.exe utility on the net after I found out that
>>> sp2 supported this tool. I found it here: -
>>>
>>> Referrer
>>> http://www.google.com.pk/search?q=ca...zap.exe+&hl=en
>>>
>>> I then used it separately for both the versions of .net (as you can
>>> also find different commands for both versions in the above referred
>>> knowledge
>>> base articles)
>>>
>>> A reboot and again the installation failed (I was attempting install
>>> from the newly downloaded redistributables)
>>>
>>> And then I attempted a repair from the run command also mentioned in
>>> these knowledge base articles, after which, interestingly enough, the
>>> installs (both) succeeded.
>>>
>>> Another visit to the windows update site followed and the updates
>>> completed successfully. I am happy that I am out of this quagmire but I
>>> wonder how many other problems sp2 will unfold in future.
>>>
>>> For those who are prompted for the location of netfx.msi after trying
>>> to install .net, they can extract it from dotnetfx.exe and then browse
>>> to that
>>> location. To do this, download dotnetfx.exe or locate it on your local
>>> hard drive or a CD. Then, from a command prompt run the following:
>>> c:\dotnetfx.exe/t:c:\temp /c. You can substitute any folder you want
>>> for the "c:\temp" parameter. This will extract netfx.msi to c:\temp if
>>> dotnetfx.exe resides in c:\
>>>
>>> I hope this helps solve the problem of all those who have failed to
>>> update their .nets.
>>>
>>>
>>>
>>
>>
>
>

Congrats.

"Dean H. Owens" <> wrote in message
news:Z1gfd.423259$mD.108402@attbi_s02...
> Hi!
>
> Worked fine! All is well.
>
> Thanks for helping,
>
> Dean
>
>
> "Usman" <> wrote in message
> news:%...
>> Hi Dean,
>> This is what the actual problem is. On most systems, this installer
>> would no be present and where it is present, it is corrupted for I don't
>> know what reasons.(That is why probably we are going through this
>> hassle). Don't worry, proceed to the next section, it will manually
>> uninstall/delete the remnants of dot net from your pc. Remember what you
>> are doing here is
>> 1) You are manually removing the dot net (which has been corrupted)
>> from your system, and
>> 2) You are installing it again afresh to enable the upgrades to
>> install successfully.
>>
>>
>> "Dean H. Owens" <> wrote in message
>> news:vsRed.300$HA.64@attbi_s01...
>>> Thank you for your post. This problem is also plaqueing me.
>>> I followed your procedure and got to this point:
>>>
>>> KB 824643 - How to troubleshoot Microsoft .NET Framework 1.1
>>> installation issues section "Mnually remove and then reinstall the .NET
>>> Framework 1.1" item 1e. I have 5 lines to Uninstall. When I attempt to
>>> uninstall them I get "Internal Error 2711. S867460". I was hesitant to
>>> go any farther.
>>>
>>> Any thoughts?
>>>
>>> Dean
>>>
>>> "Usman" <> wrote in message
>>> news:...
>>>> Well the problem has been long resolved, I did post the solution to
>>>> different newsgroups, I had the same issue and somehow resolved it
>>>> after visiting a couple of newsgroups and through my own experiments. I
>>>> am pasting the contents of one of my posts that I posted a few days
>>>> back in this newsgroup. Regarding the update successfully installing on
>>>> windows 2000; the problem is not with the update but with sp2 which you
>>>> must have installed before trying to upgrade .net. Do ask if there's
>>>> any need for further clarification/help......Here is my post: -
>>>>
>>>> After encountering an update problem relating to both versions of
>>>> Microsoft .net framework, I happened to visit windows update newsgroup
>>>> and dotnet
>>>> newsgroup and found every other person was having this problem.
>>>> Incidentally this problem had happened with them after they had
>>>> installed xp sp2. After a
>>>> lot of browsing on Google and Microsoft knowledge base articles, I
>>>> found the only solution to the problem was uninstalling both versions
>>>> of .net and
>>>> reinstalling them again. Interestingly sp2 had done enough damage to
>>>> not allow repair of these programs. Now uninstall was another bigger
>>>> problem,
>>>> but thanks to the following knowledge base articles: -
>>>>
>>>> 1) Microsoft Knowledge Base Article - 320112 --- For removing
>>>> Microsoft .NET Framework 1.0.3705
>>>> 2) Microsoft Knowledge Base Article - 824643 --- For removing
>>>> Microsoft .NET Framework 1.1
>>>>
>>>> And then I got stuck on using Msizap.exe utility, which wanted me to
>>>> download Microsoft Windows Installer Software Development Kit (SDK). I
>>>> accordingly went to the site for the download but found out that it was
>>>> a pretty big job as it included other compulsory downloads. I failed
>>>> after
>>>> numerous tries to download as the site didn't allow using any download
>>>> managers and using dial-up for huge downloads is definitely a problem.
>>>> And
>>>> then I searched for Msizap.exe utility on the net after I found out
>>>> that sp2 supported this tool. I found it here: -
>>>>
>>>> Referrer
>>>> http://www.google.com.pk/search?q=ca...zap.exe+&hl=en
>>>>
>>>> I then used it separately for both the versions of .net (as you can
>>>> also find different commands for both versions in the above referred
>>>> knowledge
>>>> base articles)
>>>>
>>>> A reboot and again the installation failed (I was attempting install
>>>> from the newly downloaded redistributables)
>>>>
>>>> And then I attempted a repair from the run command also mentioned in
>>>> these knowledge base articles, after which, interestingly enough, the
>>>> installs (both) succeeded.
>>>>
>>>> Another visit to the windows update site followed and the updates
>>>> completed successfully. I am happy that I am out of this quagmire but I
>>>> wonder how many other problems sp2 will unfold in future.
>>>>
>>>> For those who are prompted for the location of netfx.msi after
>>>> trying to install .net, they can extract it from dotnetfx.exe and then
>>>> browse to that
>>>> location. To do this, download dotnetfx.exe or locate it on your local
>>>> hard drive or a CD. Then, from a command prompt run the following:
>>>> c:\dotnetfx.exe/t:c:\temp /c. You can substitute any folder you want
>>>> for the "c:\temp" parameter. This will extract netfx.msi to c:\temp if
>>>> dotnetfx.exe resides in c:\
>>>>
>>>> I hope this helps solve the problem of all those who have failed to
>>>> update their .nets.
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>