Dota 2 v580 Full +Multilanguage +AutoUpdate

Windows 10 Download .Net Framework 3.5 Pupup Error Solution

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

 

This problem occurs when you try to install the Microsoft .NET Framework 3.5 on a computer that is running Windows 8.1, Windows Server 2012 R2, Windows 8 or Windows Server 2012.

Resolutions for error code 0x800F0906

This error code occurs because the computer cannot download the required files from Windows Update.

Method 1: Check your internet connection

This behavior can be caused by network, proxy, or firewall configurations or by network, proxy, or firewall failures. To resolve this problem, try to connect to the Microsoft Update website.

If you cannot access this website, check your Internet connection, or contact the network administrator to determine whether there is a configuration that blocks access to the website.

Method 2: Configure the Group Policy setting

This behavior can also be caused by a system administrator who configures the computer to use Windows Server Update Services (WSUS) instead of the Microsoft Windows Update server for servicing. In this case, contact your system administrator and request that they enable the Specify settings for optional component installation and component repair Group Policy setting and configure the Alternate source file path value or select the Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS) option.

To configure the Group Policy setting, follow these steps:

1. Start the Local Group Policy Editor or Group Policy Management Console.
   
   Windows 8 and Windows Server 2012: Point to the upper-right corner of the screen, click Search, type group policy, click Settings, and then click Edit group policy.
   
   
   Windows 8.1 and Windows Server 2012 R2: Point to the upper-right corner of the screen, click Search, type group policy, and then click Edit group policy.
   
2. Expand Computer Configuration, expand Administrative Templates, and then select System. The screen shot for this step is listed below.
   
3. Open the Specify settings for optional component installation and component repair Group Policy setting, and then select Enabled. The screen shot for this step is listed below.
   
4. If you want to specify an alternative source file, in the Alternate source file path box, specify a fully qualified path of a shared folder that contains the contents of the \sources\sxs folder from the installation media.
   
   Example of a shared folder path: \\server_name\share\Win8sxs
   Or, specify a WIM file. To specify a WIM file as an alternative source file location, add the prefix WIM: to the path, and then add the index of the image that you want to use in the WIM file as a suffix.
   
   Example of a WIM file path: WIM:\\server_name\share\install.wim:3Note In this example, 3 represents the index of the image in which the feature files are found.
5. If it is applicable to do this, select the Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS) check box.
6. Tap or click OK.
7. At an elevated command prompt, type the following command, and then press Enter to apply the policy immediately:
   gpupdate /force

Method 3: Use Windows installation media

You can use the Windows installation media as the file source when you enable the .NET Framework 3.5 feature. To do this, follow these steps:

1. Insert the Windows installation media.
2. 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 for the DVD drive or for the Windows 8 installation media. For example, you run the following command:
   Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess

Method 4: Alternative steps for Windows Server 2012 and for Windows Server 2012 R2

In Windows Server 2012 and Windows Server 2012 R2, you can also specify an alternative source by using Windows PowerShell cmdlts or by using the Add Roles and Features Wizard.

To use Windows PowerShell, follow these steps:

1. Insert the Windows installation media.
2. In an elevated Windows PowerShell command window, run the following command:
   Install-WindowsFeature –name NET-Framework-Core –source <drive>:\sources\sxs
   Note In this command, <drive> is a placeholder for the drive letter for the DVD drive or for the Windows installation media. For example, you run the following command:
   Install-WindowsFeature –name NET-Framework-Core –source D:\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.
   
   
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.
   
   
6. Click OK.
7. Click Install to finish the wizard.

Resolution for error code 0x800F081F

This error code can occur when an alternative installation source is specified and one of the following conditions is true:

• The location that is specified by the path does not contain the files that are required to install the feature.
• The user who tries to install the feature does not have at least READ access to the location and to the files.
• The set of installation files is corrupted, incomplete, or invalid for the version of Windows that you are running.

To resolve this problem, make sure that the full path of the source is correct (x:\sources\sxs) and that you have at least Read access to the location. To do this, try to access the source directly from the affected computer. Verify that the installation source contains a valid and complete set of files. If the problem persists, try to use a different installation source.

Resolution for error code 0x800F0907

This error code occurs if an alternative installation source is not specified or is invalid and if the Specify settings for optional component installation and component repair Group Policy setting is configured to "Never attempt to download payload from Windows Update."

To resolve this problem, review the policy setting to determine whether it is appropriate for your environment. If you do not want to download feature payloads from Windows Update, consider configuring the "Alternate source file path" value in the Group policy setting.

Note You must be a member of the Administrators group to change Group Policy settings on the local computer. If the Group Policy settings for the computer that you want to manage are controlled at the domain level, contact your system administrator.

To do this, follow these steps:

1. Start Local Group Policy Editor or Group Policy Management Console as applicable in your environment.
2. Expand Computer Configuration, expand Administrative Templates, and then select System.
3. Open the Specify settings for optional component installation and component repair Group Policy setting, and then select Enabled.
4. Determine whether the Never attempt to download payload from Windows Update Group Policy setting is enabled, and then determine the desired setting for your environment.
5. If you want to specify an alternate source file, in the Alternate source file path box, specify a fully qualified path of a shared folder that contains the contents of the \sources\sxs folder from the installation media. Or, specify a WIM file. To specify a WIM file as an alternative source file location, add the prefix WIM: to the path, and then add the index of the image that you want to use in the WIM file as a suffix. The following are examples of values that you can specify:
   • Path of a shared folder: \\server_name\share\Win8sxs
   • Path of a WIM file, in which 3 represents the index of the image in which the feature files are found: WIM: \\server_name\share\install.wim:3
6. If you want, select the Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS) check box.
7. Tap or click OK.
8. At an elevated command prompt, type the following command, and then press Enter to apply the policy immediately:
   gpupdate /force

More information

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 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.

Error messages that are associated with these error codes

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

References

For more information about how to plan for the deployment of the Net Framework 3.5 in your environment, check out the Microsoft .NET Framework 3.5 Deployment Considerations white paper.