Re: Found something Interesting .net framework updates

Wow,

For a novice like me having this same problem the fix seems rather daunting!
I'm going to try it because this stupid update has also caused other
installations to fail on my PC. Everything I try to load tells me that a
".net installation has been suspended". I am them prompted to roll back
that install......which of course fails.


"Captain" <> wrote in message
news:10A988B0-F05B-4223-9EB3-...
> 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 cmd 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.
>

Surely with all the problems regarding this update it should be withdrawn
and replaced with an update that installs seemlessly.
To me that seems sensible!

"Kevin D" <> wrote in message
news:ucl7V%...
> Wow,
>
> For a novice like me having this same problem the fix seems rather
> daunting! I'm going to try it because this stupid update has also caused
> other installations to fail on my PC. Everything I try to load tells me
> that a ".net installation has been suspended". I am them prompted to roll
> back that install......which of course fails.
>
>
> "Captain" <> wrote in message
> news:10A988B0-F05B-4223-9EB3-...
>> 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 cmd 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.
>>
>
>

What we must try to understand here is that the problem is not being caused
by the updates but by sp2. And as I wrote earlier that after reinstalling
both versions of .net, I updated my system through the same wu site which was
initially refusing to install these updates on my pc. sp2 even caused
disappearance of the installers, due to which the repair option was not
available. So if you are into this problem, dont wait for any replaced
updates, may be even sp3 wouldnt roll back the damage done.


"Fergie" wrote:

> Surely with all the problems regarding this update it should be withdrawn
> and replaced with an update that installs seemlessly.
> To me that seems sensible!
>
> "Kevin D" <> wrote in message
> news:ucl7V%...
> > Wow,
> >
> > For a novice like me having this same problem the fix seems rather
> > daunting! I'm going to try it because this stupid update has also caused
> > other installations to fail on my PC. Everything I try to load tells me
> > that a ".net installation has been suspended". I am them prompted to roll
> > back that install......which of course fails.
> >
> >
> > "Captain" <> wrote in message
> > news:10A988B0-F05B-4223-9EB3-...
> >> 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 cmd 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.
> >>
> >
> >
>
>
>

Wish you good luck. Post back if you need any help.

"Kevin D" wrote:

> Wow,
>
> For a novice like me having this same problem the fix seems rather daunting!
> I'm going to try it because this stupid update has also caused other
> installations to fail on my PC. Everything I try to load tells me that a
> ".net installation has been suspended". I am them prompted to roll back
> that install......which of course fails.
>
>
> "Captain" <> wrote in message
> news:10A988B0-F05B-4223-9EB3-...
> > 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 cmd 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.
> >
>
>
>

I think I did it all.......one Update just disappeared, or isn't needed
anymore, not sure. The other update V1.1 still will not install.


"Captain" <> wrote in message
news:E440163C-74AE-4B2C-B3EF-...
> Wish you good luck. Post back if you need any help.
>
> "Kevin D" wrote:
>
>> Wow,
>>
>> For a novice like me having this same problem the fix seems rather
>> daunting!
>> I'm going to try it because this stupid update has also caused other
>> installations to fail on my PC. Everything I try to load tells me that a
>> ".net installation has been suspended". I am them prompted to roll back
>> that install......which of course fails.
>>
>>
>> "Captain" <> wrote in message
>> news:10A988B0-F05B-4223-9EB3-...
>> > 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 cmd 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.
>> >
>>
>>
>>

Dear Kevin,
Well, in my opinion there are two possiblities for the disappeared update,
one that, the update is installed (you can confirm this by going to 'View
installation history') and the other that, .net framework 1.0 isnt installed
on your computer anymore. Did you install it again?

Moreover, the old .net 1.1 is still in your computer. Are you sure you
followed the procedure described in Microsoft Knowledge Base Article -
824643? Remember there are different procedures described for both versions
in the two knowledge base articles. Especially the one related to Msizap.exe
utility. Do it again and then install .net 1.1 again, if it still doesnt
succeed try to repair it using this command: -

InstallationSource\dotnetfx.exe /t:%temp% /c:"msiexec.exe /fvecms
%temp%\netfx.msi"

Post back if there is no success with a little bit more detail.

Usman


"Kevin D" wrote:

> I think I did it all.......one Update just disappeared, or isn't needed
> anymore, not sure. The other update V1.1 still will not install.
>
>
> "Captain" <> wrote in message
> news:E440163C-74AE-4B2C-B3EF-...
> > Wish you good luck. Post back if you need any help.
> >
> > "Kevin D" wrote:
> >
> >> Wow,
> >>
> >> For a novice like me having this same problem the fix seems rather
> >> daunting!
> >> I'm going to try it because this stupid update has also caused other
> >> installations to fail on my PC. Everything I try to load tells me that a
> >> ".net installation has been suspended". I am them prompted to roll back
> >> that install......which of course fails.
> >>
> >>
> >> "Captain" <> wrote in message
> >> news:10A988B0-F05B-4223-9EB3-...
> >> > 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 cmd 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.
> >> >
> >>
> >>
> >>
>
>
>