Net framework код ошибки 0x800f0954

Рассказываем, из-за чего возникает и как исправить ошибку 0x800f0954 в Windows 10.

Что это за ошибка?

Этот сбой связан с программным обеспечением .NET Framework. Ошибка появляется во время установки и не дает ее завершить, жалуясь на необходимость подключиться к интернету (даже если он и так есть).

А .NET Framework — это очень нужный инструмент для разработчиков, на базе которого построены многие приложения для Windows. Эти же приложения полагаются на Фреймворк при запуске. Проще говоря, обойтись без него никак нельзя. Поэтому ошибку 0x800f0954 придется как-то исправлять. Иначе есть шанс лишиться кучи программ и видеоигр.

Далее рассмотрим методы решения проблемы, которые уже доказали свою эффективность.

Меняем параметры реестра

Иногда ошибка возникает из-за проблем при подключении к внешнему серверу обновлений. В этом случае можно попытаться установить .NET Framework, игнорируя хранилища Microsoft Update.

Для этого:

Кликаем по иконке в виде лупы в левом нижнем углу.

Жмем сюда

В открывшееся поисковое поле вводим название программы regedit и запускаем ее от имени администратора.

Обязательно выбираем этот пункт

Когда появится запрос от системы безопасности, нажимаем «Да».

Возможно, для внесения изменений понадобится пароль администратора

Откроется реестр. Переходим в нем в папку Windows по пути HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows.
Кликаем по этой папке правой кнопкой мыши.

Создаем подпапку в этой директории

В появившемся контекстном меню наводим курсор на пункт «Создать», а потом выбираем опцию «Раздел».
Даем ему название WindowsUpdate.

Сначала нажимаем вот сюда

Потом кликаем правой кнопкой мыши по папке WindowsUpdate и повторяем то же самое. То есть создаем еще один раздел. На этот раз с названием AU.

Внимательно указывайте названия папок и файлов

Открываем вновь созданный раздел AU. Получится вот такой путь HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU.
Кликаем правой кнопкой мыши по пустому пространству в правой части редактора реестра.
В появившемся контекстном меню выбираем опцию «Создать параметр DWORD (32 бита)».

Создаем новую опцию

Даем параметру название UseWUServer.
Кликаем по нему дважды.

Скорее всего, у вас тут будет всего лишь один параметр

Появится окошка с настройками. Заменяем «Значение» на 0.

Остальные значения оставляем прежними

После этого перезагружаем компьютер и заново пытаемся установить .NET Framework. Ошибка должна исчезнуть.

Удаляем файлы CBS

Второй способ — удаление временных файлов CBS. Это журнал данных Component-Based Servicing. Иногда их наличие мешает установке тех или иных системных компонентов и сторонних приложений.

Чтобы их удалить:

Открываем встроенный файловый менеджер Windows.
Переходим в папку _Локальный диск (С:)WindowsLogsCBS_
Удаляем все содержимое. Просто выделяем и жмем на клавишу Delete.
А потом очищаем корзину.

У меня тут всего один файл, но у вас их может быть с десяток разных. Удаляем все сразу. Они не нужны

После удаления журналов пробуем установить .NET Framework через систему выгрузки образов Microsoft. Для этого:

Открываем поисковик Windows, кликнув по соответствующей иконке.
Ищем там программу cmd.exe и запускаем от имени администратора.

Командную строку тоже надо включать от имени администратора. И тоже может понадобиться пароль

Затем вводим команду _Dism.exe /online /enable-feature /featurename:NetFX3 /source:C:_
Дождавшись окончания работы программы, перезапускаем компьютер.
А потом еще раз пробуем установить .NET Framework. В этот раз должно получиться.

Устанавливаем .NET Framework через командную строку

Еще один способ обойти ошибку 0x800f0954 — установка .NET Framework прямо с образа системы через командную строку.

Чтобы это сделать:

