Net framework ошибка 0x800f0906 - Не ошибается лишь тот, кто ничего не делает!

title	description	ms.date	author	ms.author	manager	audience	ms.topic	ms.prod	localization_priority	ms.reviewer	ms.custom	ms.technology	adobe-target
.NET Framework 3.5 installation errors	This article describes a problem where you receive an 0x800F0906, 0x800F081F, or 0x800F0907 error code when you try to install the .NET Framework 3.5 in Windows.	12/16/2021	Deland-Han	delhan	dcscontentpm	itpro	troubleshooting	windows-client	medium	kaushika	sap:.net-framework-installation, csstroubleshoot	windows-client-application-compatibility	true

.NET Framework 3.5 installation errors: 0x800F0906, 0x800F081F, 0x800F0907, 0x800F0922

This article helps fix Microsoft .NET Framework 3.5 installation errors.

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

[!NOTE]
Installation of the .NET Framework may throw errors that are not listed in this article, but you might be able to try the following steps to fix those errors as well.
Microsoft is releasing Out-of-band (OOB) updates for .NET Framework. .NET Framework Out-of-band update to address issues after installing the January 11, 2022 Windows update

Resolutions for Windows Server

You may receive the following errors when you install the .NET Framework 3.5 in Windows Server:

Error code 0x800F0906
Error code 0x800F081F
Error code 0x800F0907

Error code 0x800F0906

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

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

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 fix 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 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:

Start the Local Group Policy Editor or Group Policy Management Console.

Point to the upper-right corner of the screen, click Search, type group policy, and then click Edit group policy.
Expand Computer Configuration, expand Administrative Templates, and then select System. The screenshot for this step is listed below.

:::image type=»content» source=»media/dotnet-framework-35-installation-error/system-option.svg» alt-text=»Screenshot of the System group policy setting window.» border=»false»:::
Open the Specify settings for optional component installation and component repair Group Policy setting, and then select Enabled. The screenshot for this step is listed below.

:::image type=»content» source=»media/dotnet-framework-35-installation-error/enabled-option.svg» alt-text=»Screenshot of the Enabled option of the Specify settings for optional component installation and component repair item.» border=»false»:::
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 sourcessxs folder from the installation media.

Example of a shared folder path: \server_nameshareWin8sxs

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_nameshareinstall.wim:3

[!NOTE]
In this example, 3 represents the index of the image in which the feature files are found.
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.
Tap or click OK.
At an elevated command prompt, type gpupdate /force, and then press Enter to apply the policy immediately.

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:

Insert the Windows installation media.
At an elevated command prompt, run the following command:
```
Dism /online /enable-feature /featurename:NetFx3 /All /Source:<drive>:sourcessxs /LimitAccess
```
In this command, <drive> is a placeholder for the drive letter for the DVD drive. For example, you run the following command:
```
Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:sourcessxs /LimitAccess
```

Method 4: Alternative steps for Windows Server

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

To use Windows PowerShell, follow these steps:

