none
NET Framework installation mess RRS feed

  • Question

  • Hello,

    I have a laptop with Windows 7 64 bit. Recently it started to bug me for installing an update to Net Framework every time I turned it off. So I uninstalled all the versions of Net Framework using cleanup tool. However, I don't think it did the job because e.g. Paint.Net still runs on my computer without any problem, although I cannot see any versions of Net Framework in the Control Panel. Then I tried to install Net Framework 3.5 and later all the updates from version 4.0 that appeared in my Windows Update window. However, the computer shuts down during the installation. What is going on? And can anybody guide me through the complete clean reinstall of Net Framework? I include the log here: https://skydrive.live.com/redir?resid=CE568F5C1467DB0C!6375&authkey=!AHuObHE60dHR6xw

    Wednesday, June 26, 2013 8:29 PM

All replies

  • Windows 7 comes with .NET Framework 2.0/3.0/3.5 through 3.5 SP1 (AKA .NET 3.5.1) embedded in the OS. You (the user) cannot remove or install these versions.

    To assess your current situation, we need to see exactly which .NET versions are currently on your computer. Run this verification tool:

    http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

    When you tried to reinstall .NET 4.0, did the install fail?

    If so, provide your install logs as follows:

    Please collect your install logs with this:

    http://aka.ms/vscollect

    After you run Collect.exe, you'll find vslogs.cab in your %temp% directory. Please upload vslogs.cab to a public site, like SkyDrive, and post the link here.

    Thursday, June 27, 2013 1:24 PM
  • The verification tool log are here:

    http://sdrv.ms/11KREOT

    http://sdrv.ms/11KRGGk

    The installation log is at

    http://sdrv.ms/11KR8Aw

    When I try to install .NET 4.0 or .NET 4.5, the computer just shuts down in the middle of the installation, so I gather it was unsuccessful.


    Thursday, June 27, 2013 1:46 PM
  • There are no install logs for either .NET 4.0 or .NET 4.5 in your vslogs.cab.

    It appears that the actual installations never started.

    Your verification log shows .NET Framework 4.0 Client profile installed.

    Please rerun the verification tool with .NET 4.0 Client Profile selected, then post ONLY the LAST 15 lines of the tool log here.

    If the Client Profile verifies successfully, try the procedure below:

    Follow these steps exactly:

    Before trying to install .NET Framework 4.0, execute this command from an ELEVATED Command Prompt provided by the .NET Framework Team:

    "This issue is likely caused by a bad ACL on assembly\tmp folder. After installing updates, the ACL propagates to installed assembly folders in both 4.0 & legacy GAC.  If those updates were installed by WU or another user, the propagated ACL will prevent install of the same assembly by the current user.

    A work around would be to reset the ACL on GAC dirs.

    for /F %D in ('dir %WINDIR%\assembly %WINDIR%\Microsoft.NET\assembly /s /b /a:d') do takeown /F %D && icacls %D /reset /T"

    After running that command, follow these steps:

    Please follow these instructions exactly:

    1. Download a fresh copy of the standalone installer for .NET Framework 4.0:

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718

    2. Also, clear your %temp% directory and disable your AV software.

    The %temp% directory is a reference to the Temp folder associated with the current user. To clear it, do the following:

    Sign on to your system with the Administrator user account you will use to run the installer. Click the Start Orb and type %temp% in the search box. The search results will show the Temp folder you want. Click on the Temp folder to open it in Windows Explorer, then delete the entire contents.

    3. Run the standalone installer from step 1 As Administrator.

    Note: Just using an administrator account is NOT enough. To activate full privileges, you must right-click the installer, then select Run as administrator.

    If the install fails, provide complete install logs as follows:

    Please collect your install logs with this:

    http://aka.ms/vscollect

    After you run Collect.exe, you'll find vslogs.cab in your %temp% directory. Please upload vslogs.cab to a public site, like SkyDrive, and post the link here.

    Thursday, June 27, 2013 3:33 PM
  • Here are the last 15 lines of the verification tool log:

    [06/27/13,19:04:52] Key: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client
    	Value: InstallPath
    	Actual Data:	REGISTRY VALUE FOUND
    [06/27/13,19:04:52] Key: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client
    	Value: Servicing
    	Actual Data:	REGISTRY VALUE FOUND
    [06/27/13,19:04:52] Key: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client
    	Value: TargetVersion
    	Expected Data:	4.0.0
    	Actual Data:	4.0.0
    [06/27/13,19:04:52] Key: HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client
    	Value: Version
    	Actual Data:	REGISTRY VALUE FOUND
    [06/27/13,19:04:52] Section [Registry - .NET Framework 4 Client (Wow6432Node)] - stop parsing entries
    [06/27/13,19:04:52] Processing custom action 'Custom Action - .NET Framework 4.0 test application'
    [06/27/13,19:04:52] ExecutablePath = 'Netfx40TestApplication.exe'
    [06/27/13,19:04:52] FriendlyName = '.NET Framework 4 test application'
    [06/27/13,19:04:52] TimeoutSeconds = '300'
    [06/27/13,19:04:52] WaitOnExit = 'true'
    [06/27/13,19:04:52] Silent = 'true'
    [06/27/13,19:04:52] Launching process 'Netfx40TestApplication.exe' now
    [06/27/13,19:04:52] Process successfully launched. Waiting 300 seconds for it to complete.
    [06/27/13,19:04:55] Process 'Netfx40TestApplication.exe' exited with return code 0
    [06/27/13,19:04:55] Verification succeeded for product .NET Framework 4 Client

    Thursday, June 27, 2013 5:08 PM
  • OK, your .NET Framework 4.0 Client Profile verifies as correct.

    Now, please follow the steps in the procedure I provided in my previous post.

    Friday, June 28, 2013 2:11 PM
  • Thanks, I followed the procedure and everything seems to be OK. Now I have 13 updates to .NET Framework in my Windows Update window. Should I install them?
    Saturday, June 29, 2013 8:13 PM
  • If you have not already done so, I would run the verification tool with .NET Framework 4.0 (not Client Profile) selected, then observe the last few lines of the tool log. If the test application completed successfully (return code = 0), your installation of the full .NET Framework 4.0 is good.

    As far as the updates are concerned, I always install all important updates on my computers. I understand why you might be hesitant, but I'd do it.

    Saturday, June 29, 2013 11:14 PM
  • OK, I chose the option "install and turn off" in the Start menu and went to bed, so I didn't actually observe what was going on but last time I checked my computer was busy installing Update 1 of 13. Today when I restarted my computer I am still prompted to install all these updates. What is going on?
    Sunday, June 30, 2013 7:35 AM
  • It appears that you have issues with your Windows Update in your OS.

    I suggest you check to see if the updates were installed. If any were and you are still being prompted to install the updates, you will need to repair your Windows Update service. For explicit guidance on fixing WU, ask here:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update?tm=1372602877500

    Sunday, June 30, 2013 2:35 PM
  • According to the list in the Control Panel, the updates were not installed, so I went ahead and tried to install them. In the meantime their number had gone down magically from 13 to 8 (without me doing anything). And then the story repeats itself: I try to install the updates, an error message appears for a moment, so quickly that I couldn't read what it said, and then the computer shuts down. When I turn it on back again, the updates are still waiting to be installed. Any suggestions?
    Sunday, June 30, 2013 3:23 PM
  • The install logs for the updates may appear in a full log set. Please provide as follows:

    Please collect your install logs with this:

    http://aka.ms/vscollect

    After you run Collect.exe, you'll find vslogs.cab in your %temp% directory. Please upload vslogs.cab to a public site, like SkyDrive, and post the link here.

    Sunday, June 30, 2013 4:43 PM
  • The logs are here:

    http://sdrv.ms/158GELY

    Sunday, June 30, 2013 5:53 PM
  • I checked the first several of the Windows Update logs and found this error "Installation failed with error code: (0x0000066A),".

    This is a Windows Update issue.

    For explicit guidance on fixing WU, ask here:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update?tm=1372602877500

    Monday, July 1, 2013 2:02 PM