Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

How do I install .NET 4 on Windows Server 2008 R2 from the command line or PowerShell?

This post shows how to do it for .NET 3.5 using dism.exe and PowerShell. I am guessing that, since the .NET 4.0 binaries need to be downloaded first, these instructions do not work for .NET 4.

share|improve this question
    
Do you mean 2008 R2? Or do you actually mean RC2 as in a release candidate? –  Ryan Bolger May 31 '11 at 16:20
    
R2 - sorry about that –  house9 Jun 1 '11 at 20:55
1  
Your question might get more views if you edit it to fix the mistake. You should also probably update your windows-server-2008 tag to windows-server-2008-r2. –  Ryan Bolger Jun 1 '11 at 23:39

2 Answers 2

up vote 7 down vote accepted

I have done the following in Powershell:

((new-object net.webclient).DownloadFile("http://download.microsoft.com/download/9/5/A/95A9616B-7A37-4AF6-BC36-D6EA96C8DAAE/dotNetFx40_Full_x86_x64.exe","dotNetFx40_Full_x86_x64.exe")) 
& .\dotNetFx40_Full_x86_x64.exe /q

There are other command line options than /q (for quiet). You can see those by doing:

& .\dotNetFx40_Full_x86_x64.exe /?

MessageBox resulting from running installer with the /? switch

share|improve this answer
    
When I run /? I get nothing ... –  jcolebrand Sep 13 '12 at 14:39
    
Are you on a windows core system (with no GUI)? The help pops up in a window on my machine. Can you run the installer without the /? switch? –  steenhulthin Sep 13 '12 at 18:05
    
The only other thing I can think of is that you don't have permissions to run the installer. –  steenhulthin Sep 13 '12 at 18:08
    
I may not have let it get that far? I expect those sorts of windows to come up right away, and instead it started rolling scrollbars, etc. –  jcolebrand Sep 13 '12 at 18:33
    
:) I agree that solution Microsoft came up with here is not really elegant. It is quite clunky to get a message box returned from a command line command. –  steenhulthin Sep 13 '12 at 18:48

This isn't specific to powershell, but might be of help. After installing .NET3.5 we follow up using the full install binaries, simply running a silent install. Depending on what and how you install this may require a reboot.

This how I've run silent installs of .NET4 in build/update scripts on 2003-2008R2 servers using the full install package:

  • dotNetFx40_Full_x86_x64.exe /q

If you've not already stumbled across these, you might find them useful:

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.