Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Silent install, repair and uninstall command lines for the .NET Framework 4

Silent install, repair and uninstall command lines for the .NET Framework 4

Rate This

I have previously posted command lines that can be used to install, repair and uninstall the versions of the .NET Framework in silent mode and unattended mode.  Now that the .NET Framework 4 has shipped, I wanted to post an equivalent set of steps to install, repair and uninstall the .NET Framework 4 Client Profile and Full.

The .NET Framework 4 uses a different setup chainer than in previous versions of the .NET Framework.  As a result, the command lines are somewhat different than in previous releases.  There are also a few differences in how the repair and uninstall processes work that I wanted to call out specifically:

  • There are different repair and uninstall command lines for 32-bit and 64-bit versions of the .NET Framework 4
  • The .NET Framework 4 includes both a client profile and a full version.  Uninstalling the full version requires 2 steps – one to uninstall the extended component and another to uninstall the client profile.

.NET Framework 4 product family

.NET Framework 4 Client Profile (32-bit) – silent repair

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart

.NET Framework 4 Client Profile (32-bit) – unattended repair

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /passive /norestart

.NET Framework 4 Client Profile (32-bit) – silent uninstall

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /uninstall /x86 /x64 /parameterfolder Client /q /norestart

.NET Framework 4 Client Profile (32-bit) – unattended uninstall

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /uninstall /x86 /x64 /parameterfolder Client /passive /norestart

.NET Framework 4 Client Profile (64-bit) – silent repair

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart

.NET Framework 4 Client Profile (64-bit) – unattended repair

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /passive /norestart

.NET Framework 4 Client Profile (64-bit) – silent uninstall

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /uninstall /x86 /x64 /parameterfolder Client /q /norestart

.NET Framework 4 Client Profile (64-bit) – unattended uninstall

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /uninstall /x86 /x64 /parameterfolder Client /passive /norestart

.NET Framework 4 Full (32-bit) – silent repair

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart

.NET Framework 4 Full (32-bit) – unattended repair

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /passive /norestart

.NET Framework 4 Full (32-bit) – silent uninstall

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Extended\setup.exe /uninstall /x86 /x64 /ia64 /parameterfolder Extended /q /norestart

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /uninstall /x86 /x64 /parameterfolder Client /q /norestart

.NET Framework 4 Full (32-bit) – unattended uninstall

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Extended\setup.exe /uninstall /x86 /x64 /ia64 /parameterfolder Extended /passive /norestart

%windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Client\setup.exe /uninstall /x86 /x64 /parameterfolder Client /passive /norestart

.NET Framework 4 Full (64-bit) – silent repair

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /q /norestart

.NET Framework 4 Full (64-bit) – unattended repair

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /repair /x86 /x64 /ia64 /parameterfolder Client /passive /norestart

.NET Framework 4 Full (64-bit) – silent uninstall

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Extended\setup.exe /uninstall /x86 /x64 /ia64 /parameterfolder Extended /q /norestart

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /uninstall /x86 /x64 /parameterfolder Client /q

.NET Framework 4 Full (64-bit) – unattended uninstall

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Extended\setup.exe /uninstall /x86 /x64 /ia64 /parameterfolder Extended /passive /norestart

%windir%\Microsoft.NET\Framework64\v4.0.30319\SetupCache\Client\setup.exe /uninstall /x86 /x64 /parameterfolder Client /passive /norestart 

