.Net Framework 1.1 SP1 stalls during installation

Whenever I select .Net Framework 1.1 SP1 from the list of avaiable updates
to install, it downloads OK (about 10MB), launches, starts to run and stops
with a generic failure indicatino.

Has anyone experienced this same problem? Solution?

"Fred Morrison" wrote:

> Whenever I select .Net Framework 1.1 SP1 from the list of avaiable updates
> to install, it downloads OK (about 10MB), launches, starts to run and stops
> with a generic failure indicatino.
>
> Has anyone experienced this same problem? Solution?
>
Regarding your first question: I have to say yes. I'm affraid I don't have a
solution yet but you are not on your own.

Here's what works:
1. download both the base .Net Framework 1.1 and the Service Pack 1.
2. disconnect from the Internet (because of the next few steps). In my
case, it's just a matter of turning the 802.11g wireless switch on the lid
of my computer to the OFF position.
3. Follow as much of KB article 824643. Much of it failed for me, but when
something wouldn't uninstall by right-clicking on the .msi file in
C:\<windir>\Installer\, I just deleted it manually and rebooted (several
times ;-)
4. Use MSCONFIG.EXE as specified in KB 824643 to do a clean boot with the
exception of allowing the Installer service to run. Then reboot. Since
Norton Internet Security 2004 and Norton Antivirus aren't running due to the
clean boot, it makes step 2 make more sense, I hope.
5. Install .Net Framework 1.1 and reboot (it goes away because of KB 824643)
6. Install .Net Framework 1.1 Service Pack 1. Before rebooting, use
MSCONFIG.EXE to return to a normal boot.
7. In my case, while the computer reboots, I slide the 802.11g wireless
switch back to the ON position.

Conclusion: Microsoft has to clean up this process. We can't go though the
agony of KB 824643 just to install .Net Framework 1.1 Service Pack 1.

"Joel Hendrix [MSFT]" <> wrote in message
news:...
> Add the following registry key and values to enable MSI logging (be sure
> to
> remove it when you no longer need it):
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Win dows\Installer]
> "Debug"=dword:00000003
> "Logging"="voicewarmup"
>
> This will create a file with the name MSI*.log (where * is a sequence of
> random alpha-numeric characters) in your %temp% folder. If you could post
> the last 10-20 lines from the log when the install hangs we could take a
> look.
>
> -Joel
> --------------------
>>From: "Fred Morrison" <>
>>Subject: Framework 1.1 SP1 starts install, then hangs
>>Date: Thu, 18 Nov 2004 18:46:46 -0500
>>Lines: 13
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>>X-RFC2646: Format=Flowed; Original
>>Message-ID: <>
>>Newsgroups: microsoft.public.dotnet.framework.setup
>>NNTP-Posting-Host: pool-138-88-28-218.res.east.verizon.net 138.88.28.218
>>Path:
> cpmsftngxa10.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFT NGXA01.phx.gbl!TK2MSFTNGP0
> 8.phx.gbl!tk2msftngp13.phx.gbl
>>Xref: cpmsftngxa10.phx.gbl microsoft.public.dotnet.framework.setup:9370
>>X-Tomcat-NG: microsoft.public.dotnet.framework.setup
>>
>>I can start the Framework 1.1 SP1 install, which launches, starts to run
> and
>>then hangs with 2 progress bars until I have to kill the application and
>>reboot. Has anyone experienced this same problem?
>>
>>Is there an install log that I can examine to help me understand where it
>>hung and possibly why?
>>
>>I'm using the Framework 1.1 SP1 that comes on the disk 1306.7, dated
>>December 2004. That CD has several things on it. I used this file:
>>
>><drive letter>:\ENGLISH\NET_FRAMEWORK1.1\SP1\NDP1.1SP1-KB867460-X86.EXE
>>
>>
>>
>
> This reply is provided AS IS, without warranty (express or implied).
>


"ArVie" <> wrote in message
news21FCBE3-6E60-4082-9F58-...
>
>
> "Fred Morrison" wrote:
>
>> Whenever I select .Net Framework 1.1 SP1 from the list of avaiable
>> updates
>> to install, it downloads OK (about 10MB), launches, starts to run and
>> stops
>> with a generic failure indicatino.
>>
>> Has anyone experienced this same problem? Solution?
>>
> Regarding your first question: I have to say yes. I'm affraid I don't have
> a
> solution yet but you are not on your own.