Создаем флэшку с установочными файлами Windows (перед этим, вероятно, придется скачать образ Windows 10 с официального сайта Microsoft).
Вставляем ее в компьютер и запоминаем букву диска, под которой она отображается в системе.
Открываем поисковик Windows.
Ищем там командную строку и запускаем ее от имени администратора.
Сразу же вводим туда команду Add-WindowsCapability -Online -Name NetFx3~~~~ -Source буква диска, под которым записана флэшка с Windows:sourcessxs

В моем случае выбран диск с буквой F. Вот как он вписывается в команду

Дожидаемся, пока завершится процесс загрузки и установки нужных компонентов.
Затем перезагружаем компьютер и заново пробуем установить .NET Framework стандартным способом.

Устанавливаем дополнительные компоненты

Если у вас установлена Windows 10 Pro (или Enterprise), то есть еще один вариант исправления ошибки. Для этого надо поменять параметры групповой политики в системе.

Чтобы это сделать:

Одновременно нажимаем клавиши Win + R.
В окне программы «Выполнить» набираем gpedit.msc и кликаем по кнопке ОК.

Это короткий путь к редактору групповых политик

Откроется редактор групповых политик. Переходим там по пути «Конфигурация компьютера»«Административные шаблоны»«Система».
Затем ищем политику под названием «Укажите параметры для установки необязательных компонентов и восстановления компонентов». Кликаем по ней два раза.
Ставим галочки напротив пункта «Включено» и напротив пункта «Скачайте содержимое для восстановления и дополнительные компоненты непосредственно из центра обновления Windows вместо использования служб Windows Server Update Services (WSUS)»
После этого перезагружаем компьютер и пробуем заново установить .NET Framework.

Загрузка …

Post Views: 3 339

Источник

Remove From My Forums

Вопрос
Title. Downloads for about 2 seconds then fails. Tried the DISM command
```
Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:sourcessxs
```
Get the same error code.

Windows 10 1709
- Изменено
  
  8 декабря 2017 г. 20:16

Ответы

Title. Downloads for about 2 seconds then fails. Tried the DISM command
```
Dism /online /enable-feature /featurename:NetFX3 /All /Source:D:sourcessxs
```
Get the same error code.

Windows 10 1709
Used the powershell command
```
Add-WindowsCapability –Online -Name NetFx3~~~~ –Source D:sourcessxs
```
which worked.
- Помечено в качестве ответа
  CFFraser
  8 декабря 2017 г. 20:37

Источник

When you attempt to install .NET Framework 3.5 or any other optional feature using “Windows Features” (optionalfeatures.exe) dialog or using DISM command-line, error 0x800F0954 may popup.

enable feature .net framework 3.5

After enabling .NET Framework 3.5 and clicking OK, the following error may appear:

Windows couldn’t complete the requested changes.

The changes couldn’t be completed. Please reboot your computer and try again.

Error code: 0x800F0954

The same error may occur when attempting to install additional speech recognition or supplemental fonts using Optional features in the Settings page or using DISM command-line. For instance, you run the following command to install .NET Framework 3.5 from an elevated or administrator Command Prompt.

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All

After pressing ENTER, here is the full error message you might see:

Deployment Image Servicing and Management tool
Version: 10.0.16299.15
Image Version: 10.0.16299.192
Enabling feature(s)
[==========================100.0%==========================]
Error: 0x800f0954
DISM failed. No operation was performed.
For more information, review the log file.
The DISM log file can be found at C:WindowsLogsDISMdism.log

The DISM.log file would show these entries/errors:

xxxx, Info                  DISM   DISM Package Manager: PID=12956 TID=12296 Further logs for online package and feature related operations can be found at %WINDIR%logsCBScbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
xxxx, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0954

And the CBS.log file would have recorded these errors:

xxxx, Info                  CBS    DWLD:Failed to do Windows update search [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS]
xxxx, Info                  CBS    FC:   WindowsUpdateDownloadFromUUP returns. [0x800F0954]

Note that the error 0x800f0954 refers to CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS which indicates that your system might have been configured to use a WSUS server (on your domain network) to get updates instead of connecting to Windows Update servers directly.

