Groups | Blog | Home
all groups > dotnet setup > december 2004 >

dotnet setup : .NET Framework 1.1 SP1 and WU


M.B. Schiekel
12/6/2004 5:27:42 PM
Hi all,

sorry to came again with a NET Framework 1.1 SP1 installation problem.

1. Win-XP-SP2 machine with a .NET 1.1.4322 Version + German language
pack above on a .NET 1.0.3705 (German version) above on a .NET 1.0.3705
(English version).

2. Windows Update started a download and installation of .NET Framework
1.0-SP3, but crashed the installation with error: E0434F4D.

3. Following KB-article Q320112 (Installation of .NET Framework Fails
and Requires Manual Removal) I deinstalled manually:
..NET 1.0.3705 english: {B43357AA-3A6D-4D94-B56E-43C44D09E548}
..NET 1.0.3705 german : {20F1FFAF-1BFF-450C-A8C7-03D1BE24B950}
..NET 1.1.4322 : {CB2F7EDD-9D1F-43C1-90FC-4F52EAE172A1}
Registry entries were removed with msizap.exe

4. New installation of .NET 1.1.4322 from Win-XP-SP2 CD installed .NET
1.1 and .NET German-Language-Pack correct. But with the 3. part of this
installation, the .NET-Framework-1.1-SP1 there was again a runtime
exception crash.

5. A manual installation of the .NET-Framework-1.1-SP1 with
NDP1.1SP1-KB867460-X86.exe /xp
and
msiexec /p S867460.msp
worked Ok.

6. But now the Windows Update again tries to install (I suppose
unnecessarily ?) .NET Framework 1.0-SP3, and again crashes with error:
E0434F4D.
I cleared the IE-cache, IE-history, WUTemp directory.
What else could be done, to clean the system and/or the Windows Update
history in this .NET framework-SP issue?

Any hints are very welcome.
Thanks in advance

M.B. Schiekel
12/28/2004 5:28:03 PM
M.B. Schiekel schrieb:

[quoted text, click to view]


Hi all,

in a former email I described, how to deal with error E0434F4D in
..NET-SPx installations and how to remove a .NET 1.0.3705 installation
manually according to KB-article Q320112, so that a .NET 1.1.4322-SP1
could manually be installed.
Unfortunately Windows Update again and again tries to install a .NET
Framework 1.0-SP3 (unsuccessful).

By comparison with a another plain windows-xp-.NET 1.1.4322 machine I
found out, that the method to overcome this WU-problem is to delete all
..NET 1.0.3705 keys in the windows-xp-registry in:
HKEY_LOCAL_MACHINE/Software/Microsoft/ActiveSetup/InstalledComponents/


With best wishes for a healthy and happy New Year for everybody -
bernhard
AddThis Social Bookmark Button