Add windowscapability сбой add windowscapability код ошибки 0x800f0907

Add windowscapability сбой add windowscapability код ошибки 0x800f0907

Вопрос

So I’ve been trying to add the RSAT for AD LDS by using either Powershell or Server Manager>Add Roles and Features, and the result is the same. «The referenced assembly could not be found. Error: 0x80073701.» I’ve seen in multiple posts where they found a referenced language package in the CBS log at c:windowsLogsCBSCBS.log and once they either remove the references in the registry key or install/re-install the language pack, the issue then goes away. I’m looking in my CBS.log and I don’t see anything about a language package missing. I do see some things about a different package though called «Microsoft-Windows-Foundation-Package

10.0.14393.0″ and immediately following that is errors about «ERROR_SXS_ASSEMBLY_MISSING.» When I do a «DISM /Online /Get-Package» that exact package shows up at the top of the list and says it is installed. Below is a screen shot of the error:

All of that to say, other posts I’ve seen mentioning to do a «sfc /scannow» and a «DISM /Online /Cleanup-Image /RestoreHealth.» When I tried the DISM command, it gave me another error that just simply outputs «0x800f0907» and that more can be found in the DISM.log. So I went there. It’s less helpful than the other log. All I can find there is this:

That’s all that looks relevant out of those two logs. An SFC /Scannow reports back that everything is fine. I’d copy and paste the text from the log, but I’m having issues pasting into this box right now and I don’t want to scrap this post. I’ll probably post it in a comment.

Источник

[FIX] Error 0x800F0907 While Installing .NET Framework 3.5 In Windows 10

6 Comments · Updated: November 14, 2016 · 05:37 PM · By Kapil Arya · Applies to: Troubleshooting, Windows 10

Earlier, we have seen how to enable .NET Framework in Windows 10, in following article:

However the PowerShell method discussed in above mentioned article requires you to specify the source files using Windows 10 ISO file. But if you’ve upgraded your earlier version of Windows to Windows 10, you may not have the source files with you. In that case, you can try enabling .NET Framework via Turn Windows Features On or Off page in Control Panel. However, when we tried to enable .NET 3.5 from there, we got this message:

Windows couldn’t complete the requested changes.

Windows couldn’t find required files to complete the requested changes. Make sure you’re connected to the Internet and try again.

Error: 0x800F0907

Closing the message ends operation with this message:

An error has occurred. Not all of the features were successfully changed.

When you try to enable the .NET 3.5 from Control Panel, Windows 10 try to activate the feature by installing some required Windows Updates. This issue can be easily solved by configuring the alternative source path which can help Windows to enable the feature without much relying on Windows Update. If you’ve source path located on some network share, you can use it here. This issue can also occur if your system is configured to get upgrades via Windows Server Update Services (WSUS) instead Windows Updates. Whatever is the case, the steps mentioned below will help you to fix this error.

FIX : Error 0x800F0907 While Installing .NET Framework 3.5 In Windows 10

1. Press + R and put gpedit.msc in Run dialog box to open Local Group Policy Editor. Click OK.

2. Next, in the Local Group Policy Editor window, navigate here:

Computer Configuration > Administrative Templates > System

3. In the right pane of System, look for Setting named Specify settings for optional component installation and component repair. Double click on this setting to modify it:

4. In the policy configuration window shown above, click on Enabled to activate the policy. Then in Options, you can specify valid alternate source file path which could have .NET Framework feature files which we’re required to enable it. You can refer policy explanation for detailed info about adding alternative source here. Also make sure Never attempt to download payload from Windows Update and Download repair content optional features directly from Windows Update instead of Windows Server Update Services (WSUS) options are checked here. Click Apply followed by OK. Close Local Group Policy Editor.

5. Press + R and put gpupdate /force in Run dialog box to update Group Policy engine. Click OK.

After updating policies, re-try to enable .NET Framework and this time it should get activated without pushing any error code.

Источник

RSAT — ошибка при установке

Remote Server Administration Tools — позволяет администрировать контроллер домена со своего рабочего компа. В моём случае с Windows 10.

Есть три способа установки:

• Общий вариант, когда мы качаем пакет и устанавливаем его вручную.
• Через дополнительные компоненты.
• Через PowerShell.

Ошибка 0x8024001d

При общем варианте установки вы можете увидеть ошибку:

Установщик обнаружил ошибку 0x8024001d