If the error 0x800f0954 occurs installing optional Windows features, it may be because the system is unable to access the Windows Update server. This is especially true in case of domain-joined computers which is configured to downloads updates from a WSUS server. It could also be possible that your computer was once a part or a corporate or domain network and the group policy setting is still in place.

Method 1: Bypass WSUS to Install Features/Updates Directly from Windows Update

To fix the problem, temporarily bypass WSUS server using the following registry edit (requires administrator privileges).

Right-click Start, and click Run
Type regedit.exe and click OK

Go to the following registry key:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU

On the right-pane, if the value named UseWUServer exists, set its data to 0
Exit the Registry Editor
Restart Windows.

Note: Please note that some servers will flip the UseWUServer back to 1 on reboot. In that scenario, set it to 0, restart the Windows Update service (without rebooting), and install the required optional feature (Feature on Demand).

Automate the above, using PowerShell (admin)

Here are the PowerShell commands to automate the following steps:

Set “UseWUServer” registry setting to 0
Restart the Windows Update service
Install .NET Framework (“NetFx3”)
Then, flip “UseWUServer” back to 1.

Set-ItemProperty "REGISTRY::HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdateAU" UseWUserver -value 0
Get-Service wuauserv | Restart-Service
Add-WindowsCapability –Online -Name NetFx3~~~~
Set-ItemProperty "REGISTRY::HKLMSoftwarePoliciesMicrosoftWindowsWindowsUpdateAU" UseWUserver -value 1

See if you’re able to install .Net Framework 3.5 or any other optional feature (e.g., Print Management, RSAT, Notepad, etc.) now. In most cases, the above steps should fix the problem.

Method 2: Bypass WSUS for Repair Content/Feature On Demand Downloads

Using this method, you can bypass WSUS server only for downloading repair content and Feature-on-Demand package installation. After you enable the following setting, Windows will use Windows Update (instead of WSUS) to download the FOD packages or the files needed to repair the operating system corruption.

Open the Group Policy Editor (gpedit.msc).

Go to:

Computer Configuration → Policies → Administrative Templates → System

Double-click “Specify settings for optional component installation and component repair”
Set “Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)” to Enabled.

(This policy setting specifies the network locations that will be used for the repair of operating system corruption and for enabling optional features that have had their payload files removed.)

Alternately, use the following registry setting equivalent:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesServicing]
"RepairContentServerSource"=dword:00000002

This fixes the error 0x800f0954 when installing a feature (FOD) using GUI or DISM.

Method 3: Install .NET Framework (or Optional Features) from Windows 10/11 ISO or DVD

If the procedure under Method 1 or 2 did not help, you may use the following DISM command (with the installation source path) to install additional features from the Windows 10/11 ISO or DVD. However, you must make sure that the Windows 10 version on your DVD or ISO corresponds to the version of Windows 10/11 installed on your system.

Here are the steps to install .NET Framework 3.5 from the Windows setup disk or ISO:

Obtain the latest Windows 10 ISO (assuming that your Windows 10/11 system is running the newest build) using the Media Creation Tool.
Download Windows ISO Using Media Creation Tool
Editor’s note: Even better option would be to update your Windows 10 device fully, and then prepare an up-to-date Windows 10 setup disk by slipstreaming. See how to Slipstream Windows (Integrate Updates with Original Setup Disk)
Mount the ISO image by double-clicking on the ISO file.
Note down the drive letter of your DVD or the mounted drive, let’s say H:
Open an elevated Command Prompt (Administrator) window.
Type the following command, and press ENTER
```
dism /online /enable-feature /featurename:NetFX3 /Source:H:sourcessxs /LimitAccess
```

Note: If you need to install the “Windows Communication Foundation (WCF) HTTP Activation” and “Windows Communication Foundation (WCF) Non-HTTP Activation”, make sure you add the /All parameter, as seen in the above screenshot. As said earlier, these two components are usually not required for most users.