<update date="6/1/2010"> Fixed incorrect command lines for uninstall of the .NET Framework 4 extended. </update>

 

  • I tried to use the full silent uninstall command lines, but they didn't work. The first command line should use the extended directory instead of the client directory!

    %windir%\Microsoft.NET\Framework\v4.0.30319\SetupCache\Extended\setup.exe /uninstall /x86 /x64 /ia64 /parameterfolder Extended /q /norestart

  • Hi Dennis Bakker - Thanks for the heads up.  I've fixed the command lines in this blog post and in the one at blogs.msdn.com/.../9553804.aspx.

  • I see all the repair & uninstall links, but no links for silent install.  I followed the link to the deployment guide, but don't see them there either.

  • Hi Brian - The deployment guide that I linked at the top of this blog post contains a section titled Command-Line Options (available at msdn.microsoft.com/.../ee942965(v=VS.100).aspx).  In that section, there is documentation about the /q, /passive and /norestart switches that you can use for silent and/or unattended installation of the .NET Framework 4.  Please let me know if you have any issues getting these command line switches to work in your scenarios.

  • Hi Aaron,

    Could you please clarify the difference between error codes 1614 and 3010? In “.NET Framework Deployment Guide for Administrators” they both are described as “A restart is required to complete the installation. This message indicates success”.

    Thanks in advance

  • Hi Pronichkin - It looks like there is a typo in that user's guide.  I think it should list error code 1641 instead of 1614.  That is one of the standard Windows Installer error codes listed at msdn.microsoft.com/.../aa368542.aspx.  I've never actually encountered a 1641 error code before - I always see 3010.  I think the difference is that with 1641, Windows Installer will initiate a reboot for you automatically (unless you use the norestart switch), whereas with 3010, Windows Installer is telling you that a reboot is needed but will not initiate one automatically.  I think you should plan on using the norestart switch in your deployment scenarios, and if you do that, you shouldn't need to handle 1641 any differently than 3010.

  • Hi Pronichkin - It looks like there is a typo in that user's guide.  I think it should list error code 1641 instead of 1614.  That is one of the standard Windows Installer error codes listed at msdn.microsoft.com/.../aa368542.aspx.  I've never actually encountered a 1641 error code before - I always see 3010.  I think the difference is that with 1641, Windows Installer will initiate a reboot for you automatically (unless you use the norestart switch), whereas with 3010, Windows Installer is telling you that a reboot is needed but will not initiate one automatically.  I think you should plan on using the norestart switch in your deployment scenarios, and if you do that, you shouldn't need to handle 1641 any differently than 3010.

  • I have a Toshiba Satellite L505 lap top and I keep getting an error message saying that I need to install .Net Framework version v4.0.30319

    Can anyone help me with this. I have no clue.

    Thanks

  • Hi Dennis - You should be able to download and install the .NET Framework 4 from www.microsoft.com/.../details.aspx to solve this type of error.

  • my SONY VAIO was upgraded to Windows 7 and we added Norton 360. Now it won't access the internet, giving me a message that NET Framework version 4 needs to be repaired. As a novice, I have no clue how to repair, and I begin classes in two weeks. Any advice would be much appreciated. Thanks, and more thanks in advance.

  • Hi JapaneseOma - You can repair the .NET Framework 4 by using the entries that it creates in the Programs and Features control panel on your computer.  They will be named "Microsoft .NET Framework 4 Extended" and "Microsoft .NET Framework 4 Client Profile".  Hopefully this will help in your scenario.

  • Hi Astebner-Thank you for the link to fix this .Net Framework error message. When I go to the link, I see I am installing .Net Framework 4. Is this the same as v4.0.30319? I am confused because the download does not mention this version at all. The error message says that I need to install .Net Framework version v4.0.30319. If I download the .Net Framework 4 will this do the trick? Thanks, Dennis

  • Hi Dennis - The final build number for the .NET Framework 4 is 4.0.30319, so yes, the .NET Framework 4 is what you want if you are seeing an error message from a program that says it needs v4.0.30319.  Let me know if you have any trouble getting it to install on your system.

  • Hi Astebner-This version 4.0.30319 is already installed on my system but the error keeps appearing. What do you suggest I do about fixing this problem? Thanks.

  • Hi Dennis - I'd suggest trying to repair the .NET Framework 4 (both the Extended and Client components) by using the entries in the Programs and Features control panel.  If that doesn't help, then I'd suggest trying to uninstall + re-install the .NET Framework 4.

Page 1 of 7 (102 items) 12345»
Leave a Comment
  • Please add 3 and 7 and type the answer here:
  • Post