.Internet Framework 3.five installation errors: 0x800F0906, 0x800F081F, 0x800F0907, 0x800F0922

  • Article
  • 10 minutes to read

This article helps fix Microsoft .Internet Framework three.5 installation errors.

Applies to: Windows 10 - all editions, Windows Server 2019, Windows Server 2012 R2
Original KB number: 2734782

Resolutions for Windows Server

You may receive the following errors when you install the .Cyberspace Framework 3.five in Windows Server:

  • Mistake lawmaking 0x800F0906
  • Error lawmaking 0x800F081F
  • Error code 0x800F0907

Error lawmaking 0x800F0906

This error lawmaking occurs because the reckoner cannot download the required files from Windows Update.

To resolve this effect, use one of the following methods:

Method one: Check your internet connectedness

This beliefs tin exist caused by network, proxy, or firewall configurations or past network, proxy, or firewall failures. To fix this trouble, effort to connect to the Microsoft Update website.

If you cannot access this website, cheque 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 Grouping Policy setting

This behavior can too be caused by a system administrator who configures the computer to use Windows Server Update Services (WSUS) instead of the Windows Update server for servicing. In this example, 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 direct to download repair content instead of Windows Server Update Services (WSUS) option.

To configure the Group Policy setting, follow these steps:

  1. Beginning the Local Group Policy Editor or Group Policy Direction Console.

    Point to the upper-correct corner of the screen, click Search, type grouping policy, and and then click Edit grouping policy.

  2. Expand Figurer Configuration, expand Administrative Templates, so select System. The screenshot for this step is listed below.

    Screenshot of the System group policy setting window.

  3. Open the Specify settings for optional component installation and component repair Grouping Policy setting, and and so select Enabled. The screenshot for this pace is listed below.

    Screenshot of the Enabled option of the Specify settings for optional component installation and component repair item.

  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 binder from the installation media.

    Example of a shared folder path: \\server_name\share\Win8sxs

    Or, specify a WIM file. To specify a WIM file equally an alternative source file location, add the prefix WIM: to the path, and then add the index of the image that you desire to use in the WIM file equally a suffix.

    Case of a WIM file path: WIM:\\server_name\share\install.wim:3

    Note

    In this instance, three represents the index of the epitome in which the characteristic files are plant.

  5. If information technology is applicable to practice 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 control prompt, type gpupdate /forcefulness, and so printing Enter to apply the policy immediately.

Method 3: Utilise Windows installation media

You can use the Windows installation media every bit the file source when yous enable the .Net Framework 3.5 characteristic. 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:<bulldoze>:\sources\sxs /LimitAccess

    In this command, <drive> is a placeholder for the drive letter for the DVD drive. For example, you lot run the following command:

                      Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess

Method four: Alternative steps for Windows Server

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

To employ Windows PowerShell, follow these steps:

  1. Insert the Windows installation media.

  2. In an elevated Windows PowerShell command window, run the post-obit command:

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

    In this command, <drive> is a placeholder for the bulldoze letter of the alphabet for the DVD drive or for the Windows installation media. For example, yous run the following control:

                      Install-WindowsFeature proper noun Internet-Framework-Cadre source D:\sources\sxs

To use the Add Roles and Features Magician, 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 .Cyberspace Framework 3.5 Features check box, and then click Adjacent.

  4. On the Confirm installation selections page, click the Specify an alternating source path link. The screenshot for this step is listed below.

    Screenshot of the Specify an alternate source path link on the Conform installation selections page.

  5. On the Specify Alternating Source Path folio, type the path of the SxS binder as a local path or every bit a network share path. The screenshot for this step is listed beneath.

    Screenshot of the Specify Alternate Source Path page.

  6. Click OK.

  7. Click Install to terminate the wizard.

Mistake lawmaking 0x800F081F

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

  • The location that is specified by the path does non comprise the files that are required to install the feature.
  • The user who tries to install the feature does not accept at least READ access to the location and to the files.
  • The set up of installation files is corrupted, incomplete, or invalid for the version of Windows that y'all are running.

To ready this problem, make sure that the full path of the source is correct (ten:\sources\sxs) and that you lot accept at to the lowest degree Read access to the location. To practice this, endeavor to access the source directly from the affected computer. Verify that the installation source contains a valid and complete set of files. If the trouble persists, attempt to utilise a different installation source.

Mistake lawmaking 0x800F0907