Similarly, to install other optional features using DISM, refer blog post Adding features (including .NET 3.5) to Windows 10 – Michael Niehaus’ Windows and Office deployment ramblings as well as Microsoft Docs articles DISM Capabilities Package Servicing Command-Line Options & Available features on demand

Hope this article helped you install .NET Framework 3.5 or any other optional Windows features, without getting the error 0x800F0954.

One small request: If you liked this post, please share this?

One «tiny» share from you would seriously help a lot with the growth of this blog.
Some great suggestions:

Pin it!
Share it to your favorite blog + Facebook, Reddit
Tweet it!

So thank you so much for your support. It won’t take more than 10 seconds of your time. The share buttons are right below.

[Fix] .NET Framework 3.5 Error 0x800f0950 in Windows 10/11

Источник

Some users are getting the Error Code 0x800f0954 when attempting to install .NET Framework 3.5 or a different optional feature in Windows 10. Most users are reporting that this error occurs while they trying to install the package via Windows Features, but others are getting it while using the DISM command-line tool. The error doesn’t seem to be exclusive to a certain Windows version since it’s confirmed to occur on Windows 7, Windows 8.1 and Windows 10.

Error Code 0x800f0954

What is causing the Error Code 0x800f0954?

We looked into this particular issue by trying to replicate the issue on our testing machines and by looking at various user reports that have encountered this exact problem. As it turns out, there are several different potential culprits that might end up triggering this error code:

The computer cannot access the Windows Update server – In some cases, the error message occurs because the system is not able to reach the WU server. This is typical in situations where there’s a whole network of domain-joined computers configured to download updates from a WSUS server. In this case, you can resolve the issue by bypassing the WSUS.
DISM CBS logs are triggering the issue – Sometimes, the CBS logs generated by the DISM utility can point towards a problem that doesn’t actually exist. In this case, you can resolve the issue by deleting the Component Based Servicing logs and re-running the DISM command that was previously failing with this error message.
.NET Framework needs to be installed via Powershell – If you’re trying to install an older .NET Framework package, you might have to do it from a PowerShell window in order to avoid the 0x800f0954 error.
Group policy is preventing the installation – There’s one policy that has the potential of triggering this particular error if it’s disabled from the Local Group Policy Editor. If this scenario is applicable, you can resolve the issue by enabling the ‘Specify settings for optional component installation and component repair’ policy.

If you’re currently searching for a fix for the 0x800f0954 error, this article will provide you with several troubleshooting steps. Down below, you’ll find a collection of methods that other users in a similar situation have successfully used to fix this particular issue.

Keep in mind that the methods below are ordered by efficiency and severity, so we encourage you to follow them in the order that they are presented. Chances are not every potential fix will be applicable to your current situation, so feel free to skip the methods that cannot be followed.

Method 1: Bypassing the WSUS

If you get the 0x800f0954 error while trying to install optional Windows features, it’s probably because your system cannot access the Windows Update server. This seems to have occurred for a lot of users in a similar situation – especially in situations where there’s a whole network of domain-joined computers that are configured to download updates from a WSUS server.

If your situation is similar, it’s possible that the issue occurs because your computer was once a part of a domain network and the group policy setting is still in place. If this scenario is applicable, you can resolve the issue by temporarily bypassing the WSUS server. You can do this easily by performing the following registry edit:

Press Windows key + R to open up a Run dialog box. Then, type “regedit” and hit Ctrl + Shift + Enter to open up the Registry Editor with administrative privileges. When prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
Inside the Registry Editor, use the left-hand pane to navigate to the following location:
```
HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU
```
Note: You can also paste the address directly into the navigation bar and press Enter to get there instantly.
If the WindowsUpdate key doesn’t exist, you’ll need to create it manually. To do this, right-click on the Windows key, select New > Key and name it ‘WindowsUpdate’. Then, right-click on the newly created key and select New > Key and name the newest key AU.
With the AU key selected, move over to the right-hand pane, right-click on an empty space and choose New > String value. Next, rename the newly created string value to UseWUServer.
Once the UseWUServer key has been created, double-click on it and set it’s Value Data to 0.
Close the Registry Editor, restart your computer and see if the issue has been resolved at the next system startup.

