Link to home
Start Free TrialLog in
Avatar of bwoolf01
bwoolf01

asked on

Vista-64 Windows Update and manual attempts fail to install .NET Framework 3.5?

How can I uninstall/reinstall the .NET Framework 3.5 in Vista-64?
Avatar of ilalopoulos
ilalopoulos
Flag of Greece image

You can find the information you want at: http://blogs.msdn.com/astebner/archive/2008/08/01/8803442.aspx

Look at the Vista Windows Server 2008 Instructions.

(Note: In control panel's Programs and Features, if you see only the installed programs select the option 'View installed updates' on the left side.)

If you are succesfull with the uninstall, download the dotnetfx35.exe from microsoft's site, this is the .NET 3.5 Service Pack 1 with updates also for .NET 2.0 and .NET 3.0 and install it.

Good Luck
Avatar of bwoolf01
bwoolf01

ASKER

Thanx ilalopoulos for your timely response.
Will try your proposed solution tonight at home.
Do you know if "dotnetfx35.exe" will work for Vista-64??

Yes, it will.
ilalopoulos,
Unfortunately, no success with that approach last night.

- Apparently there were no Framework versions installed other than those within the OS. (2.0 and 3.0)
- There were no other updates installed.
- dotnetfx35.exe failed during setup.

I then used the cleanup tool to wipe the failed installations.

Attempted to load the Frameworks individually (manually) and sequentially on Vista.
Was able to successfully load 3.5, but am not able to update it to SP1 either manually or through Windows Update.  Windows Update is trying to install 3.5 SP1 but the install fails.  Other unrelated Windows Update installs are working.

So I believe I've isolated the problem to the need to upgrade Framework 3.5 to SP1, but am unable to do that.  Am worried that I have not been able to apply all of the necessary upgrades and SPs to prior versions.  When I tried to update 2.0 to SP1 I got a message that the (manual) upgrade would not run on Vista.  Same thing when I tried to update 3.0 to SP1.  But 3.5 installed fine (manually) on its own.  Just can't seem to apply the SPs.  Feel like I'm stuck in an endless loop.

Would appreciate any suggestions before I bite the bullet and reinstall the OS.

Thanx,
bwoolf
Sorry to hear that your pc still has the problem.

A 2nd approach: visit the Unified .NET Framework Troubleshooting Guide at http://blogs.msdn.com/astebner/articles/454956.aspx

You will find:
tons of specific information on .net framework installation, tools that you can use to clean .net installations and among other the locations of the logs, where you can see why the installation failed.

Give it a try and let me know.

John
John

I have this version of 3.5 installed:

http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en

It includes 2.0, 2.0SP1, 3.0, 3.0SP1.

Where do you suggest I start tonight??
ASKER CERTIFIED SOLUTION
Avatar of ilalopoulos
ilalopoulos
Flag of Greece image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
John,
First let me thank you for your attention and advice.
-Am running Windows Vista Ultimate Service Pack 1 (not RC)
-new blog advice had not helped.

Unfortunately, nothing has changed.

Output from log of failed .NET 3.5 SP1 install is below.

It indicates that .NET Framework 2.0SP1 (x64) (CBS) is not installed.
but my installation of 3.5 should have included 2.0SP1 ???
Do I need an (x64) version of 3.5??


[05/12/09,21:04:18] Microsoft .NET Framework 2.0SP1 (x64) (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (x64) (CBS). MSI returned error code 87
[05/12/09,21:04:28] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0SP1 (x64) (CBS) is not installed.
[05/12/09,21:18:43] Microsoft .NET Framework 2.0SP1 (x64) (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (x64) (CBS). MSI returned error code 87
[05/12/09,21:18:52] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0SP1 (x64) (CBS) is not installed.
[05/12/09,21:38:46] Microsoft .NET Framework 2.0SP1 (x64) (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (x64) (CBS). MSI returned error code 87
[05/12/09,21:38:58] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0SP1 (x64) (CBS) is not installed.
[05/12/09,22:27:33] Microsoft .NET Framework 2.0SP1 (x64) (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (x64) (CBS). MSI returned error code 87
[05/12/09,22:27:44] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0SP1 (x64) (CBS) is not installed.
[05/14/09,09:57:13] Microsoft .NET Framework 2.0SP1 (x64) (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (x64) (CBS). MSI returned error code 87
[05/14/09,09:57:24] WapUI: [2] DepCheck indicates Microsoft .NET Framework 2.0SP1 (x64) (CBS) is not installed.

Open in new window

I quote from this blog http://blogs.msdn.com/astebner/archive/2007/05/07/2465257.aspx :

"Error code 87 for these service packs mean that the package could not be installed due to an error with the command line parameters.  In this case, the problem is that the path to the service pack setup file contains a space in it (c:\Downloaded Files), and there is a bug in .NET Framework 3.5 beta 1 setup where it does not correctly put quotes around paths with spaces in them.

How to resolve the error

If you run into this issue while attempting to install the .NET Framework 3.5 beta 1 and Visual Studio Orcas beta 1 setup, you will need to move the setup files to a folder that does not contain spaces in the name and then re-run setup."

the same resolution in http://social.msdn.microsoft.com/Forums/en-US/vs2008prereleaseinstallandsetup/thread/cd28b452-c362-4dc6-9faf-0e8767dace22
in this page look also at the last comment from mr Jul
What does MrJul mean by

"going to the WCU\dotNetFramework\dotNetMSP\x86" ???
WCU stands for Windows Component Update.

What he means is that he accessed the WCU directory of dotnetfx35.exe directly by going to the unpacked contents. If you can't find the directory where the unpacked files are, you can extract its contents - try right clicking on it and select extract (I am using winrar for this).



John,
I can't tell you how much I appreciate your help.
You have been there for me every step of the way.

I wish I could tell you that this worked, but the reality is that I am running out of time.
Working on my daughter's laptop and she must return to school this weekend.

So we have both decided to proceed with the OS re-install.

Thank You so much for your efforts.

bwoolf
You are welcome bwoolf :D
ilalopoulos provided timely and excellent advice and links to appropriate solutions for my issue.  Unfortunately, I was not able to resolve my particular problem and ran out of time. My daughter had to return to college, so we decided to reinstall the OS, which did resolve my problem.