Это означает, что ваша версия Windows больше не поддерживает общий вариант установки RSAT. Устанавливайте через дополнительные компоненты или через PowerShell.

Ошибка 0x800f0954

При попытке установить RSAT через дополнительные компоненты вы можете столкнуться с ошибкой «сбой установки».

В журнале при этом ничего вразумительного не написано.

При попытке установить RSAT через PowerShell та же ошибка выглядит несколько иначе.

Сбой Add-WindowsCapability. Код ошибки: 0x800f0954

Покопавшись я понял, что проблема кроется в политиках домена, скорее всего, дополнительные компоненты пытаются установиться через доменный WSUS, а нужных пакетов там нет. С одной стороны это и не плохо, нечего юзерам ставить всякое админское ПО. С другой стороны, мне-то оно нужно.

Решим проблему через локальные политики. Запускаем gpedit.msc:

Открывается редактор локальной групповой политики. Нам нужен раздел Конфигурация компьютера > Административные шаблоны > Система > Укажите параметры для установки необязательных компонентов и восстановления компонентов. Или Computer Configuration > Administrative Templates > System > Specify settings for optional component installation and component repair.

Редактируем политику. Включаем и ставим галку «Скачайте содержимое для восстановления и дополнительные компоненты непосредственно из Центра обновления Windows вместо использования служб Windows Server Update Services (WSUS)».

Теперь, если доступ в Интернет есть, всё установится. Проверяем установку RSAT через дополнительные компоненты.

Источник

Add windowscapability сбой add windowscapability код ошибки 0x800f0907

Вопрос

We’re starting to push out Windows 10 v1809 for our new workstations and we’ve hit a bump — I can’t get snmp to work on those workstations. If I go to Control Panel > Windows Features there’s no snmp option. Using the following command:

under PowerShell as administrator gives the following error message:

I tried changing to the domain admin account but I get the same «Access is denied» error.

I found this command:

but that gives me this error:

I looked up Error: 0x800f080c and found several posts regarding .Net. These computers have 3.5 and 4.7 installed.

Any ideas, suggestions, or recommendations on how we can get snmp working on our v1809 computers?

Ответы

i also have something that can help you.

In my company we do not have access to microsoft servers (firewall rules, no windows update, no catalog. )

In my case, to install SNMP on 1809 i have to :

1) Have an internet access without restriction (my cellphone)

2) set to 0 the following registry key : HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAUusewuserver en 0

launch the following commands :

netshh winhttp reset proxy
net stop wuauserv
net start wuauserv

edit : those commands and the registry key are about specific configuration in professionnal environment (proxy server, wsus etc. ) that can mess installation from microsoft servers

3) launch the following powershell command : add-windowscapability -online -name «SNMP.Client

and it works in my case !

sorry english is not my mother tongue

Все ответы

I also found a suggestion to change this setting from 1 to 0 but no joy there either:

Get-WindowsCapability -Online -Name «SNMP*»

Add-WindowsCapability -Online -Name «SNMP.Client

TASK [systemprep : Install OpenSSH] ********************************************
fatal: [default]: FAILED! => {"changed": true, "cmd": "Get-WindowsCapability -Online -Name OpenSSH.Server* | Add-WindowsCapability -Online", "delta": "0:00:08.388772", "end": "2021-04-30 10:58:33.105127", "msg": "non-zero return code", "rc": 1, "start": "2021-04-30 10:58:24.716355", "stderr": "Add-WindowsCapability : Add-WindowsCapability failed. Error code = 0x800f0950rnAt line:1 char:119rn+ ... ability -Online -Name OpenSSH.Server* | Add-WindowsCapability -Onlinern+                                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~rn    + CategoryInfo          : NotSpecified: (:) [Add-WindowsCapability], COMExceptionrn    + FullyQualifiedErrorId : Microsoft.Dism.Commands.AddWindowsCapabilityCommand", "stderr_lines": ["Add-WindowsCapability : Add-WindowsCapability failed. Error code = 0x800f0950", "At line:1 char:119", "+ ... ability -Online -Name OpenSSH.Server* | Add-WindowsCapability -Online", "+                                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~", "    + CategoryInfo          : NotSpecified: (:) [Add-WindowsCapability], COMException", "    + FullyQualifiedErrorId : Microsoft.Dism.Commands.AddWindowsCapabilityCommand"], "stdout": "", "stdout_lines": []}