If this method didn’t resolve the issue or it wasn’t applicable, move down to the next method below.

Method 2: Cleaning the CBS logs

Some users that we’re encountering this exact issue have reported that they managed to resolve the issue after deleting the CBS (Component Based Servicing) logs related to DISM. After doing this and re-running the DISM command, some affected users have reported that the 0x800f0954 error was no longer occurring.

Here’s what you need to do:

Open File Explorer and navigate to the following location:
```
C:WindowsLogsCBS
```
Once you get inside the CBS folder, select everything there and choose Delete.
After every file .log and .cab file is deleted, you can close the CBS folder.
Press Windows key + R to open up a Run dialog box. Then, type “cmd” and press Ctrl + Shift + Enter to open up an elevated Command Prompt. When you see the UAC (User Account Control), click Yes to grant administrative privileges.
Inside the elevated Command Prompt, type the following command and press Enter to rerun the DISM command once again:
```
Dism.exe /online /enable-feature /featurename:NetFX3 /source:C:
```
After hitting Enter, the .NET Framework should install without the 0x800f0954 error.

If you’re still encountering the same error message or this method wasn’t applicable to your current scenario, move down to the next method below.

Method 3: Using PowerShell to install .NET Framework 3.5

If you’re encountering the 0x800f0954 error while trying to install the .NET Framework 3.5 by using DISM (Deployment Image Servicing and Management), you might be able to circumvent the error message by using Powershell.

Several affected users have reported that the error code was no longer occurring after they ran a powershell command that ended up fixing the problem. Here’s what you need to do:

Press Windows key + R to open up a run command. Then, type “powershell” and press Ctrl + Shift + Enter to open up an elevated Powershell prompt. When prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
Run dialog: powershell Then press Ctrl + Shift + Enter
Inside the elevated Powershell prompt, type the following command and press Enter to run it:
```
Add-WindowsCapability –Online -Name NetFx3~~~~ –Source D:sourcessxs
```
Close the elevated Powershell prompt and restart your machine.
At the next system startup, attempt to install the .NET Framework 3.5 once again and see if the issue has been resolved.

If the same error is still occurring, move down to the next method below.

Method 4: Using the Group Policy Editor

If you get the 0x800f0954 error while trying to add the RSAT Toolset, chances are you’ll need to make some changes using the Group Policy Editor tool. Several users have managed to solve this issue by running the Gpedit tool to modify some settings related to Component Installation and Component Repair.

After enabling a certain local policy and allowing the OS to download repair content and optional features directly from WU, several users have reported that the issue was resolved.

Note: Keep in mind that the Group Policy Editor tool is not available for all Windows versions. If you have Windows 10 Home or another version that doesn’t include it, you’ll need to follow this article (here) to install the policy editor on your computer.

If you have the Group Policy Editor on your Windows version, here’s a quick guide on how to make the necessary edits:

Press Windows key + R to open up a Run dialog box. Then, type “gpedit.msc” and press Enter to open up the Local Group Policy Editor. If you’re prompted by the UAC (User Account Control), click Yes to grant administrative privileges.
Typing “gpedit.msc” in the Run prompt
Once you’re inside the Local Group Policy Editor, use the left-hand pane to navigate to the following location:
Computer ConfigurationAdministrative TemplatesSystem
Then, with System selected, go over to the right-hand pane and double-click on the Specify settings for optional component installation and component repair.
Specify settings for optional component installation and component repair
Next, set the policy to Enabled and make sure to check the box associated with Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (USUS).
Enable the required Policy
Hit Apply to save the configuration, then close the Local Group Policy Editor and restart your computer.
At the next system startup, the error should no longer occur.

Solution 5: Changing Registry Value UseWUServer

