.NET framework 3.0 install fails with 1603!

Removed .NET Framework 3.0 (and 2.0 and 1.1) from my system because KB928365 did not stop to install successfully over and over again. Now I try to reinstall .NET Framework 3.0 and it fails with code 1603. Had a look at the error log and found:

"
*** Blocking Components exist and must be satisified before continuing to install ***
Microsoft .NET Framework 3.0 ist bereits installiert <--- ???? see below
*** End of Blocking Component List ***
Failed to pass the Warnings/Blocks checks in CVSScenario:Tongue Tiedtart()
Microsoft .NET Framework 3.0 Language Pack - DEU: [2] Error code 1603 for this component means "Schwerwiegender Fehler bei der Installation.
"

Microsoft .NET Framework 3.0 already installed??? Can't be!
There is no entry in my software list, no entry in my registry and vs_uninst_winfx.exe returns "products selected for deinstallation not found! "

Where do I go from there? Any help will be appreciated before I reinstall Windows!

Kind regards!

E.G.Gru

 

If you are certain that you actually need .NET Framework 3 then you should follow the MicroSoft instructions here.

If you are unsure whether you need it or not, you don't need it.

 

Thank you for sharing your ideas! However I've been trough all of this written at Microsofts to no avail ...

I am absolutely not worried about the missing .NET framework (but the rules say "... some applications may need .NET Framework ..." though), but I want to stop "MS Automatic Update" to keep downloading service for non-existing software and pestering me to apply! Then the apply fails (of course) and this game happens over and over and over again. There is no way to tell Automatic Update that I am sick and tired of this ...

I will have another go at the registry as soon as I can find some time ...

Kind regards

 

That isn't a critical update and you can deselect it at the MS Updater center. Tag the box labeled "Do not show this again" after clicking the + symbol next to the particular item. I'm sure you probably tried all that but I have to suggest it anyway to make the thread complete for others.

 

Weeeeell, that's only half a solution. Every single (new) service for framework will still be pestering me ...

Anyway, thank you very much again!

Cheers!

 

Ladies and gentlemen!

After a lengthy process I found out - the "real" problem the .NET framework 3.0 installation had was with .NET framework 2.0 (!!!) Corrected this problem and - everything works fine now!

But - please don't ask me what I think of a suite of programs which is not able to pass the "real" error to the user and leaves the user out there puzzled ...

N.B. "Lengthy process" - scanned all framework installation logs in the users TEMP folder. Unfortunately I have only the folder names in German:

C:\Dokumente und Einstellungen\...user name...\Lokale Einstellungen\Temp

Kind regards