Insert the Windows installation media.
In an elevated Windows PowerShell command window, run the following command:
```
Install-WindowsFeature name NET-Framework-Core source <drive>:sourcessxs
```
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:sourcessxs
```

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

Insert the Windows installation media.
Start the Add Roles and Features Wizard.
On the Select features page, select the .NET Framework 3.5 Features check box, and then click Next.
On the Confirm installation selections page, click the Specify an alternate source path link. The screenshot for this step is listed below.

:::image type=»content» source=»media/dotnet-framework-35-installation-error/specify-alternate-source-path.svg» alt-text=»Screenshot of the Specify an alternate source path link on the Conform installation selections page.» border=»false»:::
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 screenshot for this step is listed below.

:::image type=»content» source=»media/dotnet-framework-35-installation-error/path-of-sxs-folder.svg» alt-text=»Screenshot of the Specify Alternate Source Path page.» border=»false»:::
Click OK.
Click Install to finish the wizard.

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 fix this problem, make sure that the full path of the source is correct (x:sourcessxs) 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.

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 fix 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:

Start Local Group Policy Editor or Group Policy Management Console as applicable in your environment.
Expand Computer Configuration, expand Administrative Templates, and then select System.
Open the Specify settings for optional component installation and component repair Group Policy setting, and then select Enabled.
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.
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 sourcessxs 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_nameshareWin8sxs
- Path of a WIM file, in which 3 represents the index of the image in which the feature files are found:
  WIM:\server_nameshareinstall.wim:3
If you want, select the Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS) check box.
Tap or click OK.
At an elevated command prompt, type the gpupdate /force, and then press Enter to apply the policy immediately.

Resolution for Windows 10

Error code 0x800F0906, 0x800F081F, or 0x800F0907

To fix the error codes for Windows 10, follow these steps:
1. Download the Windows Media Creation tool, and create an ISO image locally, or create an image for the version of Windows that you have installed.
2. Configure the Group Policy as in Method 2, but also follow these steps:
  1. Mount the ISO image that’s created in step 1.
  2. Point the Alternate source file path to the ISO sourcessxs folder from the ISO.
  3. Run the gpupdate /force command.
  4. Add the .NET Framework feature.
Error code 0x800F0922

The following error message occurs when you do Windows 10 upgrade:

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

[!NOTE]
This error code is not specific to .NET Framework.

To fix this issue, follow these steps:
1. Open the .NET Framework installation files folder.
2. Open Sources folder.
3. Right-click the SXS folder, and then click Properties.
4. Click Security and make sure that there is a check mark next to Read & Execute. If the check mark isn’t there, click the Edit button and turn it on.
5. Press Windows Key + X keyboard shortcut.
6. Click Command Prompt (Admin).
7. In the Command Prompt window, type 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 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 and Windows Server 2012 R2, 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

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

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

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

The .NET Framework 3.5 is available for customers with Volume Licensing or MSDN Subscription, as Feature on-Demand Media is available.

Error codes are not listed when you install .NET Framework 3.5

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

Windows help
Net Framework 3.5 and 4.5 error 0x80070002
Install the .NET Framework 3.5 in Windows 10
Microsoft .NET Framework 3.5 Deployment Considerations

Источник

After trying to install .net 3.5 via the program and features (see below). I was getting unable to install error 800F0906

I am using windows 8.1.

asked Aug 7, 2014 at 17:03

I inserted windows 8.1 dvd and mounted to d drive then executed from powershell.

Open admin command prompt
Type powershell
From ps prompt type

Enable-WindowsOptionalFeature -Online -FeatureName ‘NetFx3’ -Source ‘d:sourcessxs’

It did take 5 minutes to run.

answered Aug 7, 2014 at 17:03

DavidDavid

3,0184 gold badges45 silver badges77 bronze badges

You probably have a GPO that blocks updates directly from Microsoft. Did not check the WSUS server to see if the required packages were present. Simply made these registry changes and the PC was able to pull down the updates. Note, no need to undo these as the GPO will do it for you.

----- Below this line is the actual content to create your own .REG file -----

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesWindowsUpdate]
"DisableWindowsUpdateAccess"=dword:00000000
"DisableWindowsUpdateAccessMode"=dword:00000000

Machavity♦

30.7k27 gold badges91 silver badges100 bronze badges

answered Aug 10, 2015 at 16:03

Found link that identifies two Windows Updates as the problem if DISM
and the offline installer do not work. Uninstall KB2966826 and
KB2966828, then try installing 3.5 from programs and features. It
worked for me.

By Chris Wardario

answered Sep 8, 2014 at 16:30

UmairUmair

4,7143 gold badges27 silver badges46 bronze badges

I had to log in as a local admin account, rather than runas to get it to download the missing binaries.

answered Mar 16, 2015 at 22:28

I ran into this issue today and it ended up being a problem with the WSUS server not having the necessary updates synced. To test this, I removed the PC from the policy that points the the WSUS server and adding the feature through the control panel is now working. I don’t know if this will apply to everyone but I figured I would add my two cents.

answered Jun 3, 2015 at 14:12

I was facing same issue.

Cause:
under gpeditor, MS update service location was set to some local WSUS.

Solution:
copy that URL and set MS update service location disable or Not configured from gpeditor.
now try steps from feature on/off Windows to install .Net Framework 3.5.
after successfully completion revert WSUS update service URL.

[for MS update service location:
under Run=> gpedit.msc
navigate to Comp Conf->Admin Templates->Win Components->Win Update->»Specify internet MS update service location»
]

if MS update service location is not configured then check internet connection otherwise it’s some other related issue.

Vini.g.fer

11.6k16 gold badges60 silver badges90 bronze badges

answered Jan 21, 2016 at 13:53

answered Apr 6, 2019 at 13:53

check your windows firewall. That must be turned on.

answered Aug 30, 2016 at 8:53

Источник

Question

Issue: How to fix .NET Framework Installation error 0x800F0906 in Windows?

Hello. I tried to install the .NET Framework but I received the 0x800F0906 error. How do I fix this?

Solved Answer

The .NET Framework^[1] is a Microsoft software development platform that is required to run many applications and services on Windows operating systems. It offers a comprehensive and consistent programming model for developing applications with visually stunning user interfaces, seamless and secure communication, and the ability to model a variety of business processes. The .NET Framework is a critical component for the proper operation of many software applications, so it must be installed.

The error code 0x800F0906 is a common problem that can arise during the installation of the .NET Framework on Windows-based computers. This error code is typically generated when the system is unable to download and install the required files for the .NET Framework for a variety of reasons, including a poor internet connection, corrupt system files, or conflicts with other software installed on the system.

This issue can affect users in several ways, including:

Preventing the installation of certain software applications that require the .NET Framework to run.
Causing existing .NET Framework-dependent applications to stop working.
Interrupting the installation process of other software applications that require the .NET Framework to be installed.

To resolve the .NET Framework installation error 0x800F0906, you can follow the step-by-step instructions below or you can try an automatic maintenance tool like RestoroMac Washing Machine X9. It can fix most system errors, BSODs,^[2] corrupted files, and registry^[3] issues.