Vista - Re: .net framework 1.1 installation error

"AbA" <AbA@discussions.microsoft.com> wrote in message
news:A9C30AAC-1C4E-41EA-9E61-21364D492E23@microsoft.com...
>I keep getting an error message when i try to install .net framework 1.1:
> Application has generated an exception that could not be handled
> ProcessId=0x1208 (4616), Thread id=0x10a0(4256)
> and variants of it.
>
> I'm running Vista Home Premium, and basically i've been trying to set up
> McAfee Backup - it requires .net 1.1, for some reason.
>
> I haven't been able to find anything on the web that seems to be
> applicable,
> and the McAfee tech rep tried to help, he said it's a microsoft issue.
> apparently, i'm the first customer with this sort of problem. appreciate
> any
> assistance.
>

I'll first apologize for not having a solution to your problem.
Can we assume you are running (or, trying to run) the latest version of the
McAfee product, certified by McAfee as Vista compatible?
Do the symptoms arise during the McAfee product install, or are you trying
to install .NET Framework v 1.1 as a separate entity?
I know Microsoft has stated that they are not supporting Visual Studio .NET
2003 (uses .NET Framework v1.1) in Vista, but as I've seen posts from users
claiming they have made it work (VS 2003, that is), it must be possible to
install .NET Framework v 1.1.
You'll note that I'm crossposting this to one of the Vista groups, in the
hope somebody there will have a solution for you.

microsoft.public.windows.vista.general

I use McAfee too. You have an account with McAfee which will let you
reinstall the software later. So if you are unable to turn off the firewall
and antivirus during the Windows Update procedure, just uninstall it until
all previous updates are complete. Also, do the install of net frameworks on
their own, without other updates at the same time and last. For example, if
you see a bunch of items in Windows Update then update the other items in one
pass, reboot and then when net framework updates are there alone just do them
isolated. I had trouble with the .NET Framework 3.0 end-user runtime for
WinXP and had to follow these steps.