This fault lawmaking 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 fix this trouble, review the policy setting to determine whether it is advisable for your environment. If you practise 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 Grouping Policy settings for the computer that you desire 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 Direction Panel every bit applicable in your environs.

  2. Expand Computer Configuration, expand Administrative Templates, and then select Arrangement.

  3. Open the Specify settings for optional component installation and component repair Grouping Policy setting, and and then select Enabled.

  4. Make up one's mind whether the Never effort to download payload from Windows Update Group Policy setting is enabled, and then determine the desired setting for your environment.

  5. If you desire to specify an alternate source file, in the Alternating source file path box, specify a fully qualified path of a shared folder that contains the contents of the \sources\sxs binder from the installation media. Or, specify a WIM file. To specify a WIM file as an alternative source file location, add together the prefix WIM: to the path, and then add the index of the image that you want to use in the WIM file equally 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 three represents the index of the image in which the characteristic files are found:
      WIM:\\server_name\share\install.wim:three

  6. If you desire, 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, blazon the gpupdate /force, and so press Enter to apply the policy immediately.

Resolution for Windows 10

  • Error lawmaking 0x800F0906, 0x800F081F, or 0x800F0907

    To fix the mistake codes for Windows x, follow these steps:

    1. Download the Windows Media Creation tool, and create an ISO prototype locally, or create an image for the version of Windows that you have installed.

    2. Configure the Group Policy as in Method 2, simply besides follow these steps:

      1. Mountain the ISO epitome that's created in footstep 1.
      2. Point the Alternating source file path to the ISO sources\sxs folder from the ISO.
      3. Run the gpupdate /strength command.
      4. Add the .Cyberspace Framework feature.

  • Error code 0x800F0922

    The following fault message occurs when you do Windows ten upgrade:

    0x800F0922 CBS_E_INSTALLERS_FAILED: Processing advanced installers and generic commands failed.

    Note

    This error code is not specific to .Cyberspace Framework.

    To fix this consequence, follow these steps:

    1. Open the .Cyberspace Framework installation files folder.

    2. Open Sources binder.

    3. Right-click the SXS binder, and then click Backdrop.

    4. Click Security and make sure that at that place is a check mark next to Read & Execute. If the bank check mark isn't there, click the Edit button and turn it on.

    5. Printing Windows Central + X keyboard shortcut.

    6. Click Command Prompt (Admin).

    7. In the Command Prompt window, blazon the following command and press Enter:

                            dism /online /enable-feature /featurename:netfx3 /all /source:c:\sxs /limitaccess

    8. In the Command Prompt window, type the following command and press Enter:

                            dism /online /Cleanup-Image /RestoreHealth

More information

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

In Windows 10 and Windows Server 2012 R2, the .NET Framework 3.5 is a Feature on Demand. The metadata for Features on Need is included. However, the binaries and other files associated with the characteristic are non included. When you enable a characteristic, Windows tries to contact Windows Update to download the missing data to install the feature. The network configuration and how computers are configured to install updates in the environment can affect this procedure. Therefore, yous may meet errors when you lot first install these features.

Error messages that are associated with these fault codes

Error code Error letters
0x800F0906 The source files could not be downloaded.
Use the source choice to specify the location of the files that are required to restore the feature. For more than data on specifying a source location, meet http://become.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 Net to download necessary files. Make sure that you're connected to the Net, and click Retry to try once again.

Installation of 1 or more roles, role services, or features failed.
The source files could non be constitute. Try installing the roles, office services, or features again in a new Add Roles and Features Sorcerer 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 past the calculator account of the destination server.

0x800F0906 - CBS_E_DOWNLOAD_FAILURE

Error code: 0x800F0906

Error: 0x800f0906
0x800F081F The source files could not be found.
Apply the Source option to specify the location of the files that are required to restore the characteristic. For more information on specifying a source location, see http://get.microsoft.com/fwlink/?LinkId=243077.
The DISM log file tin be found at C:\Windows\Logs\DISM\dism.log

0x800F081F - CBS_E_SOURCE_MISSING

Error code: 0x800F081F

Error: 0x800F081F
0x800F0907 DISM failed. No functioning was performed.
For more information, review the log file.
The DISM log file tin can be constitute at C:\Windows\Logs\DISM\dism.log

Considering 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 ambassador for more information.

0x800F0907 - CBS_E_GROUPPOLICY_DISALLOWED

Error code: 0x800F0907

Fault: 0x800F0907

Download the .NET Framework 3.5 outside of the Windows Update requirement

The .Net Framework 3.v is bachelor for customers with Volume Licensing or MSDN Subscription, equally Feature on-Need Media is available.

Fault codes are non listed when yous install .NET Framework 3.v

When you install .Internet Framework 3.5, yous may encounter other error codes that are not listed in this article, for more information, go to the following articles:

  • Windows assist

  • Cyberspace Framework 3.5 and 4.v error 0x80070002

  • Install the .Cyberspace Framework three.v in Windows 10

  • Microsoft .NET Framework iii.v Deployment Considerations