If none of the above methods work, we will attempt to change the UseWUServer registry entry and change it to disabled. Apparently, after a recent Windows update, this key was conflicting with Windows update service and causing the error message under discussion. Make sure that you are logged in as an administrator before proceeding further and backup your registry just in case.

Press Windows + R, type “regedit” in the dialogue box and press Enter.

Once in the registry editor, navigate to the following path:

HKLM/Software/Policies/Microsoft/Windows/WindowsUpdate/AU/UseWUServer

Now, change the value from 1 to 0.
After making the following changes, restart your computer and start the update service again. Check if the issue is resolved.

Kevin Arrows

Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Источник

Skipping the WSUS server is a quick way to fix this

by Ola-Hassan Bolaji

A Computer Engineering graduate, he has spent most of his life reading and writing about computers. He finds joy in simplifying complex topics into simple solutions for PC… read more

Updated on April 24, 2023

Reviewed by
Alex Serban

Kevin Arrows

Источник

Skipping the WSUS server is a quick way to fix this

by Ola-Hassan Bolaji

A Computer Engineering graduate, he has spent most of his life reading and writing about computers. He finds joy in simplifying complex topics into simple solutions for PC… read more

Updated on April 24, 2023

Reviewed by
Alex Serban

After moving away from the corporate work-style, Alex has found rewards in a lifestyle of constant analysis, team coordination and pestering his colleagues. Holding an MCSA Windows Server… read more

If you are getting the error code 0x800f0954 while trying to install .NET Framework, it might be because of a corrupt CBS log file.
You can solve this issue quickly and effectively by bypassing the WSUS server.
Clearing the CBS log file and restarting the installation process is another surefire fix.

XINSTALL BY CLICKING THE DOWNLOAD FILE

Easily get rid of Windows errors
Fortect is a system repair tool that can scan your complete system for damaged or missing OS files and replace them with working versions from its repository automatically.
Boost your PC performance in three easy steps:

Download and Install Fortect on your PC.
Launch the tool and Start scanning
Right-click on Repair, and fix it within a few minutes

0 readers have already downloaded Fortect so far this month

.NET Framework is one of the many important optional Windows features that users can decide to install or not. However, installing these features is not usually straightforward, with users reporting a frustrating error code 0x800f0954.

While this error can be due to various factors, it is not the most difficult to fix, as shown in this comprehensive guide.

What is error code 0x800f0954 installing .NET Framework 3.5 on Windows 11 or 10?

The error code 0x800f0954 shows up if your PC cannot get through to the Windows Update server while you are trying to install an optional update.

Below are some of the potential causes of this issue:

Wrong settings: In some cases, this issue can be due to the Download repair content and optional features directly from the Windows Update setting on the Group Policy editor. You need to ensure this feature is enabled to bypass this error code.
Corrupt CBS log: This problem can sometimes occur because of a corrupt log file on your PC. You need to clean these junk files and try the installation of the optional feature again.

How do I fix error 0x800f0954?

1. Bypass Windows Update server

Press the Windows key + R, type regedit, and click OK.
Navigate to the path below in the left pane: HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU
Now, double-click the UseWUServer option in the right pane. If the WindowsUpdate option does not exist as in the path above, follow these steps to create it:
Set its Value data to 0 and click the OK button.
Finally, restart your PC and check if you can install the optional updates.

That is how to fix the error code 0x800f0954 on Windows 10 or 11 using the registry. This solution will only help you bypass the Windows Update server.

2. Use PowerShell

Press the Windows key + S, type powershell, and select Run as administrator under Windows PowerShell.
Copy and paste the command below and hit Enter to run it: Add-WindowsCapability –Online -Name NetFx3~~~~ –Source D:sourcessxs
Finally, restart your PC and try to install .NET Framework 3.5 again.

Some PC issues are hard to tackle, especially when it comes to missing or corrupted system files and repositories of your Windows.
Be sure to use a dedicated tool, such as Fortect, which will scan and replace your broken files with their fresh versions from its repository.

