Windows Server 2012 R2 .NET 3.5 Install

dotNet


If you can’t figure out or remember how to install the .NET Framework 3.5 Features on a Windows Server 2012 R2 server without a DVD or USB drive, you’ve come to the right place.

The Caged Rat is back with a simple but effective way to install .NET Framework 3.5 (which includes .NET 2.0 and 3.0) on a Windows Server 2012 R2 physical or virtual machine without a DVD or USB drive.


why are you getting this error?

 

Win 2K12 R2 .NET 3.5 Install Error

Related .NET Framework 3.5 installation error codes:  0x800F0906, 0x800F081F, 0x800F0907

These errors may occur when you use an installation wizard, the Deployment Image Servicing and Management (DISM) tool, or Windows PowerShell commands to enable the .NET Framework 3.5.

In Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2, and Windows Server 2012, the .Net Framework 3.5 is a Feature on Demand. The metadata for Features on Demand is included.  However, the binaries and other files associated with the feature are not included.  When you enable a feature, Windows tries to contact Windows Update to download the missing information to install the feature.  The network configuration and how computers are configured to install updates in the environment can affect this process.  Therefore, you may encounter errors when you first install these features.


Install .net framework 3.5 features


Step 1:  Setup Install Source Directory

Option 1:  On a different Windows system with a DVD drive, that is reachable on your network by the Windows Server 2012 R2 server that requires the .NET Framework 3.5 Features installation, share the DVD drive.  Insert the Windows Windows Server 2012 R2 installation media into the shared DVD drive.

Option 2:  On a different Windows system with a DVD drive, copy the Windows Server 2012 R2 installation media disk files to a network share that is reachable by the Windows Server 2012 R2 server that requires the .NET Framework 3.5 Features installation.


STEP 2:  Map Network Drive…

  1. Open a Windows Command Processor (“Windows Shell”) with “Run as administrator” (a.k.a. elevated command prompt).
  2. Map a drive letter (e.g., “z”) to the shared DVD drive of the remote Windows system (Option 1 above) or map a drive letter to the network share directory (Option 2 above) that contains the Windows Server 2012 R2 OS installer disk files.
net use <drive letter>: \\computername\sharename /user:domain\username password
net use <drive letter>: \\IP address\sharename /user:domain\username *

For example, net use z: \\server1\d-drive /user:contoso\jdoe *

NOTE:  The asterisk (*) forces a prompt for the user password.  The password is hidden from being displayed in the command shell.

STEP 3:  Install .NET 3.5

At an elevated command prompt, run the following command:

DISM /online /enable-feature /featurename:NetFx3 /All /Source:<drive>:\sources\sxs /LimitAccess

NOTE:  In this command, <drive> is a placeholder for the drive letter of the mapped network drive which is the source for the Windows 2012 R2 installation media.

DISM /online /enable-feature /featurename:NetFx3 /All /Source:Z:\sources\sxs /LimitAccess

To use Windows PowerShell, follow these steps:

In an elevated Windows PowerShell command window, run the following command:

Install-WindowsFeature –name NET-Framework-Core –source <drive>:\sources\sxs

To use the Add Roles and Features Wizard, follow these steps:

  1. Insert the Windows installation media.
  2. Start the Add Roles and Features Wizard.
  3. On the Select features page, select the .Net Framework 3.5 Features check box, and then click Next.
  4. On the Confirm installation selections page, click the Specify an alternate source path link. The screen shot for this step is listed below.image
  5. On the Specify Alternate Source Path page, type the path of the SxS folder as a local path or as a network share path. The screen shot for this step is listed below.imageimage
  6. Click OK.
  7. Click Install to finish the wizard.

Error code Error messages
0x800F0906
The source files could not be downloaded.
Use the “source” option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at
C:\Windows\Logs\DISM\dism.log
Windows couldn’t complete the requested changes.
Windows couldn’t connect to the Internet to download necessary files. Make sure that you’re connected to the Internet, and click “Retry” to try again.
Installation of one or more roles, role services, or features failed.
The source files could not be found. Try installing the roles, role services, or features again in a new Add Roles and Features Wizard session, and on the Confirmation page of the wizard, click “Specify an alternate source path” to specify a valid location of the source files that are required for the installation. The location must be accessible by the computer account of the destination server.
0x800F0906 – CBS_E_DOWNLOAD_FAILURE
Error code: 0x800F0906
Error: 0x800f0906
0x800F081F
The source files could not be found.
Use the “Source” option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at
C:\Windows\Logs\DISM\dism.log
0x800F081F – CBS_E_SOURCE_MISSING
Error code: 0x800F081F
Error: 0x800F081F
0x800F0907
DISM failed. No operation was performed.
For more information, review the log file.
The DISM log file can be found at
C:\Windows\Logs\DISM\dism.log
Because of network policy settings, Windows couldn’t connect to the Internet to download files that are required to complete the requested changes. Contact your network administrator for more information.
0x800F0907 – CBS_E_GROUPPOLICY_DISALLOWED
Error code: 0x800F0907
Error: 0x800F0907
Facebook Comments