Install-WindowsFeature-Name NET-Framework-Core source files could not be downloaded

For more information on specifying a source location, see Configure a Windows Repair Source. To do it, follow these steps:.

For example, if you have Windows Server R2 Datacenter installed, the required index number is 4. If you have Windows Server R2 Standard installed, the required index number is 2. For example: If your media is on drive F, and you're installing the full version of Datacenter, enter the following command:.

The Windows Server R2 Volume Licensing media was designed to require access to Windows Update to add optional components or features that aren't included in the side-by-side repository. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows PowerShell. NET Framework 3. Here was the latest powershell error: Install-WindowsFeature : The server could not update the provided feature files in the time allowed.

Thanks All! Best Answer. Thanks Mike View this "Best Answer" in the replies below ». Mike This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. TroyKerns wrote: Have not been able to test.

Try copying the image to the server you're having problems with and then running the install entirely locally. Once it's installed you can delete the local image you just created via the copy. Windows Server expert. Either install update or uninstall and Server Manager running on Windows Server or Windows 8 cannot be used to install roles, role services, and features on servers that are running Windows Server R2.

You must be logged on to a server as an administrator to install or uninstall roles, role services, and features. If you are logged on to the local computer with an account that does not have administrator rights on your target server, right-click the target server in the Servers tile, and then click Manage As to provide an account that has administrator rights. The server on which you want to mount an offline VHD must be added to Server Manager, and you must have Administrator rights on that server.

For more information about what roles, role services, and features are, see Roles, Role Services, and Features. Install roles, role services, and features by using the Add Roles and Features Wizard. Remove roles, role services, and features by using the Remove Roles and Features Wizard. Install roles and features on multiple servers by running a Windows PowerShell script. In a single session in the Add Roles and Features Wizard, you can install roles, role services, and features on the local server, a remote server that has been added to Server Manager, or an offline VHD.

If Server Manager is already open, go on to the next step. If Server Manager is not already open, open it by doing one of the following.

On the Before you begin page, verify that your destination server and network environment are prepared for the role and feature you want to install. Click Next. On the Select installation type page, select Role-based or feature-based installation to install all parts of roles or features on a single server, or Remote Desktop Services installation to install either a virtual machine-based desktop infrastructure or a session-based desktop infrastructure for Remote Desktop Services.

The Remote Desktop Services installation option distributes logical parts of the Remote Desktop Services role across different servers as needed by administrators. On the Select destination server page, select a server from the server pool, or select an offline VHD. For information about how to add servers to your server pool, see Add Servers to Server Manager. After you have selected the destination server, click Next.

See the note at the start of Install roles, role services, and features by using the Add Roles and Features Wizard. VHDs cannot have more than one system volume or partition. The network shared folder in which the VHD file is stored must grant the following access rights to the computer or local system account of server that you have selected to mount the VHD.

User-only account access is not sufficient. The share can grant Read and Write permissions to the Everyone group to allow access to the VHD, but for security reasons, this is not recommended. Full Control access on the Security tab , file or folder Properties dialog box.

Select roles, select role services for the role if applicable, and then click Next to select features. As you proceed, the Add Roles and Features Wizard automatically informs you if conflicts were found on the destination server that can prevent selected roles or features from installation or normal operation.

You are also prompted to add any roles, role services, or features that are required by the roles or features that you have selected. Additionally, if you plan to manage the role remotely, either from another server, or from a Windows client-based computer that is running Remote Server Administration Tools, you can opt not to install management tools and snap-ins for roles on the destination server.

By default, in the Add Roles and Features Wizard, management tools are selected for installation. On the Confirm installation selections page, review your role, feature, and server selections. If you are ready to install, click Install. You can also export your selections to an XML-based configuration file that you can use for unattended installations with Windows PowerShell. To export the configuration you specified in this Add Roles and Features Wizard session, click Export configuration settings , and then save the XML file to a convenient location.

The Specify an alternate source path command on the Confirm installation selections page lets you specify an alternate source path for the files that are required to install roles and features on the selected server. In Windows Server , Features on Demand lets you reduce the amount of disk space used by the operating system, by removing role and feature files from servers that are exclusively managed remotely.