Sometimes, the error 0x800f0954 can be due to minor compatibility issues on your PC. The solution is to run the command above to clear these glitches.

3. Use the Group Policy editor to bypass WSUS

Press the Windows key + R, type gpedit.msc, and click OK.
Navigate to the path below in the left pane: Computer ConfigurationAdministrative TemplatesSystem
Now, double-click Specify settings for optional component installation and component repair in the right pane.
Next, tick the Enabled button.
Check the box for Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS).
Finally, click the Apply button, followed by OK.

Another effective solution to fix the 0x800f0954 error while trying to install optional features on your PC is to make changes to your Group Policy editor.

Read more about this topic

Apoint.exe: What is it & How to Fix its Errors
NTVDM.exe: What is it & How to Fix its Errors
Deleting Files Doesn’t Free up Space? Here’s What to Do
Shpafact.dll: What is It And How to Fix Its Errors
Diskpart Failed to Clear Disk Attributes: 4 Ways to Fix

4. Use Windows ISO or DVD

Get a Windows ISO using the Media Creation Tool.
Now, double-click the ISO file to mount it. Note the drive letter of your drive or DVD.
Press the Windows key, type cmd, and click Run as administrator under Command Prompt.
Next, copy and paste the command (replace X with your drive letter) below and hit Enter: dism /online /enable-feature /featurename:NetFX3 /Source:X:sourcessxs /LimitAccess
Finally, wait for the command to finish running and restart your PC.

If you are still getting the 0x800f0954 error while trying to install optional features on your PC, you can try to use a Windows ISO file to complete the task.

5. Clean the CBS log

Press the Windows key + E to open File Explorer and navigate to the path below: C:WindowsLogsCBS
Double-click the CBS folder and delete its content.
Press the Windows key + S, type cmd, and choose Run as administrator under Command Prompt.
Now, type the command below and hit Enter to run it: Dism.exe /online /enable-feature /featurename:NetFX3 /source:C:
Finally, wait for the command to finish running and try to install .NET Framework again.

If you got the 0x800f0954 error while using DISM restorehealth command, it might be because of a corrupt CBS log file. You need to clear this file to fix this issue.

We have reached the end of this detailed guide on the 0x800f0954 error. If you want to know how to repair a corrupt .NET Framework, check our detailed guide to do it effortlessly.

Feel free to let us know the solution that helped you fix this issue in the comments below.

Still experiencing issues?

SPONSORED

If the above suggestions have not solved your problem, your computer may experience more severe Windows troubles. We suggest choosing an all-in-one solution like Fortect to fix problems efficiently. After installation, just click the View&Fix button and then press Start Repair.

Источник

Что это за ошибка?

Меняем параметры реестра

Удаляем файлы CBS

Устанавливаем .NET Framework через командную строку

Устанавливаем дополнительные компоненты

Вопрос

Ответы

Method 1: Bypass WSUS to Install Features/Updates Directly from Windows Update

Automate the above, using PowerShell (admin)

Method 2: Bypass WSUS for Repair Content/Feature On Demand Downloads

Method 3: Install .NET Framework (or Optional Features) from Windows 10/11 ISO or DVD

One small request: If you liked this post, please share this?

Related article

What is causing the Error Code 0x800f0954?

Method 1: Bypassing the WSUS

Method 2: Cleaning the CBS logs

Method 3: Using PowerShell to install .NET Framework 3.5

Method 4: Using the Group Policy Editor

Solution 5: Changing Registry Value UseWUServer

Kevin Arrows

Skipping the WSUS server is a quick way to fix this

Kevin Arrows

Skipping the WSUS server is a quick way to fix this

What is error code 0x800f0954 installing .NET Framework 3.5 on Windows 11 or 10?

How do I fix error 0x800f0954?

1. Bypass Windows Update server

2. Use PowerShell

3. Use the Group Policy editor to bypass WSUS

4. Use Windows ISO or DVD

5. Clean the CBS log

Возможно, вам также будет интересно: