Не удалось удалить компонент ошибка 80071779

Перейти к контенту

Ошибка 0x80071779 в Windows 10 обычно встречаются в версии 1803. Обновление Windows 10 апреля 2018 года содержит проблему в сетевых соединениях. Когда пользователи пытаются удалить клиент для сетей Microsoft в свойствах сетевого адаптера, они сталкиваются с кодом ошибки 0x80071779. Давайте разберем, как удалить протокол клиента для сетей Майкрософт. 

Как исправить ошибку 0x80071779 компонента для сетей в Windows 10

Когда вы пытаетесь удалить клиент для сетей Microsoft через сетевые свойства, то вам выдаст ошибку 0x80071779. Давайте ниже разберем, как исправить её.Ошибка 0x80071779 в Windows 10

Для удаления протокола можно использовать PowerShell. 

channel

Шаг 1. Нажмите сочетание кнопок Win + X и выберите «Windows PowerShell (администратор)«.

Шаг 2. Теперь введите ниже команду и нажмите Ввод.

Get-NetAdapterBinding

команда Get-NetAdapterBinding

Шаг 3. Эта команда покажет Вам ваши сетевые адаптеры и клиент для сетей Microsoft (ms_msclient). У вас таже как и у меня могут быть куча подключений, запомните свое основное подключение или то в котором вы хотите удалить клиент для сетей Microsoft. В моем случае это Ethernet.

Список сетевых адаптеров

Шаг 4. Чтобы удалить сетевой протокол введите еще одну команду. Замените в команде Ethernet на свое, если у вас другой адаптер. 

Disable-NetAdapterBinding -Name „Ethernet“ -ComponentID ms_msclient

Удалить протокол клиента для сетей Microsoft

Смотрите еще:

  • Как сбросить настройки сети
  • Как изменить имя профиля сети в Windows
  • Не найден сетевой путь ошибка 0x80070035
  • Не удается получить доступ к сайту и найти DNS-адрес сервера
  • Не удается подключиться к WiFi или Локальной сети в Windows 10 

[ Telegram | Поддержать ]

  • Remove From My Forums

  • Question

  • 1- wireless concoction problem :

    I do update my driver to Dell Inc. Inspiron 5537  Dell Wireless 1705 802.11b/g/n (2.4GHZ)
    but now the signal of wi-fi many time going and some time get 3 sign or 2 sign or 1 sign in signal the wireless connection is not fixed at the same level
    I do everything like reset wifi and reinstall driver but its same problem 

    before I do have original driver but I forget what the name its working great before I update wi-fi driver so what I can do to fixing it or what the original driver for that model  ?

    2- cannot uninstall (Error: 0x80071779)

     I have just updated my PC to the latest build 

    can’t uninstall the Client for Microsoft Networks or other network components. You receive the following error message:

    Could not uninstall the Client for Microsoft Networks feature.

    The error is 0x80071779.

    i read can use  PowerShell cmdlet to remove all but when i do i get same the screenshot and cant uninstall the Client 

    hope to get help thanks

  • Remove From My Forums

  • Question

  • 1- wireless concoction problem :

    I do update my driver to Dell Inc. Inspiron 5537  Dell Wireless 1705 802.11b/g/n (2.4GHZ)
    but now the signal of wi-fi many time going and some time get 3 sign or 2 sign or 1 sign in signal the wireless connection is not fixed at the same level
    I do everything like reset wifi and reinstall driver but its same problem 

    before I do have original driver but I forget what the name its working great before I update wi-fi driver so what I can do to fixing it or what the original driver for that model  ?

    2- cannot uninstall (Error: 0x80071779)

     I have just updated my PC to the latest build 

    can’t uninstall the Client for Microsoft Networks or other network components. You receive the following error message:

    Could not uninstall the Client for Microsoft Networks feature.

    The error is 0x80071779.

    i read can use  PowerShell cmdlet to remove all but when i do i get same the screenshot and cant uninstall the Client 

    hope to get help thanks

  • Remove From My Forums

  • Question

  • 1- wireless concoction problem :

    I do update my driver to Dell Inc. Inspiron 5537  Dell Wireless 1705 802.11b/g/n (2.4GHZ)
    but now the signal of wi-fi many time going and some time get 3 sign or 2 sign or 1 sign in signal the wireless connection is not fixed at the same level
    I do everything like reset wifi and reinstall driver but its same problem 

    before I do have original driver but I forget what the name its working great before I update wi-fi driver so what I can do to fixing it or what the original driver for that model  ?

    2- cannot uninstall (Error: 0x80071779)

     I have just updated my PC to the latest build 

    can’t uninstall the Client for Microsoft Networks or other network components. You receive the following error message:

    Could not uninstall the Client for Microsoft Networks feature.

    The error is 0x80071779.

    i read can use  PowerShell cmdlet to remove all but when i do i get same the screenshot and cant uninstall the Client 

    hope to get help thanks

  • Remove From My Forums

  • Question

  • 1- wireless concoction problem :

    I do update my driver to Dell Inc. Inspiron 5537  Dell Wireless 1705 802.11b/g/n (2.4GHZ)
    but now the signal of wi-fi many time going and some time get 3 sign or 2 sign or 1 sign in signal the wireless connection is not fixed at the same level
    I do everything like reset wifi and reinstall driver but its same problem 

    before I do have original driver but I forget what the name its working great before I update wi-fi driver so what I can do to fixing it or what the original driver for that model  ?

    2- cannot uninstall (Error: 0x80071779)

     I have just updated my PC to the latest build 

    can’t uninstall the Client for Microsoft Networks or other network components. You receive the following error message:

    Could not uninstall the Client for Microsoft Networks feature.

    The error is 0x80071779.

    i read can use  PowerShell cmdlet to remove all but when i do i get same the screenshot and cant uninstall the Client 

    hope to get help thanks

  • Hi,

    This is by design in Windows 10 1803.

    Quote MSFT Jeffrey’s explanation:

    I agree that the message box could be a lot better here.  We’ll look into that for the next release.

    Blocking uninstallation of inbox drivers is by design, however.  We do not support using this UI to remove built-in drivers.  We don’t test in that configuration, and we know that uninstalling drivers breaks things.

    As you’ve probably already noticed, uninstalling a driver from this UI was never permanent.  E.g., if you uninstalled a driver from Windows 7, then upgraded to Windows 8, it would get reinstalled.  Maybe more disconcertingly, a monthly security
    update that affected that particular driver could reinstall it.  The reason is that the OS’s servicing stack isn’t really aware of this UI, and doesn’t realize when this UI is removing drivers.  The OS’s servicing stack will reinstall the driver
    any time the driver is serviced.

    There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or LBFO
    team.  And if you uninstall it, bridges and teams will be permanently broken.  We’ve gotten support requests from quite a few customers who inadvertently damaged their systems by uninstalling drivers, and need help putting it back together. 
    In Windows 10 1803, we block attempts to damage the system.

    Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V, WDAG, and Containers optional features.  Optional features
    are indeed supported and we do test the OS with the feature removed.

    If there are specific drivers that you would like to be removable, but which are not currently part of an Optional Feature, please file a feature request in the Feedback Hub.

    Please note that you can always unbind the driver from any/all NICs, either using this GUI or using the PowerShell cmdlet «Disable-NetAdapterBinding».  The only change is that you can’t deregister the OS driver entirely.  But if you
    unbind the driver from all your NICs, it’s effectively the same as uninstalling the driver.

    Also note that 3rd party drivers can still be installed & uninstalled (or bound/unbound) from this GUI.  The change only affects the drivers that are part of the OS.

    Source thread is here:

    https://social.technet.microsoft.com/Forums/en-US/38e53f34-a607-4368-9d9b-7acba1d32b80/cannot-uninstall-protocols-such-as-client-for-microsoft-networks?forum=win10itpronetworking

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact
    tnmff@microsoft.com.

    • Edited by

      Thursday, May 3, 2018 2:21 AM

    • Marked as answer by
      ONEIGHBOUR
      Friday, May 4, 2018 8:38 AM

    • Источник

    Содержание

    1. Исправить ошибку 0x80071779 в Windows 10
    2. Как исправить ошибку 0x80071779 компонента для сетей в Windows 10
    3. Не открываются общие сетевые SMB папки в Windows 10
    4. Вы не можете получить гостевой доступ к общей папке без проверки подлинности
    5. Вашей системе необходимо использовать SMB2 или более позднюю
    6. Ошибка 0x80071779 при удалении сетевых компонентов в Windows 10
    7. Симптомы
    8. Причина
    9. Решение
    10. Дополнительные сведения
    11. Не могу обновить Windows 10. Выдает ошибку 0x80070005
    12. Ответы (8) 

    Исправить ошибку 0x80071779 в Windows 10

    Ошибка 0x80071779 в Windows 10 обычно встречаются в версии 1803. Обновление Windows 10 апреля 2018 года содержит проблему в сетевых соединениях. Когда пользователи пытаются удалить клиент для сетей Microsoft в свойствах сетевого адаптера, они сталкиваются с кодом ошибки 0x80071779. Давайте разберем, как удалить протокол клиента для сетей Майкрософт.

    Как исправить ошибку 0x80071779 компонента для сетей в Windows 10

    Когда вы пытаетесь удалить клиент для сетей Microsoft через сетевые свойства, то вам выдаст ошибку 0x80071779. Давайте ниже разберем, как исправить её.

    Для удаления протокола можно использовать PowerShell.

    Шаг 1. Нажмите сочетание кнопок Win + X и выберите «Windows PowerShell (администратор)«.

    Шаг 2. Теперь введите ниже команду и нажмите Ввод.

    Get-NetAdapterBinding

    Шаг 3. Эта команда покажет Вам ваши сетевые адаптеры и клиент для сетей Microsoft (ms_msclient). У вас таже как и у меня могут быть куча подключений, запомните свое основное подключение или то в котором вы хотите удалить клиент для сетей Microsoft. В моем случае это Ethernet.

    Шаг 4. Чтобы удалить сетевой протокол введите еще одну команду. Замените в команде Ethernet на свое, если у вас другой адаптер.

    Disable-NetAdapterBinding -Name „Ethernet“ -ComponentID ms_msclient

    Не открываются общие сетевые SMB папки в Windows 10

    Если вы из Windows 10 не можете открыть сетевые папки на других сетевых устройствах (NAS, Samba сервера Linux) или на компьютерах со старыми версиями Windows (Windows 7/ XP /2003), скорее всего проблема связана с тем, что в вашей новой версии Windows 10 отключена поддержка устаревших и небезопасных версий протокола SMB (используется в Windows для доступа к общим сетевым папкам и файлам). Так, начиная с Windows 10 1709, был отключен протокол SMBv1 и анонимный (гостевой) доступ к сетевым папкам по протоколу SMBv2.

    Конкретные действия, которые нужно предпринять зависят от ошибки, которая появляется в Windows 10 при доступе к общей папке и от настроек удаленного SMB сервера, на котором хранятся общие папки.

    Вы не можете получить гостевой доступ к общей папке без проверки подлинности

    Начиная с версии Windows 10 1709 (Fall Creators Update) Enterprise и Education пользователи стали жаловаться, что при попытке открыть сетевую папку на соседнем компьютере стала появляться ошибка:

    При это на других компьютерах со старыми версиями Windows 8.1/7 или на Windows 10 с билдом до 1709, эти же сетевые каталоги открываются нормально. Эта проблем связана с тем, что в современных версиях Windows 10 (начиная с 1709) по умолчанию запрещен сетевой доступ к сетевым папкам под гостевой учетной записью по протоколу SMBv2 (и ниже). Гостевой (анонимный) доступ подразумевают доступ к сетевой папке без аутентификации. При доступе под гостевым аккаунтом по протоколу SMBv1/v2 не применяются такие методы защиты трафика, как SMB подписывание и шифрование, что делает вашу сессию уязвимой против MiTM (man-in-the-middle) атак.

    При попытке открыть сетевую папку под гостем по протоколу SMB2, в журнале клиента SMB (Microsoft-Windows-SMBClient) фиксируется ошибка:

    В большинстве случае с этой проблемой можно столкнуться при использовании старых версий NAS (обычно для простоты настройки на них включают гостевой доступ) или при доступе к сетевым папкам на старых версиях Windows 7/2008 R2 или Windows XP /2003 с настроенным анонимным (гостевым) доступом (см. таблицу поддерживаемых версий SMB в разных версиях Windows).

    В этом случае Microsoft рекомендует изменить настройки на удаленном компьютере или NAS устройстве, который раздает сетевые папки. Желательно переключить сетевой ресурс в режим SMBv3. А если поддерживается только протокол SMBv2, настроить доступ с аутентификацией. Это самый правильный и безопасный способ исправить проблему.

    В зависимости от устройства, на котором хранятся сетевые папки, вы должны отключить на них гостевой доступ.

    • NAS устройство – отключите гостевой доступ в настройках вашего NAS устройства (зависит от модели);
    • Samba сервер на Linux — если вы раздаете SMB каталог с Linux, в конфигурационном файле smb.conf в секции [global] нужно добавить строку: map to guest = never
      А в секции с описанием сетевой папки запретить анонимный доступ: guest ok = no
    • В Windows вы можете включить общий доступ к сетевым папкам и принтерам с парольной защитой в разделе Control PanelAll Control Panel ItemsNetwork and Sharing CenterAdvanced sharing settings. Для All Networks (Все сети) в секции “Общий доступ с парольной защитой” (Password Protected Sharing) имените значение на “Включить общий доступ с парольной защитой” (Turn on password protected sharing). В этом случае анонимный (гостевой) доступ к папкам будет отключен и вам придется создать локальных пользователей, предоставить им доступ к сетевым папкам и принтерам и использовать эти аккаунты для подключения к общим папкам на этом компьютере.

    Есть другой способ – изменить настройки вашего SMB клиента и разрешить доступ с него на сетевые папки под гостевой учетной записью.

    Чтобы разрешить гостевой доступ с вашего компьютера, откройте редактор групповых политик (gpedit.msc) и перейдите в раздел: Конфигурация компьютера -> Административные шаблоны -> Сеть -> Рабочая станция Lanman (Computer Configuration ->Administrative templates -> Network (Сеть) -> Lanman Workstation). Включите политику Enable insecure guest logons (Включить небезопасные гостевые входы).

    В Windows 10 Home, в которой нет редактора локальной GPO, вы можете внести аналогичное изменение через редактор реестра вручную:

    Или такой командой:

    reg add HKLMSYSTEMCurrentControlSetServicesLanmanWorkstationParameters /v AllowInsecureGuestAuth /t reg_dword /d 00000001 /f

    Вашей системе необходимо использовать SMB2 или более позднюю

    Другая возможная проблема при доступе к сетевой папке из Windows 10 – поддержка на стороне сервера только протокола SMBv1. Т.к. клиент SMBv1 по умолчанию отключен в Windows 10 1709, при попытке открыть шару вы можете получить ошибку:

    При этом соседние устройства SMB могут не отображаться в сетевом окружении и при открытии по UNC пути может появляться ошибка 0x80070035.

    Т.е. из сообщения об ошибке четко видно, что сетевая папка поддерживает только SMBv1 протокол доступа. В этом случае нужно попытаться перенастроить удаленное SMB устройство для поддержки как минимум SMBv2 (правильный и безопасный путь).

    Если сетевые папки раздает Samba на Linux, вы можете указать минимально поддерживаемую версию SMB в файле smb.conf так:

    В Windows 7/Windows Server 2008 R2 вы можете отключить SMBv1 и разрешить SMBv2 так:
    Set-ItemProperty -Path «HKLM:SYSTEMCurrentControlSetServicesLanmanServerParameters» SMB1 -Type DWORD -Value 0 –Force

    Set-ItemProperty -Path «HKLM:SYSTEMCurrentControlSetServicesLanmanServerParameters» SMB2 -Type DWORD -Value 1 –Force

    В Windows 8.1 отключите SMBv1, разрешите SMBv2 и SMBv3 и проверьте что для вашего сетевого подключения используется частный или доменный профиль:

    Disable-WindowsOptionalFeature -Online -FeatureName «SMB1Protocol»
    Set-SmbServerConfiguration –EnableSMB2Protocol $true

    Если ваше сетевое устройство (NAS, Windows XP, Windows Server 2003), поддерживает только протокол SMB1, в Windows 10 вы можете включить отдельный компонент SMB1Protocol-Client. Но это не рекомендуется.

    Запустите консоль PowerShell и проверьте, что SMB1Protocol-Client отключен ( State: Disabled ):

    Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol-Client

    Включите поддержку протокола SMBv1 (потребуется перезагрузка):

    Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol-Client

    Также вы можете включить/отключить дополнительные компоненты Windows 10 (в том числе SMBv1) из меню optionalfeatures.exe -> SMB 1.0/CIFS File Sharing Support

    В Windows 10 1709 и выше клиент SMBv1 автоматически удаляется, если он не использовался более 15 дней (за это отвечает компонент SMB 1.0/CIFS Automatic Removal).

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

    Ошибка 0x80071779 при удалении сетевых компонентов в Windows 10

    Эта статья помогает устранить ошибку 0x80071779, которая возникает при отсечении клиента для Microsoft Networks или других сетевых компонентов.

    Оригинальная версия продукта: Окно 10 — все выпуски
    Исходный номер КБ: 4340181

    Симптомы

    Начиная с Windows 10, версии 1803 и более новых устройств или компьютеров, нельзя удалить клиент для Microsoft Networks или других сетевых компонентов. Вы получаете следующее сообщение об ошибке:

    Не удалось удалить функцию Client for Microsoft Networks.

    Причина

    Такое поведение является особенностью данного продукта.

    Решение

    Корпорация Майкрософт не поддерживает использование этого GUI или netcfg для съемки протоколов или встроенных драйверов. Вместо этого можно отсеять драйвер из сетевых адаптеров с помощью этого GUI или cmdlet Disable-NetAdapterBinding PowerShell. Фактически это то же самое, что и при отстраивном драйвере.

    Дополнительные сведения

    Если существуют определенные драйверы, которые необходимо удалить, но которые в настоящее время не являются частью необязательных функций, подаст запрос на функции в центре отзывов.

    Не могу обновить Windows 10. Выдает ошибку 0x80070005

    Ответы (8) 

    BT(если она есть), остановить службу обновлений, очистить содержимое папки c:WindowsSoftwareDistribution, и повторить поиск обновлений.

    3 польз. нашли этот ответ полезным

    Был ли этот ответ полезным?

    К сожалению, это не помогло.

    Отлично! Благодарим за отзыв.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв, он поможет улучшить наш сайт.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв.

    1 пользователь нашел этот ответ полезным

    Был ли этот ответ полезным?

    К сожалению, это не помогло.

    Отлично! Благодарим за отзыв.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв, он поможет улучшить наш сайт.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв.

    __
    Если мой ответ вам помог, пожалуйста, отметьте его как ответ.

    Disclaimer: В ответе могут быть ссылки на сайты не на сайты Microsoft, Все советы с таких сайтов Вы выполняете на свой страх и риск.

    Был ли этот ответ полезным?

    К сожалению, это не помогло.

    Отлично! Благодарим за отзыв.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв, он поможет улучшить наш сайт.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв.

    Был ли этот ответ полезным?

    К сожалению, это не помогло.

    Отлично! Благодарим за отзыв.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв, он поможет улучшить наш сайт.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв.

    __
    Если мой ответ вам помог, пожалуйста, отметьте его как ответ.

    Disclaimer: В ответе могут быть ссылки на сайты не на сайты Microsoft, Все советы с таких сайтов Вы выполняете на свой страх и риск.

    6 польз. нашли этот ответ полезным

    Был ли этот ответ полезным?

    К сожалению, это не помогло.

    Отлично! Благодарим за отзыв.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв, он поможет улучшить наш сайт.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв.

    Был ли этот ответ полезным?

    К сожалению, это не помогло.

    Отлично! Благодарим за отзыв.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв, он поможет улучшить наш сайт.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв.

    Был ли этот ответ полезным?

    К сожалению, это не помогло.

    Отлично! Благодарим за отзыв.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв, он поможет улучшить наш сайт.

    Насколько Вы удовлетворены этим ответом?

    Благодарим за отзыв.

    Здравствуйте, Сава Знатнов,

    Приносим извинения за длительное ожидание ответа и благодарим за предоставленную информацию.

    Если проблема с обновлением все еще актуальна, пожалуйста, попробуйте выполнить следующее:

    1. Если у Вас есть возможность установить вновь, попробуйте удалить любое стороннее антивирусное ПО.

    2. Выполните следующие проверки и автоматические исправления:
    Для этого запустите командную строку от имени администратора.
    — Введите Dism / Online / Cleanup — Image / CheckHealth и нажмите Ввод
    — Вне зависимости от результатов введите Dism / Online / Cleanup — Image / RestoreHealth и нажмите Ввод
    DISM (подробнее по ссылке) может помочь устранить некоторые ошибки повреждения Windows .
    — sfc / scannow и нажмите Ввод (средство проверки системных файлов)

    3. Отключите те устройства, которые Вам не потребуются.

    Попробуйте установить обновление повторно.

    Если результат тот же, пожалуйста, расскажите подробно о выполненных действиях.
    Также, просим указать полное название модели материнской платы (если используете стационарный компьютер) или Вашего ноутбука.
    Для этого выберите сочетание клавиш Win + R > укажите msinfo 32 > нажмите ввод
    В случае ноутбука модель можно найти на самом устройстве (на корпусе).     Она будет указана снизу на задней крышке.

    Ждем Вашего ответа.
    Мы будем рады предоставить дальнейшую поддержку.

    Всего доброго,
    Кристина

    Источник

    mstscax.dll error and 0x80071779 in Windows 10 usually occur in version 1803. The Windows 10 April 2018 Update contains several problems in network and RDP connections. It appears that there is no NIC adapter binding for the network that can be uninstalled through GUI. However, you can get rid of  mstscax.dll error and 0x80071779 in Windows 10 pretty easily.

    When users make an attempt to uninstall the client for Microsoft networks in the properties of a network adapter, they come across an Error Code 0x80071779. Whereas mstscax.dll message may show while using Remote Desktop Protocol for remote connections in Windows 10. However, Microsoft mentioned mstscax.dll error and 0x80071779 problems in KB articles along with their solutions.

    Error 0x80071779 in Windows 10

    When the administrator of Windows 10 version 1803 based device tries to uninstall the client for Microsoft networks through the network properties, they come across this specific issue. Probably a few numbers of users may need to perform this uninstallation in order to remove Microsoft networks.

    How to Fix mstscax.dll error and 0x80071779 in Windows 10 Pic 1

    Fix Through PowerShell

    You can use the PowerShell cmdlet Disable-NetAdapterBinding to dispel the protocol. Here is the procedure –

    Step-1: Make a joint press of Win+X in order to open Power user menu.

    Step-2: Select “Windows PowerShell (Admin)” from the visible list and when a UAC appears, do a click on Yes to continue.

    Explore more ways to Run PowerShell as administrator in Windows 10.

    Step-3: Now type in the following command after the blinking cursor and then hit Enter.

    Get-NetAdapterBinding

    How to Fix mstscax.dll error and 0x80071779 in Windows 10 Pic 2

    This command will list all adapter bindings where ms_msclient specifies Microsoft client and ms_pacer addresses the QoS packet planner.

    Step-4: Moving ahead, type the below-given command in PowerShell and press Enter in order to delete a network protocol.

    Disable-NetAdapterBinding -Name „Ethernet0“ -ComponentID ms_msclient

    Note- To complete the process perfectly make sure you have put your Network name in the place of Ethernet0.

    mstscax.dll Error in Windows 10

    As mentioned above, this error shows up while using Remote Desktop Protocol (in short RDP) for remote connections in Windows 10. This error also seems to appear after the installation of an update such as KB4284835.

    Furthermore, this problem comes up on PCs where mstsc.exe and mstxcax.dll files were replaced with a previous version of these files. Replacing them from earlier versions of the OS fails to support and thus lead to an unexpected behavior. And as a result, when users make an attempt to install future updates (KB4284835), file mismatch error occurs.

    Hence, to resolve it, go through the below-given sequence of steps.

    Step-1: At first, take ownership of your PC. And then provide full authorization to mstscax.dll and mstsc.exe files respectively.

    Step-2: Uninstall the update that is causing this issue which is probably KB4284835.

    Step-3: Processing forward, restore original Windows 10 files (mstsc.exe and mstscax.dll) to the following folder.

    %windir%system32

    Step-4: After successfully restoring the files, restart Windows 10 PC.

    Step-5: Next, Reinstall the update again.

    Step-6: Finally, again Reboot your computer once again in order to finish the process.

    That’s all. Hopefully, you have resolved the issue already. If you have any question, don’t hesitate to ask.

    Repair any Windows problems such as Blue/Black Screen, DLL, Exe, application, Regisrty error and quickly recover system from issues using Reimage.

    • Remove From My Forums

    • Question

    • When trying to uninstall protocols from adapter, I get the error below.

      Could not uninstall the Client for Microsoft Networks feature.

      The error is 0x80071779

      I have uninstalled all the adapters, reset winsock…

      I am running Microsoft Windows [Version 10.0.17134.1]

      • Edited by
        rbcarra
        Thursday, April 19, 2018 3:38 AM

    All replies

    • Hi rbcarra,

      Based on my test, yes and I can reproduce your problem.

      It can be uninstalled on previous version, like Windows 10 1709, Windows 10 1607 etc. But when I uninstall it on Windows 10 1803, the result is same as yours:

      And I capture the activity on Windows 10 1709 and Windows 10 1803, nothing can be found:

      I will submit this feedback via our own channel. It’s also recommend you submit it via built-in Feedback app. If any update, I will post here.

      Please remember to mark the replies as answers if they help.
      If you have feedback for TechNet Subscriber Support, contact
      tnmff@microsoft.com.

      • Proposed as answer by
        Karen_HuMicrosoft contingent staff
        Monday, April 23, 2018 8:11 AM

    • Same here. Upgrade or even fresh install of 1803 borks this feature.

    • Hello,

      Why would we need to remove the Client for Microsoft Networks?

      Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

    • It is unspecific to the protocol. You cannot remove any protocol at the moment.

    • Hi rbcarras,

      Try to change the TCP/IP properties in the Registry with the following path:
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL11.SQL2012MSSQLServerSuperSocketNetLibTcp]

      Momominta

      What if i don’t even have this entry?

    • I agree that the message box could be a lot better here.  We’ll look into that for the next release.

      Blocking uninstallation of inbox drivers is by design, however.  We do not support using this UI to remove built-in drivers.  We don’t test in that configuration, and we know that uninstalling drivers breaks things.

      As you’ve probably already noticed, uninstalling a driver from this UI was never permanent.  E.g., if you uninstalled a driver from Windows 7, then upgraded to Windows 8, it would get reinstalled.  Maybe more disconcertingly, a monthly security
      update that affected that particular driver could reinstall it.  The reason is that the OS’s servicing stack isn’t really aware of this UI, and doesn’t realize when this UI is removing drivers.  The OS’s servicing stack will reinstall the driver
      any time the driver is serviced.

      There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or LBFO team. 
      And if you uninstall it, bridges and teams will be permanently broken.  We’ve gotten support requests from quite a few customers who inadvertently damaged their systems by uninstalling drivers, and need help putting it back together.  In Windows
      10 1803, we block attempts to damage the system.

      Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V, WDAG, and Containers optional features.  Optional features
      are indeed supported and we do test the OS with the feature removed.

      If there are specific drivers that you would like to be removable, but which are not currently part of an Optional Feature, please file a feature request in the Feedback Hub.

      Please note that you can always unbind the driver from any/all NICs, either using this GUI or using the PowerShell cmdlet «Disable-NetAdapterBinding».  The only change is that you can’t deregister the OS driver entirely.  But if you unbind
      the driver from all your NICs, it’s effectively the same as uninstalling the driver.

      Also note that 3rd party drivers can still be installed & uninstalled (or bound/unbound) from this GUI.  The change only affects the drivers that are part of the OS.

    • Hello,

      Why would we need to remove the Client for Microsoft Networks?

      Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

      We want remove «Client for Microsoft Networks», LLDP and many others ’cause they are unnecessary to system operation specially on
      public networks and machines that access many unknown networks…

    • Uninstalling all items for my connection but TCP/IPv4 never broke anything for me on a stand alone system.
      You guys force way to much to be installed on Windows pr. default and preventing uninstallation on top is just a silly move.

      Regards Joerg Baermann

      • Proposed as answer by
        krakdcorn
        Sunday, November 18, 2018 6:23 PM

    • You can always unbind these drivers — just uncheck the box next to its name.  Unbinding the driver will 100% prevent it from communicating on that network.

    • We do not support using this UI to remove built-in Drivers.

      Since when ? — You have this UI with the Option to install/remove Protocols, inside Windows for almost 30 Years !!! — Not sure, if it was there in Windows 3.11 but Windows 95 got it… — Even some external Network/Wlan protocols, work with exactly this Panel!
      — Are you sure, you speak for the whole MS-Company, when you say, you just drop the support, for Network Protocol, de-install, re-install, install, cause one update broke it ?

      • Edited by
        Beschwerde
        Sunday, May 13, 2018 7:29 PM

    • There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or
      LBFO team.   …

      Why is this even on the client SKU as NIC teams are not supported on client SKUs ?

    • I recall an advanced Windows NT course where we taught unbinding protocols to a NIC in order to lock down a machine. Part of the Microsoft curriculum taught how to take it a step further and actually uninstall the protocols. This was back in the late 1990’s!
      Given the advancements in technology since then and even greater cyber threats of today, why in the world would Microsoft ever prevent us from uninstalling a protocol if we didn’t want it there? This is a huge problem.

    • A little workaround I did to fix this «little bug». I have services like Server and
      Workstation disabled (plus a few other things), that should take care of the «Client for Microsoft Network» and «File and Printer Sharing». As for the rest, disabling the driver should prevent them from working.

      rem Link-Layer Topology Discovery Responder / Default - 2
reg add "HKLMSystemCurrentControlSetServicesrspndr" /v "Start" /t REG_DWORD /d "4" /f

rem Link-Layer Topology Discovery Mapper I/O Driver / Default - 2
reg add "HKLMSystemCurrentControlSetServiceslltdio" /v "Start" /t REG_DWORD /d "4" /f

rem Microsoft LLDP Protocol Driver / Default - 2
reg add "HKLMSystemCurrentControlSetServicesMsLldp" /v "Start" /t REG_DWORD /d "4" /f

rem Microsoft Virtual Network Adapter Enumerator / Default - 3
reg add "HKLMSystemCurrentControlSetServicesNdisVirtualBus" /v "Start" /t REG_DWORD /d "4" /f

rem QoS for storage I/O traffic / Default - 2
reg add "HKLMSystemCurrentControlSetServicesstorqosflt" /v "Start" /t REG_DWORD /d "4" /f

rem QoS Multimeda Class Scheduler / Default - 2
reg add "HKLMSystemCurrentControlSetServicesMMCSS" /v "Start" /t REG_DWORD /d "4" /f

rem QoS Packet Scheduler / Default - 1
reg add "HKLMSystemCurrentControlSetServicesPsched" /v "Start" /t REG_DWORD /d "4" /f

rem Named pipe service trigger provider / Default - 1
rem https://msdn.microsoft.com/en-us/library/windows/desktop/aa365590(v=vs.85).aspx
reg add "HKLMSystemCurrentControlSetServicesnpsvctrig" /v "Start" /t REG_DWORD /d "4" /f

rem NetBIOS Interface / Default - 1
reg add "HKLMSystemCurrentControlSetServicesNetBIOS" /v "Start" /t REG_DWORD /d "4" /f

rem NetBIOS over TCP/IP / Default - 1
reg add "HKLMSystemCurrentControlSetServicesNetBT" /v "Start" /t REG_DWORD /d "4" /f

rem Remote Desktop Device Redirector Bus Driver / Default - 3
reg add "HKLMSystemCurrentControlSetServicesrdpbus" /v "Start" /t REG_DWORD /d "4" /f

rem The framework for network mini-redirectors / Default - 1
rem https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/the-redirected-drive-buffering-subsystem
reg add "HKLMSystemCurrentControlSetServicesrdbss" /v "Start" /t REG_DWORD /d "4" /f

rem A little bonus - Disable IPv6/LMHOSTS lookup/NetBIOS and Set DNS Servers
netsh int ipv6 isatap set state disabled
netsh int teredo set state disabled
netsh interface ipv6 6to4 set state state=disabled undoonstop=disabled
reg add "HKLMSystemCurrentControlSetServicesTcpip6Parameters" /v "DisabledComponents" /t REG_DWORD /d "255" /f
wmic nicconfig where DHCPEnabled=TRUE call SetDNSServerSearchOrder ("1.1.1.1")
reg add "HKLMSystemCurrentControlSetServicesNetBTParameters" /v "EnableLMHOSTS" /t REG_DWORD /d "0" /f
wmic nicconfig where TcpipNetbiosOptions=0 call SetTcpipNetbios 2
wmic nicconfig where TcpipNetbiosOptions=1 call SetTcpipNetbios 2
      • Edited by
        TairikuOkami
        Saturday, June 9, 2018 12:08 PM

    • ‘ We don’t test in that configuration’ — very sad.   Maybe misleading.  Inconsistent.   Slightly arrogant.

      It is not just ‘protocols’.   It includes ‘service’ and ‘client’ network features.

      In the past some of these were not uninstallable.   And when you tried to uninstall the button to do so was greyed out.   Now items that in the past were uninstallable are not, the uninstall button does not grey out, and you get a silly
      error message.

      Someone dropped the ball at Microsoft.   Seems to happen a lot.

      Stan

    • Well said, like DNS Cache service for example, which can be disabled only via registry,, ofr now. Disabling it increases security by decreasing the attack surface on the client’s side, like DNS poisoning. DNS malware/attacks are on the rise. I disable it
      plus I use dnscrypt with DNSSEC servers.

      DNS Security

      • Edited by
        TairikuOkami
        Saturday, June 9, 2018 3:43 PM

    • Hi rbcarra,

      Based on my test, yes and I can reproduce your problem.

      It can be uninstalled on previous version, like Windows 10 1709, Windows 10 1607 etc. But when I uninstall it on Windows 10 1803, the result is same as yours:

      And I capture the activity on Windows 10 1709 and Windows 10 1803, nothing can be found:

      I will submit this feedback via our own channel. It’s also recommend you submit it via built-in Feedback app. If any update, I will post here.

      Please remember to mark the replies as answers if they help.
      If you have feedback for TechNet Subscriber Support, contact
      tnmff@microsoft.com.

      Have a look at this kb article — maybe the PowerShell workaround helps.

      1. Press Windows + X and invoke PowerShell console

      2. Enter Get-NetAdapterBinding and press Enter

      This lists all bindings of your network

      3. Enter the following command to remove a binding

      Disable-NetAdapterBinding -Name „Ethernet0“ -ComponentID ms_msclient


      Ethernet0 is the placeholder for your network adapter. Instead of ms_msclient you need to identify the component ID returned by Get-NetAdapterBinding and press Enter. QoS is ms_pacer imho.

      HTP

      Gruß/greetings G. Born — Blogs: http://www.borncity.com/blog (Ger) — http://www.borncity.com/win (EN)

      • Edited by
        Günter BornMVP
        Tuesday, June 26, 2018 1:38 PM
        added the PS commands

    • This is part of some workaround here: https://blog.olandese.nl/2017/05/03/solve-docker-for-windows-error-a-firewall-is-blocking-file-sharing-between-windows-and-the-containers/

      So by breaking existing functionality, you also broke workaround. Not cool.

    • Public KB

      Error 0x80071779 when removing network components in Windows 10, version 1803
      https://support.microsoft.com/en-us/help/4340181/

    • Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V

      Wrong. I’ve uninstalled Hyper-V feature but it didn’t remove neither Hyper-V adapters nor v-switch driver from the OS. I’ve managed to remove NICs manually but can’t uninstall v-switch driver because of this error. There should be some solution to purge
      this garbage from the system.

    • I been a whole week that I’m trying to fix this, I got screwed using this garbage hyper-v that can not be cleaned from my computer, effectively wrecking any chance of using virtual-box. MS should get a damn checklist and work by it instead of half-fixing
      old issues.

    • Also trying to use the Docker workaround. Tried Gunter Born’s approach to disable and then re-enable the binding. Sadly did not work.

    • I have tried many of the above suggestions on Windows 10 Pro and no luck.

      I have tried using the disable-netadapterbinding on the file and print sharing service for the particular network but after that when i tried to install it again it doesn’t show up in the list as a service to pick.

      Also just tried the disable then enable netadapterbinding command and that didn’t work either.

      Any other ideas?

    • Remove From My Forums

    • Question

    • When trying to uninstall protocols from adapter, I get the error below.

      Could not uninstall the Client for Microsoft Networks feature.

      The error is 0x80071779

      I have uninstalled all the adapters, reset winsock…

      I am running Microsoft Windows [Version 10.0.17134.1]

      • Edited by
        rbcarra
        Thursday, April 19, 2018 3:38 AM

    All replies

    • Hi rbcarra,

      Based on my test, yes and I can reproduce your problem.

      It can be uninstalled on previous version, like Windows 10 1709, Windows 10 1607 etc. But when I uninstall it on Windows 10 1803, the result is same as yours:

      And I capture the activity on Windows 10 1709 and Windows 10 1803, nothing can be found:

      I will submit this feedback via our own channel. It’s also recommend you submit it via built-in Feedback app. If any update, I will post here.

      Please remember to mark the replies as answers if they help.
      If you have feedback for TechNet Subscriber Support, contact
      tnmff@microsoft.com.

      • Proposed as answer by
        Karen_HuMicrosoft contingent staff
        Monday, April 23, 2018 8:11 AM

    • Same here. Upgrade or even fresh install of 1803 borks this feature.

    • Hello,

      Why would we need to remove the Client for Microsoft Networks?

      Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

    • It is unspecific to the protocol. You cannot remove any protocol at the moment.

    • Hi rbcarras,

      Try to change the TCP/IP properties in the Registry with the following path:
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL11.SQL2012MSSQLServerSuperSocketNetLibTcp]

      Momominta

      What if i don’t even have this entry?

    • I agree that the message box could be a lot better here.  We’ll look into that for the next release.

      Blocking uninstallation of inbox drivers is by design, however.  We do not support using this UI to remove built-in drivers.  We don’t test in that configuration, and we know that uninstalling drivers breaks things.

      As you’ve probably already noticed, uninstalling a driver from this UI was never permanent.  E.g., if you uninstalled a driver from Windows 7, then upgraded to Windows 8, it would get reinstalled.  Maybe more disconcertingly, a monthly security
      update that affected that particular driver could reinstall it.  The reason is that the OS’s servicing stack isn’t really aware of this UI, and doesn’t realize when this UI is removing drivers.  The OS’s servicing stack will reinstall the driver
      any time the driver is serviced.

      There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or LBFO team. 
      And if you uninstall it, bridges and teams will be permanently broken.  We’ve gotten support requests from quite a few customers who inadvertently damaged their systems by uninstalling drivers, and need help putting it back together.  In Windows
      10 1803, we block attempts to damage the system.

      Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V, WDAG, and Containers optional features.  Optional features
      are indeed supported and we do test the OS with the feature removed.

      If there are specific drivers that you would like to be removable, but which are not currently part of an Optional Feature, please file a feature request in the Feedback Hub.

      Please note that you can always unbind the driver from any/all NICs, either using this GUI or using the PowerShell cmdlet «Disable-NetAdapterBinding».  The only change is that you can’t deregister the OS driver entirely.  But if you unbind
      the driver from all your NICs, it’s effectively the same as uninstalling the driver.

      Also note that 3rd party drivers can still be installed & uninstalled (or bound/unbound) from this GUI.  The change only affects the drivers that are part of the OS.

    • Hello,

      Why would we need to remove the Client for Microsoft Networks?

      Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

      We want remove «Client for Microsoft Networks», LLDP and many others ’cause they are unnecessary to system operation specially on
      public networks and machines that access many unknown networks…

    • Uninstalling all items for my connection but TCP/IPv4 never broke anything for me on a stand alone system.
      You guys force way to much to be installed on Windows pr. default and preventing uninstallation on top is just a silly move.

      Regards Joerg Baermann

      • Proposed as answer by
        krakdcorn
        Sunday, November 18, 2018 6:23 PM

    • You can always unbind these drivers — just uncheck the box next to its name.  Unbinding the driver will 100% prevent it from communicating on that network.

    • We do not support using this UI to remove built-in Drivers.

      Since when ? — You have this UI with the Option to install/remove Protocols, inside Windows for almost 30 Years !!! — Not sure, if it was there in Windows 3.11 but Windows 95 got it… — Even some external Network/Wlan protocols, work with exactly this Panel!
      — Are you sure, you speak for the whole MS-Company, when you say, you just drop the support, for Network Protocol, de-install, re-install, install, cause one update broke it ?

      • Edited by
        Beschwerde
        Sunday, May 13, 2018 7:29 PM

    • There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or
      LBFO team.   …

      Why is this even on the client SKU as NIC teams are not supported on client SKUs ?

    • I recall an advanced Windows NT course where we taught unbinding protocols to a NIC in order to lock down a machine. Part of the Microsoft curriculum taught how to take it a step further and actually uninstall the protocols. This was back in the late 1990’s!
      Given the advancements in technology since then and even greater cyber threats of today, why in the world would Microsoft ever prevent us from uninstalling a protocol if we didn’t want it there? This is a huge problem.

    • A little workaround I did to fix this «little bug». I have services like Server and
      Workstation disabled (plus a few other things), that should take care of the «Client for Microsoft Network» and «File and Printer Sharing». As for the rest, disabling the driver should prevent them from working.

      rem Link-Layer Topology Discovery Responder / Default - 2
reg add "HKLMSystemCurrentControlSetServicesrspndr" /v "Start" /t REG_DWORD /d "4" /f

rem Link-Layer Topology Discovery Mapper I/O Driver / Default - 2
reg add "HKLMSystemCurrentControlSetServiceslltdio" /v "Start" /t REG_DWORD /d "4" /f

rem Microsoft LLDP Protocol Driver / Default - 2
reg add "HKLMSystemCurrentControlSetServicesMsLldp" /v "Start" /t REG_DWORD /d "4" /f

rem Microsoft Virtual Network Adapter Enumerator / Default - 3
reg add "HKLMSystemCurrentControlSetServicesNdisVirtualBus" /v "Start" /t REG_DWORD /d "4" /f

rem QoS for storage I/O traffic / Default - 2
reg add "HKLMSystemCurrentControlSetServicesstorqosflt" /v "Start" /t REG_DWORD /d "4" /f

rem QoS Multimeda Class Scheduler / Default - 2
reg add "HKLMSystemCurrentControlSetServicesMMCSS" /v "Start" /t REG_DWORD /d "4" /f

rem QoS Packet Scheduler / Default - 1
reg add "HKLMSystemCurrentControlSetServicesPsched" /v "Start" /t REG_DWORD /d "4" /f

rem Named pipe service trigger provider / Default - 1
rem https://msdn.microsoft.com/en-us/library/windows/desktop/aa365590(v=vs.85).aspx
reg add "HKLMSystemCurrentControlSetServicesnpsvctrig" /v "Start" /t REG_DWORD /d "4" /f

rem NetBIOS Interface / Default - 1
reg add "HKLMSystemCurrentControlSetServicesNetBIOS" /v "Start" /t REG_DWORD /d "4" /f

rem NetBIOS over TCP/IP / Default - 1
reg add "HKLMSystemCurrentControlSetServicesNetBT" /v "Start" /t REG_DWORD /d "4" /f

rem Remote Desktop Device Redirector Bus Driver / Default - 3
reg add "HKLMSystemCurrentControlSetServicesrdpbus" /v "Start" /t REG_DWORD /d "4" /f

rem The framework for network mini-redirectors / Default - 1
rem https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/the-redirected-drive-buffering-subsystem
reg add "HKLMSystemCurrentControlSetServicesrdbss" /v "Start" /t REG_DWORD /d "4" /f

rem A little bonus - Disable IPv6/LMHOSTS lookup/NetBIOS and Set DNS Servers
netsh int ipv6 isatap set state disabled
netsh int teredo set state disabled
netsh interface ipv6 6to4 set state state=disabled undoonstop=disabled
reg add "HKLMSystemCurrentControlSetServicesTcpip6Parameters" /v "DisabledComponents" /t REG_DWORD /d "255" /f
wmic nicconfig where DHCPEnabled=TRUE call SetDNSServerSearchOrder ("1.1.1.1")
reg add "HKLMSystemCurrentControlSetServicesNetBTParameters" /v "EnableLMHOSTS" /t REG_DWORD /d "0" /f
wmic nicconfig where TcpipNetbiosOptions=0 call SetTcpipNetbios 2
wmic nicconfig where TcpipNetbiosOptions=1 call SetTcpipNetbios 2
      • Edited by
        TairikuOkami
        Saturday, June 9, 2018 12:08 PM

    • ‘ We don’t test in that configuration’ — very sad.   Maybe misleading.  Inconsistent.   Slightly arrogant.

      It is not just ‘protocols’.   It includes ‘service’ and ‘client’ network features.

      In the past some of these were not uninstallable.   And when you tried to uninstall the button to do so was greyed out.   Now items that in the past were uninstallable are not, the uninstall button does not grey out, and you get a silly
      error message.

      Someone dropped the ball at Microsoft.   Seems to happen a lot.

      Stan

    • Well said, like DNS Cache service for example, which can be disabled only via registry,, ofr now. Disabling it increases security by decreasing the attack surface on the client’s side, like DNS poisoning. DNS malware/attacks are on the rise. I disable it
      plus I use dnscrypt with DNSSEC servers.

      DNS Security

      • Edited by
        TairikuOkami
        Saturday, June 9, 2018 3:43 PM

    • Hi rbcarra,

      Based on my test, yes and I can reproduce your problem.

      It can be uninstalled on previous version, like Windows 10 1709, Windows 10 1607 etc. But when I uninstall it on Windows 10 1803, the result is same as yours:

      And I capture the activity on Windows 10 1709 and Windows 10 1803, nothing can be found:

      I will submit this feedback via our own channel. It’s also recommend you submit it via built-in Feedback app. If any update, I will post here.

      Please remember to mark the replies as answers if they help.
      If you have feedback for TechNet Subscriber Support, contact
      tnmff@microsoft.com.

      Have a look at this kb article — maybe the PowerShell workaround helps.

      1. Press Windows + X and invoke PowerShell console

      2. Enter Get-NetAdapterBinding and press Enter

      This lists all bindings of your network

      3. Enter the following command to remove a binding

      Disable-NetAdapterBinding -Name „Ethernet0“ -ComponentID ms_msclient


      Ethernet0 is the placeholder for your network adapter. Instead of ms_msclient you need to identify the component ID returned by Get-NetAdapterBinding and press Enter. QoS is ms_pacer imho.

      HTP

      Gruß/greetings G. Born — Blogs: http://www.borncity.com/blog (Ger) — http://www.borncity.com/win (EN)

      • Edited by
        Günter BornMVP
        Tuesday, June 26, 2018 1:38 PM
        added the PS commands

    • This is part of some workaround here: https://blog.olandese.nl/2017/05/03/solve-docker-for-windows-error-a-firewall-is-blocking-file-sharing-between-windows-and-the-containers/

      So by breaking existing functionality, you also broke workaround. Not cool.

    • Public KB

      Error 0x80071779 when removing network components in Windows 10, version 1803
      https://support.microsoft.com/en-us/help/4340181/

    • Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V

      Wrong. I’ve uninstalled Hyper-V feature but it didn’t remove neither Hyper-V adapters nor v-switch driver from the OS. I’ve managed to remove NICs manually but can’t uninstall v-switch driver because of this error. There should be some solution to purge
      this garbage from the system.

    • I been a whole week that I’m trying to fix this, I got screwed using this garbage hyper-v that can not be cleaned from my computer, effectively wrecking any chance of using virtual-box. MS should get a damn checklist and work by it instead of half-fixing
      old issues.

    • Also trying to use the Docker workaround. Tried Gunter Born’s approach to disable and then re-enable the binding. Sadly did not work.

    • I have tried many of the above suggestions on Windows 10 Pro and no luck.

      I have tried using the disable-netadapterbinding on the file and print sharing service for the particular network but after that when i tried to install it again it doesn’t show up in the list as a service to pick.

      Also just tried the disable then enable netadapterbinding command and that didn’t work either.

      Any other ideas?

    Перейти к контенту

    Ошибка 0x80071779 в Windows 10 обычно встречаются в версии 1803. Обновление Windows 10 апреля 2018 года содержит проблему в сетевых соединениях. Когда пользователи пытаются удалить клиент для сетей Microsoft в свойствах сетевого адаптера, они сталкиваются с кодом ошибки 0x80071779. Давайте разберем, как удалить протокол клиента для сетей Майкрософт. 

    Как исправить ошибку 0x80071779 компонента для сетей в Windows 10

    Когда вы пытаетесь удалить клиент для сетей Microsoft через сетевые свойства, то вам выдаст ошибку 0x80071779. Давайте ниже разберем, как исправить её.Ошибка 0x80071779 в Windows 10

    Для удаления протокола можно использовать PowerShell. 

    channel

    Шаг 1. Нажмите сочетание кнопок Win + X и выберите «Windows PowerShell (администратор)«.

    Шаг 2. Теперь введите ниже команду и нажмите Ввод.

    Get-NetAdapterBinding

    команда Get-NetAdapterBinding

    Шаг 3. Эта команда покажет Вам ваши сетевые адаптеры и клиент для сетей Microsoft (ms_msclient). У вас таже как и у меня могут быть куча подключений, запомните свое основное подключение или то в котором вы хотите удалить клиент для сетей Microsoft. В моем случае это Ethernet.

    Список сетевых адаптеров

    Шаг 4. Чтобы удалить сетевой протокол введите еще одну команду. Замените в команде Ethernet на свое, если у вас другой адаптер. 

    Disable-NetAdapterBinding -Name „Ethernet“ -ComponentID ms_msclient

    Удалить протокол клиента для сетей Microsoft

    Смотрите еще:

    • Как сбросить настройки сети
    • Как изменить имя профиля сети в Windows
    • Не найден сетевой путь ошибка 0x80070035
    • Не удается получить доступ к сайту и найти DNS-адрес сервера
    • Не удается подключиться к WiFi или Локальной сети в Windows 10 

    [ Telegram | Поддержать ]

    • Remove From My Forums

    • Question

    • 1- wireless concoction problem :

      I do update my driver to Dell Inc. Inspiron 5537  Dell Wireless 1705 802.11b/g/n (2.4GHZ)
      but now the signal of wi-fi many time going and some time get 3 sign or 2 sign or 1 sign in signal the wireless connection is not fixed at the same level
      I do everything like reset wifi and reinstall driver but its same problem 

      before I do have original driver but I forget what the name its working great before I update wi-fi driver so what I can do to fixing it or what the original driver for that model  ?

      2- cannot uninstall (Error: 0x80071779)

       I have just updated my PC to the latest build 

      can’t uninstall the Client for Microsoft Networks or other network components. You receive the following error message:

      Could not uninstall the Client for Microsoft Networks feature.

      The error is 0x80071779.

      i read can use  PowerShell cmdlet to remove all but when i do i get same the screenshot and cant uninstall the Client 

      hope to get help thanks

    • Remove From My Forums

    • Question

    • 1- wireless concoction problem :

      I do update my driver to Dell Inc. Inspiron 5537  Dell Wireless 1705 802.11b/g/n (2.4GHZ)
      but now the signal of wi-fi many time going and some time get 3 sign or 2 sign or 1 sign in signal the wireless connection is not fixed at the same level
      I do everything like reset wifi and reinstall driver but its same problem 

      before I do have original driver but I forget what the name its working great before I update wi-fi driver so what I can do to fixing it or what the original driver for that model  ?

      2- cannot uninstall (Error: 0x80071779)

       I have just updated my PC to the latest build 

      can’t uninstall the Client for Microsoft Networks or other network components. You receive the following error message:

      Could not uninstall the Client for Microsoft Networks feature.

      The error is 0x80071779.

      i read can use  PowerShell cmdlet to remove all but when i do i get same the screenshot and cant uninstall the Client 

      hope to get help thanks

    • Remove From My Forums

    • Question

    • 1- wireless concoction problem :

      I do update my driver to Dell Inc. Inspiron 5537  Dell Wireless 1705 802.11b/g/n (2.4GHZ)
      but now the signal of wi-fi many time going and some time get 3 sign or 2 sign or 1 sign in signal the wireless connection is not fixed at the same level
      I do everything like reset wifi and reinstall driver but its same problem 

      before I do have original driver but I forget what the name its working great before I update wi-fi driver so what I can do to fixing it or what the original driver for that model  ?

      2- cannot uninstall (Error: 0x80071779)

       I have just updated my PC to the latest build 

      can’t uninstall the Client for Microsoft Networks or other network components. You receive the following error message:

      Could not uninstall the Client for Microsoft Networks feature.

      The error is 0x80071779.

      i read can use  PowerShell cmdlet to remove all but when i do i get same the screenshot and cant uninstall the Client 

      hope to get help thanks

    • Remove From My Forums

    • Question

    • 1- wireless concoction problem :

      I do update my driver to Dell Inc. Inspiron 5537  Dell Wireless 1705 802.11b/g/n (2.4GHZ)
      but now the signal of wi-fi many time going and some time get 3 sign or 2 sign or 1 sign in signal the wireless connection is not fixed at the same level
      I do everything like reset wifi and reinstall driver but its same problem 

      before I do have original driver but I forget what the name its working great before I update wi-fi driver so what I can do to fixing it or what the original driver for that model  ?

      2- cannot uninstall (Error: 0x80071779)

       I have just updated my PC to the latest build 

      can’t uninstall the Client for Microsoft Networks or other network components. You receive the following error message:

      Could not uninstall the Client for Microsoft Networks feature.

      The error is 0x80071779.

      i read can use  PowerShell cmdlet to remove all but when i do i get same the screenshot and cant uninstall the Client 

      hope to get help thanks

  • Hi,

    This is by design in Windows 10 1803.

    Quote MSFT Jeffrey’s explanation:

    I agree that the message box could be a lot better here.  We’ll look into that for the next release.

    Blocking uninstallation of inbox drivers is by design, however.  We do not support using this UI to remove built-in drivers.  We don’t test in that configuration, and we know that uninstalling drivers breaks things.

    As you’ve probably already noticed, uninstalling a driver from this UI was never permanent.  E.g., if you uninstalled a driver from Windows 7, then upgraded to Windows 8, it would get reinstalled.  Maybe more disconcertingly, a monthly security
    update that affected that particular driver could reinstall it.  The reason is that the OS’s servicing stack isn’t really aware of this UI, and doesn’t realize when this UI is removing drivers.  The OS’s servicing stack will reinstall the driver
    any time the driver is serviced.

    There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or LBFO
    team.  And if you uninstall it, bridges and teams will be permanently broken.  We’ve gotten support requests from quite a few customers who inadvertently damaged their systems by uninstalling drivers, and need help putting it back together. 
    In Windows 10 1803, we block attempts to damage the system.

    Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V, WDAG, and Containers optional features.  Optional features
    are indeed supported and we do test the OS with the feature removed.

    If there are specific drivers that you would like to be removable, but which are not currently part of an Optional Feature, please file a feature request in the Feedback Hub.

    Please note that you can always unbind the driver from any/all NICs, either using this GUI or using the PowerShell cmdlet «Disable-NetAdapterBinding».  The only change is that you can’t deregister the OS driver entirely.  But if you
    unbind the driver from all your NICs, it’s effectively the same as uninstalling the driver.

    Also note that 3rd party drivers can still be installed & uninstalled (or bound/unbound) from this GUI.  The change only affects the drivers that are part of the OS.

    Source thread is here:

    https://social.technet.microsoft.com/Forums/en-US/38e53f34-a607-4368-9d9b-7acba1d32b80/cannot-uninstall-protocols-such-as-client-for-microsoft-networks?forum=win10itpronetworking

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact
    tnmff@microsoft.com.

    • Edited by

      Thursday, May 3, 2018 2:21 AM

    • Marked as answer by
      ONEIGHBOUR
      Friday, May 4, 2018 8:38 AM

    • Источник

    Содержание

    1. Исправить ошибку 0x80071779 в Windows 10
    2. Как исправить ошибку 0x80071779 компонента для сетей в Windows 10
    3. 0x80071779 windows 10 при удалении общего доступа
    4. Answered by:
    5. Question
    6. Answers
    7. Исправлено: ошибка 0x80071771 в Windows 10 —
    8. Что вызывает ошибку 0x80071771?
    9. Способ 1: получение полного разрешения на доступ к файлу
    10. Способ 2: импорт сертификата шифрования файлов EFS + ключ в Windows 10
    11. Экспорт сертификата EFS + ключ
    12. Вариант первый: импорт сертификата шифрования файла EFS и ключа через файл PFX
    13. 0x80071779 windows 10 при удалении общего доступа
    14. Answered by:
    15. Question
    16. Answers
    17. All replies
    18. How to Fix mstscax.dll error and 0x80071779 in Windows 10
    19. How to Fix mstscax.dll error 0x80071779 in Windows 10
    20. Error 0x80071779 in Windows 10
    21. Fix Through PowerShell
    22. mstscax.dll Error in Windows 10

    Исправить ошибку 0x80071779 в Windows 10

    Ошибка 0x80071779 в Windows 10 обычно встречаются в версии 1803. Обновление Windows 10 апреля 2018 года содержит проблему в сетевых соединениях. Когда пользователи пытаются удалить клиент для сетей Microsoft в свойствах сетевого адаптера, они сталкиваются с кодом ошибки 0x80071779. Давайте разберем, как удалить протокол клиента для сетей Майкрософт.

    Как исправить ошибку 0x80071779 компонента для сетей в Windows 10

    Когда вы пытаетесь удалить клиент для сетей Microsoft через сетевые свойства, то вам выдаст ошибку 0x80071779. Давайте ниже разберем, как исправить её. %D0%9E%D1%88%D0%B8%D0%B1%D0%BA%D0%B0 0x80071779 %D0%B2 Windows 10

    Для удаления протокола можно использовать PowerShell.

    Шаг 1. Нажмите сочетание кнопок Win + X и выберите «Windows PowerShell (администратор)«.

    Шаг 2. Теперь введите ниже команду и нажмите Ввод.

    Get-NetAdapterBinding

    %D0%BA%D0%BE%D0%BC%D0%B0%D0%BD%D0%B4%D0%B0 Get NetAdapterBinding

    Шаг 3. Эта команда покажет Вам ваши сетевые адаптеры и клиент для сетей Microsoft (ms_msclient). У вас таже как и у меня могут быть куча подключений, запомните свое основное подключение или то в котором вы хотите удалить клиент для сетей Microsoft. В моем случае это Ethernet.

    %D0%A1%D0%B8%D0%BF%D0%B8%D1%81%D0%BE%D0%BA %D1%81%D0%B5%D1%82%D0%B5%D0%B2%D1%8B%D1%85 %D0%B0%D0%B4%D0%B0%D0%BF%D1%82%D0%B5%D1%80%D0%BE%D0%B2

    Шаг 4. Чтобы удалить сетевой протокол введите еще одну команду. Замените в команде Ethernet на свое, если у вас другой адаптер.

    Источник

    0x80071779 windows 10 при удалении общего доступа

    This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

    trans

    Answered by:

    trans

    Question

    trans

    trans

    I have just updated my PC to the latest build (1803; OS Build 17134.1) to test before we deploy to our staff. As part of our build we uninstall the QoS Packet Scheduler feature from the Network Adapter. Looks like Microsoft has re-installed this as part of upgrading the previous version of Windows 10. When I try to uninstall this from the NIC I get the below error. Anyone else having the same error? Any suggestions on how to uninstall QoS?

    Answers

    trans

    trans

    This is by design in Windows 10 1803.

    Quote MSFT Jeffrey’s explanation:

    I agree that the message box could be a lot better here. We’ll look into that for the next release.

    Blocking uninstallation of inbox drivers is by design, however. We do not support using this UI to remove built-in drivers. We don’t test in that configuration, and we know that uninstalling drivers breaks things.

    As you’ve probably already noticed, uninstalling a driver from this UI was never permanent. E.g., if you uninstalled a driver from Windows 7, then upgraded to Windows 8, it would get reinstalled. Maybe more disconcertingly, a monthly security update that affected that particular driver could reinstall it. The reason is that the OS’s servicing stack isn’t really aware of this UI, and doesn’t realize when this UI is removing drivers. The OS’s servicing stack will reinstall the driver any time the driver is serviced.

    T here’s some advice circulating the Internet to uninstall the «Multiplexor» driver. This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or LBFO team. And if you uninstall it, bridges and teams will be permanently broken. We’ve gotten support requests from quite a few customers who inadvertently damaged their systems by uninstalling drivers, and need help putting it back together. In Windows 10 1803, we block attempts to damage the system.

    Some of the built-in drivers can be uninstalled as part of a larger «optional feature». For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V, WDAG, and Containers optional features. Optional features are indeed supported and we do test the OS with the feature removed.

    If there are specific drivers that you would like to be removable, but which are not currently part of an Optional Feature, please file a feature request in the Feedback Hub.

    Please note that you can always unbind the driver from any/all NICs, either using this GUI or using the PowerShell cmdlet «Disable-NetAdapterBinding». The only change is that you can’t deregister the OS driver entirely. But if you unbind the driver from all your NICs, it’s effectively the same as uninstalling the driver.

    Also note that 3rd party drivers can still be installed & uninstalled (or bound/unbound) from this GUI. The change only affects the drivers that are part of the OS.

    Источник

    Исправлено: ошибка 0x80071771 в Windows 10 —

    Некоторые пользователи получают 0x80071771 ошибка при попытке открыть или обработать файл в Windows 10. Обычно это происходит после того, как пользователь обновился до последней версии Windows со старой версии. Сообщение об ошибке иногда сопровождается сообщением «Указанный файл не может быть расшифрован«.

    ispravleno oshibka 0x80071771 v windows 10 1Ошибка 0x80071771 в Windows 10

    Что вызывает ошибку 0x80071771?

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

    Как выясняется, этот конкретный код ошибки чаще всего встречается, когда пользователь пытается получить доступ к файлу, который был ранее создан и зашифрован на другом компьютере.

    Это конкретное сообщение об ошибке в основном связано с файлами, которые были зашифрованы с Шифрованная файловая система (EFS). Это встроенное в Windows шифрование, которое широко используется для шифрования файлов и папок, чтобы защитить их от нежелательного доступа.

    Эта система шифрования была разработана для предотвращения доступа к вашему компьютеру ваших конфиденциальных данных от угроз или злоумышленников. Дело в том, что после того, как файл зашифрован, требуется сертификат для доступа к нему с другого устройства. Из-за этого зашифрованный файл может быть доступен только на том компьютере, который был зашифрован без каких-либо дополнительных операций.

    Имея это в виду, есть два способа получить доступ к зашифрованному файлу на другом компьютере:

    Если вы в настоящее время ищете способ решить 0x80071771 Ошибка, эта статья предоставит вам несколько шагов по устранению неполадок. Скорее всего, не все описанные ниже методы будут применимы к вашему сценарию.

    В связи с этим мы советуем вам следовать методам в том порядке, в котором они представлены, и игнорировать методы, которые невозможно воспроизвести. В конечном итоге вы должны наткнуться на метод, который решит проблему для вас.

    Способ 1: получение полного разрешения на доступ к файлу

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

    Вам нужно будет выполнить следующие шаги на компьютере, где файл был изначально зашифрован. Заполнив их, вы сможете переместить файл и открыть его на другом компьютере, не сталкиваясь с 0x80071771 ошибка.

    Несколько пострадавших пользователей сообщили, что им удалось разрешить 0x80071771 ошибка, выполнив шаги ниже. Вот что вам нужно сделать:

    После выполнения описанных выше действий ваш компьютер только что получил полные разрешения для доступа к файлу. Затем выполните действия ниже, чтобы использовать командную строку с повышенными правами для расшифровки файла:

    Если вы все еще сталкиваетесь с 0x80071771 Ошибка — «Указанный файл не может быть расшифрован» Проблема при попытке открыть файл, перейдите к следующему способу ниже.

    Способ 2: импорт сертификата шифрования файлов EFS + ключ в Windows 10

    Единственный способ открыть зашифрованный файл (файл EFS) на другом компьютере — это импортировать его вместе с сертификатом и ключом. Любое отдельное приложение, которое не имеет соответствующего ключа шифрования файла, не сможет его открыть.

    Но для того, чтобы этот метод был применим, вам нужно иметь доступ к компьютеру, который использовался для шифрования файла и экспорта ключа + сертификата. Вот краткое руководство о том, как это сделать:

    Экспорт сертификата EFS + ключ

    ispravleno oshibka 0x80071771 v windows 10 12 1Экспорт файла PFX

    Следующие шаги покажут вам, как импортировать файл PFX, который используется для сертификата шифрования файла, и ключ, используемый с EFS, на другом компьютере. Есть два разных метода, которые вы можете использовать для импорта этого сертификата + ключ.

    Оба метода будут работать для любой версии Windows 10, поэтому придерживайтесь того, какой из них более удобен для вашей текущей ситуации:

    Вариант первый: импорт сертификата шифрования файла EFS и ключа через файл PFX

    ispravleno oshibka 0x80071771 v windows 10 13 1Импорт ключа + сертификата через файл PFX

    Источник

    0x80071779 windows 10 при удалении общего доступа

    This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

    trans

    Answered by:

    trans

    Question

    trans

    trans

    I have installations of SQL Server 2012 Express on Windows Server 2008 R2 that pop up this error whenever I try to change anything in the TCP/IP properties in Sql Server Configuration Manager:

    How can I solve this?

    EN

    PT

    Answers

    trans

    trans

    Did you has administrator right on the server? You can also try to change the TCP/IP properties in the Registry with the following path:
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL11.SQL2012MSSQLServerSuperSocketNetLibTcp]

    Fanny Liu
    TechNet Community Support

    signature

    trans

    trans

    worthwhile going through the link. check comments from ROB he finally get it working with sql express.

    trans

    trans

    I’m failing to see what the solution was or in what way is that post related to the problem I’m having.

    EN

    PT

    trans

    trans

    Did you has administrator right on the server? You can also try to change the TCP/IP properties in the Registry with the following path:
    [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL11.SQL2012MSSQLServerSuperSocketNetLibTcp]

    Fanny Liu
    TechNet Community Support

    signature

    trans

    trans

    I do have administrator rights and I’m using the same account that installed the SQL Server instance.

    I was able to change the settings directly in the registry and now I can change it on the Sql Server Management Console.

    I wonder whatever happened.

    EN

    PT

    trans

    trans

    I’ve hit this problem before in the past when I have multiple versions of SQL Server installed on the same machine.

    trans

    trans

    trans

    trans

    Just here to report that I’m experiencing the same issue ever since SQL Server 2014. Clean Operating System and default installation via Win Authentication always results in having this issue. I’ve been applying this «registry hack», how I like to call it, for 3 years now.

    I’m thinking this is a service permission problem. The default installation routine creates a bunch of users and roles for SQL server. And despite logging in as system administrator, the permissions are still not enough to fiddle with the TCP/IP settings.

    Obviously giving such a generic message for a failed HRESULT like » The specified file is read only. [0x80071779] » for such a common error is careless and a very poor example of error reporting to say the least.

    Just dropping another hopeless reply / reminder here as none of the answers above are able to get anywhere near fixing that issue.

    Источник

    How to Fix mstscax.dll error and 0x80071779 in Windows 10

    mstscax.dll error and 0x80071779 in Windows 10 usually occur in version 1803. The Windows 10 April 2018 Update contains several problems in network and RDP connections. It appears that there is no NIC adapter binding for the network that can be uninstalled through GUI. However, you can get rid of mstscax.dll error and 0x80071779 in Windows 10 pretty easily.

    When users make an attempt to uninstall the client for Microsoft networks in the properties of a network adapter, they come across an Error Code 0x80071779. Whereas mstscax.dll message may show while using Remote Desktop Protocol for remote connections in Windows 10. However, Microsoft mentioned mstscax.dll error and 0x80071779 problems in KB articles along with their solutions.

    How to Fix mstscax.dll error 0x80071779 in Windows 10

    Error 0x80071779 in Windows 10

    When the administrator of Windows 10 version 1803 based device tries to uninstall the client for Microsoft networks through the network properties, they come across this specific issue. Probably a few numbers of users may need to perform this uninstallation in order to remove Microsoft networks.

    How to Fix mstscax.dll error and 0x80071779 in Windows 10 Pic 1 e1530452394795

    Fix Through PowerShell

    You can use the PowerShell cmdlet Disable-NetAdapterBinding to dispel the protocol. Here is the procedure –

    Step-1: Make a joint press of Win+X in order to open Power user menu.

    Step-2: Select “Windows PowerShell (Admin)” from the visible list and when a UAC appears, do a click on Yes to continue.

    Step-3: Now type in the following command after the blinking cursor and then hit Enter.

    How to Fix mstscax.dll error and 0x80071779 in Windows 10 Pic 2

    This command will list all adapter bindings where ms_msclient specifies Microsoft client and ms_pacer addresses the QoS packet planner.

    Step-4: Moving ahead, type the below-given command in PowerShell and press Enter in order to delete a network protocol.

    Note- To complete the process perfectly make sure you have put your Network name in the place of Ethernet0.

    mstscax.dll Error in Windows 10

    As mentioned above, this error shows up while using Remote Desktop Protocol (in short RDP) for remote connections in Windows 10. This error also seems to appear after the installation of an update such as KB4284835.

    Furthermore, this problem comes up on PCs where mstsc.exe and mstxcax.dll files were replaced with a previous version of these files. Replacing them from earlier versions of the OS fails to support and thus lead to an unexpected behavior. And as a result, when users make an attempt to install future updates (KB4284835), file mismatch error occurs.

    Hence, to resolve it, go through the below-given sequence of steps.

    Step-1: At first, take ownership of your PC. And then provide full authorization to mstscax.dll and mstsc.exe files respectively.

    Step-2: Uninstall the update that is causing this issue which is probably KB4284835.

    Step-3: Processing forward, restore original Windows 10 files (mstsc.exe and mstscax.dll) to the following folder.

    Step-4: After successfully restoring the files, restart Windows 10 PC.

    Step-5: Next, Reinstall the update again.

    Step-6: Finally, again Reboot your computer once again in order to finish the process.

    That’s all. Hopefully, you have resolved the issue already. If you have any question, don’t hesitate to ask.

    Источник

    Источник

    RRS feed

    • Remove From My Forums

    • Question

    • When trying to uninstall protocols from adapter, I get the error below.

      Could not uninstall the Client for Microsoft Networks feature.

      The error is 0x80071779

      I have uninstalled all the adapters, reset winsock…

      I am running Microsoft Windows [Version 10.0.17134.1]

      • Edited by
        rbcarra
        Thursday, April 19, 2018 3:38 AM

    All replies

    • Hi rbcarra,

      Based on my test, yes and I can reproduce your problem.

      It can be uninstalled on previous version, like Windows 10 1709, Windows 10 1607 etc. But when I uninstall it on Windows 10 1803, the result is same as yours:

      And I capture the activity on Windows 10 1709 and Windows 10 1803, nothing can be found:

      I will submit this feedback via our own channel. It’s also recommend you submit it via built-in Feedback app. If any update, I will post here.

      Please remember to mark the replies as answers if they help.
      If you have feedback for TechNet Subscriber Support, contact
      tnmff@microsoft.com.

      • Proposed as answer by
        Karen_HuMicrosoft contingent staff
        Monday, April 23, 2018 8:11 AM

    • Same here. Upgrade or even fresh install of 1803 borks this feature.

    • Hello,

      Why would we need to remove the Client for Microsoft Networks?

      Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

    • It is unspecific to the protocol. You cannot remove any protocol at the moment.

    • Hi rbcarras,

      Try to change the TCP/IP properties in the Registry with the following path:
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL11.SQL2012MSSQLServerSuperSocketNetLibTcp]

      Momominta

      What if i don’t even have this entry?

    • I agree that the message box could be a lot better here.  We’ll look into that for the next release.

      Blocking uninstallation of inbox drivers is by design, however.  We do not support using this UI to remove built-in drivers.  We don’t test in that configuration, and we know that uninstalling drivers breaks things.

      As you’ve probably already noticed, uninstalling a driver from this UI was never permanent.  E.g., if you uninstalled a driver from Windows 7, then upgraded to Windows 8, it would get reinstalled.  Maybe more disconcertingly, a monthly security
      update that affected that particular driver could reinstall it.  The reason is that the OS’s servicing stack isn’t really aware of this UI, and doesn’t realize when this UI is removing drivers.  The OS’s servicing stack will reinstall the driver
      any time the driver is serviced.

      There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or LBFO team. 
      And if you uninstall it, bridges and teams will be permanently broken.  We’ve gotten support requests from quite a few customers who inadvertently damaged their systems by uninstalling drivers, and need help putting it back together.  In Windows
      10 1803, we block attempts to damage the system.

      Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V, WDAG, and Containers optional features.  Optional features
      are indeed supported and we do test the OS with the feature removed.

      If there are specific drivers that you would like to be removable, but which are not currently part of an Optional Feature, please file a feature request in the Feedback Hub.

      Please note that you can always unbind the driver from any/all NICs, either using this GUI or using the PowerShell cmdlet «Disable-NetAdapterBinding».  The only change is that you can’t deregister the OS driver entirely.  But if you unbind
      the driver from all your NICs, it’s effectively the same as uninstalling the driver.

      Also note that 3rd party drivers can still be installed & uninstalled (or bound/unbound) from this GUI.  The change only affects the drivers that are part of the OS.

    • Hello,

      Why would we need to remove the Client for Microsoft Networks?

      Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

      We want remove «Client for Microsoft Networks», LLDP and many others ’cause they are unnecessary to system operation specially on
      public networks and machines that access many unknown networks…

    • Uninstalling all items for my connection but TCP/IPv4 never broke anything for me on a stand alone system.
      You guys force way to much to be installed on Windows pr. default and preventing uninstallation on top is just a silly move.

      Regards Joerg Baermann

      • Proposed as answer by
        krakdcorn
        Sunday, November 18, 2018 6:23 PM

    • You can always unbind these drivers — just uncheck the box next to its name.  Unbinding the driver will 100% prevent it from communicating on that network.

    • We do not support using this UI to remove built-in Drivers.

      Since when ? — You have this UI with the Option to install/remove Protocols, inside Windows for almost 30 Years !!! — Not sure, if it was there in Windows 3.11 but Windows 95 got it… — Even some external Network/Wlan protocols, work with exactly this Panel!
      — Are you sure, you speak for the whole MS-Company, when you say, you just drop the support, for Network Protocol, de-install, re-install, install, cause one update broke it ?

      • Edited by
        Beschwerde
        Sunday, May 13, 2018 7:29 PM

    • There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or
      LBFO team.   …

      Why is this even on the client SKU as NIC teams are not supported on client SKUs ?

    • I recall an advanced Windows NT course where we taught unbinding protocols to a NIC in order to lock down a machine. Part of the Microsoft curriculum taught how to take it a step further and actually uninstall the protocols. This was back in the late 1990’s!
      Given the advancements in technology since then and even greater cyber threats of today, why in the world would Microsoft ever prevent us from uninstalling a protocol if we didn’t want it there? This is a huge problem.

    • A little workaround I did to fix this «little bug». I have services like Server and
      Workstation disabled (plus a few other things), that should take care of the «Client for Microsoft Network» and «File and Printer Sharing». As for the rest, disabling the driver should prevent them from working.

      rem Link-Layer Topology Discovery Responder / Default - 2
reg add "HKLMSystemCurrentControlSetServicesrspndr" /v "Start" /t REG_DWORD /d "4" /f

rem Link-Layer Topology Discovery Mapper I/O Driver / Default - 2
reg add "HKLMSystemCurrentControlSetServiceslltdio" /v "Start" /t REG_DWORD /d "4" /f

rem Microsoft LLDP Protocol Driver / Default - 2
reg add "HKLMSystemCurrentControlSetServicesMsLldp" /v "Start" /t REG_DWORD /d "4" /f

rem Microsoft Virtual Network Adapter Enumerator / Default - 3
reg add "HKLMSystemCurrentControlSetServicesNdisVirtualBus" /v "Start" /t REG_DWORD /d "4" /f

rem QoS for storage I/O traffic / Default - 2
reg add "HKLMSystemCurrentControlSetServicesstorqosflt" /v "Start" /t REG_DWORD /d "4" /f

rem QoS Multimeda Class Scheduler / Default - 2
reg add "HKLMSystemCurrentControlSetServicesMMCSS" /v "Start" /t REG_DWORD /d "4" /f

rem QoS Packet Scheduler / Default - 1
reg add "HKLMSystemCurrentControlSetServicesPsched" /v "Start" /t REG_DWORD /d "4" /f

rem Named pipe service trigger provider / Default - 1
rem https://msdn.microsoft.com/en-us/library/windows/desktop/aa365590(v=vs.85).aspx
reg add "HKLMSystemCurrentControlSetServicesnpsvctrig" /v "Start" /t REG_DWORD /d "4" /f

rem NetBIOS Interface / Default - 1
reg add "HKLMSystemCurrentControlSetServicesNetBIOS" /v "Start" /t REG_DWORD /d "4" /f

rem NetBIOS over TCP/IP / Default - 1
reg add "HKLMSystemCurrentControlSetServicesNetBT" /v "Start" /t REG_DWORD /d "4" /f

rem Remote Desktop Device Redirector Bus Driver / Default - 3
reg add "HKLMSystemCurrentControlSetServicesrdpbus" /v "Start" /t REG_DWORD /d "4" /f

rem The framework for network mini-redirectors / Default - 1
rem https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/the-redirected-drive-buffering-subsystem
reg add "HKLMSystemCurrentControlSetServicesrdbss" /v "Start" /t REG_DWORD /d "4" /f

rem A little bonus - Disable IPv6/LMHOSTS lookup/NetBIOS and Set DNS Servers
netsh int ipv6 isatap set state disabled
netsh int teredo set state disabled
netsh interface ipv6 6to4 set state state=disabled undoonstop=disabled
reg add "HKLMSystemCurrentControlSetServicesTcpip6Parameters" /v "DisabledComponents" /t REG_DWORD /d "255" /f
wmic nicconfig where DHCPEnabled=TRUE call SetDNSServerSearchOrder ("1.1.1.1")
reg add "HKLMSystemCurrentControlSetServicesNetBTParameters" /v "EnableLMHOSTS" /t REG_DWORD /d "0" /f
wmic nicconfig where TcpipNetbiosOptions=0 call SetTcpipNetbios 2
wmic nicconfig where TcpipNetbiosOptions=1 call SetTcpipNetbios 2

      • Edited by
        TairikuOkami
        Saturday, June 9, 2018 12:08 PM

    • ‘ We don’t test in that configuration’ — very sad.   Maybe misleading.  Inconsistent.   Slightly arrogant.

      It is not just ‘protocols’.   It includes ‘service’ and ‘client’ network features.

      In the past some of these were not uninstallable.   And when you tried to uninstall the button to do so was greyed out.   Now items that in the past were uninstallable are not, the uninstall button does not grey out, and you get a silly
      error message.

      Someone dropped the ball at Microsoft.   Seems to happen a lot.

      Stan

    • Well said, like DNS Cache service for example, which can be disabled only via registry,, ofr now. Disabling it increases security by decreasing the attack surface on the client’s side, like DNS poisoning. DNS malware/attacks are on the rise. I disable it
      plus I use dnscrypt with DNSSEC servers.

      DNS Security

      • Edited by
        TairikuOkami
        Saturday, June 9, 2018 3:43 PM

    • Hi rbcarra,

      Based on my test, yes and I can reproduce your problem.

      It can be uninstalled on previous version, like Windows 10 1709, Windows 10 1607 etc. But when I uninstall it on Windows 10 1803, the result is same as yours:

      And I capture the activity on Windows 10 1709 and Windows 10 1803, nothing can be found:

      I will submit this feedback via our own channel. It’s also recommend you submit it via built-in Feedback app. If any update, I will post here.

      Please remember to mark the replies as answers if they help.
      If you have feedback for TechNet Subscriber Support, contact
      tnmff@microsoft.com.

      Have a look at this kb article — maybe the PowerShell workaround helps.

      1. Press Windows + X and invoke PowerShell console

      2. Enter Get-NetAdapterBinding and press Enter

      This lists all bindings of your network

      3. Enter the following command to remove a binding

      Disable-NetAdapterBinding -Name „Ethernet0“ -ComponentID ms_msclient


      Ethernet0 is the placeholder for your network adapter. Instead of ms_msclient you need to identify the component ID returned by Get-NetAdapterBinding and press Enter. QoS is ms_pacer imho.

      HTP

      Gruß/greetings G. Born — Blogs: http://www.borncity.com/blog (Ger) — http://www.borncity.com/win (EN)

      • Edited by
        Günter BornMVP
        Tuesday, June 26, 2018 1:38 PM
        added the PS commands

    • This is part of some workaround here: https://blog.olandese.nl/2017/05/03/solve-docker-for-windows-error-a-firewall-is-blocking-file-sharing-between-windows-and-the-containers/

      So by breaking existing functionality, you also broke workaround. Not cool.

    • Public KB

      Error 0x80071779 when removing network components in Windows 10, version 1803
      https://support.microsoft.com/en-us/help/4340181/

    • Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V

      Wrong. I’ve uninstalled Hyper-V feature but it didn’t remove neither Hyper-V adapters nor v-switch driver from the OS. I’ve managed to remove NICs manually but can’t uninstall v-switch driver because of this error. There should be some solution to purge
      this garbage from the system.

    • I been a whole week that I’m trying to fix this, I got screwed using this garbage hyper-v that can not be cleaned from my computer, effectively wrecking any chance of using virtual-box. MS should get a damn checklist and work by it instead of half-fixing
      old issues.

    • Also trying to use the Docker workaround. Tried Gunter Born’s approach to disable and then re-enable the binding. Sadly did not work.

    • I have tried many of the above suggestions on Windows 10 Pro and no luck.

      I have tried using the disable-netadapterbinding on the file and print sharing service for the particular network but after that when i tried to install it again it doesn’t show up in the list as a service to pick.

      Also just tried the disable then enable netadapterbinding command and that didn’t work either.

      Any other ideas?

    Источник

    RRS feed

    • Remove From My Forums

    • Question

    • When trying to uninstall protocols from adapter, I get the error below.

      Could not uninstall the Client for Microsoft Networks feature.

      The error is 0x80071779

      I have uninstalled all the adapters, reset winsock…

      I am running Microsoft Windows [Version 10.0.17134.1]

      • Edited by
        rbcarra
        Thursday, April 19, 2018 3:38 AM

    All replies

    • Hi rbcarra,

      Based on my test, yes and I can reproduce your problem.

      It can be uninstalled on previous version, like Windows 10 1709, Windows 10 1607 etc. But when I uninstall it on Windows 10 1803, the result is same as yours:

      And I capture the activity on Windows 10 1709 and Windows 10 1803, nothing can be found:

      I will submit this feedback via our own channel. It’s also recommend you submit it via built-in Feedback app. If any update, I will post here.

      Please remember to mark the replies as answers if they help.
      If you have feedback for TechNet Subscriber Support, contact
      tnmff@microsoft.com.

      • Proposed as answer by
        Karen_HuMicrosoft contingent staff
        Monday, April 23, 2018 8:11 AM

    • Same here. Upgrade or even fresh install of 1803 borks this feature.

    • Hello,

      Why would we need to remove the Client for Microsoft Networks?

      Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

    • It is unspecific to the protocol. You cannot remove any protocol at the moment.

    • Hi rbcarras,

      Try to change the TCP/IP properties in the Registry with the following path:
      [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL11.SQL2012MSSQLServerSuperSocketNetLibTcp]

      Momominta

      What if i don’t even have this entry?

    • I agree that the message box could be a lot better here.  We’ll look into that for the next release.

      Blocking uninstallation of inbox drivers is by design, however.  We do not support using this UI to remove built-in drivers.  We don’t test in that configuration, and we know that uninstalling drivers breaks things.

      As you’ve probably already noticed, uninstalling a driver from this UI was never permanent.  E.g., if you uninstalled a driver from Windows 7, then upgraded to Windows 8, it would get reinstalled.  Maybe more disconcertingly, a monthly security
      update that affected that particular driver could reinstall it.  The reason is that the OS’s servicing stack isn’t really aware of this UI, and doesn’t realize when this UI is removing drivers.  The OS’s servicing stack will reinstall the driver
      any time the driver is serviced.

      There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or LBFO team. 
      And if you uninstall it, bridges and teams will be permanently broken.  We’ve gotten support requests from quite a few customers who inadvertently damaged their systems by uninstalling drivers, and need help putting it back together.  In Windows
      10 1803, we block attempts to damage the system.

      Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V, WDAG, and Containers optional features.  Optional features
      are indeed supported and we do test the OS with the feature removed.

      If there are specific drivers that you would like to be removable, but which are not currently part of an Optional Feature, please file a feature request in the Feedback Hub.

      Please note that you can always unbind the driver from any/all NICs, either using this GUI or using the PowerShell cmdlet «Disable-NetAdapterBinding».  The only change is that you can’t deregister the OS driver entirely.  But if you unbind
      the driver from all your NICs, it’s effectively the same as uninstalling the driver.

      Also note that 3rd party drivers can still be installed & uninstalled (or bound/unbound) from this GUI.  The change only affects the drivers that are part of the OS.

    • Hello,

      Why would we need to remove the Client for Microsoft Networks?

      Thanks, Darrell Gorter [MSFT] This posting is provided «AS IS» with no warranties, and confers no rights.

      We want remove «Client for Microsoft Networks», LLDP and many others ’cause they are unnecessary to system operation specially on
      public networks and machines that access many unknown networks…

    • Uninstalling all items for my connection but TCP/IPv4 never broke anything for me on a stand alone system.
      You guys force way to much to be installed on Windows pr. default and preventing uninstallation on top is just a silly move.

      Regards Joerg Baermann

      • Proposed as answer by
        krakdcorn
        Sunday, November 18, 2018 6:23 PM

    • You can always unbind these drivers — just uncheck the box next to its name.  Unbinding the driver will 100% prevent it from communicating on that network.

    • We do not support using this UI to remove built-in Drivers.

      Since when ? — You have this UI with the Option to install/remove Protocols, inside Windows for almost 30 Years !!! — Not sure, if it was there in Windows 3.11 but Windows 95 got it… — Even some external Network/Wlan protocols, work with exactly this Panel!
      — Are you sure, you speak for the whole MS-Company, when you say, you just drop the support, for Network Protocol, de-install, re-install, install, cause one update broke it ?

      • Edited by
        Beschwerde
        Sunday, May 13, 2018 7:29 PM

    • There’s some advice circulating the Internet to uninstall the «Multiplexor» driver.  This is bad advice: it buys you nothing, since the multiplexor doesn’t even get loaded in memory unless you need it for a bridge or
      LBFO team.   …

      Why is this even on the client SKU as NIC teams are not supported on client SKUs ?

    • I recall an advanced Windows NT course where we taught unbinding protocols to a NIC in order to lock down a machine. Part of the Microsoft curriculum taught how to take it a step further and actually uninstall the protocols. This was back in the late 1990’s!
      Given the advancements in technology since then and even greater cyber threats of today, why in the world would Microsoft ever prevent us from uninstalling a protocol if we didn’t want it there? This is a huge problem.

    • A little workaround I did to fix this «little bug». I have services like Server and
      Workstation disabled (plus a few other things), that should take care of the «Client for Microsoft Network» and «File and Printer Sharing». As for the rest, disabling the driver should prevent them from working.

      rem Link-Layer Topology Discovery Responder / Default - 2
reg add "HKLMSystemCurrentControlSetServicesrspndr" /v "Start" /t REG_DWORD /d "4" /f

rem Link-Layer Topology Discovery Mapper I/O Driver / Default - 2
reg add "HKLMSystemCurrentControlSetServiceslltdio" /v "Start" /t REG_DWORD /d "4" /f

rem Microsoft LLDP Protocol Driver / Default - 2
reg add "HKLMSystemCurrentControlSetServicesMsLldp" /v "Start" /t REG_DWORD /d "4" /f

rem Microsoft Virtual Network Adapter Enumerator / Default - 3
reg add "HKLMSystemCurrentControlSetServicesNdisVirtualBus" /v "Start" /t REG_DWORD /d "4" /f

rem QoS for storage I/O traffic / Default - 2
reg add "HKLMSystemCurrentControlSetServicesstorqosflt" /v "Start" /t REG_DWORD /d "4" /f

rem QoS Multimeda Class Scheduler / Default - 2
reg add "HKLMSystemCurrentControlSetServicesMMCSS" /v "Start" /t REG_DWORD /d "4" /f

rem QoS Packet Scheduler / Default - 1
reg add "HKLMSystemCurrentControlSetServicesPsched" /v "Start" /t REG_DWORD /d "4" /f

rem Named pipe service trigger provider / Default - 1
rem https://msdn.microsoft.com/en-us/library/windows/desktop/aa365590(v=vs.85).aspx
reg add "HKLMSystemCurrentControlSetServicesnpsvctrig" /v "Start" /t REG_DWORD /d "4" /f

rem NetBIOS Interface / Default - 1
reg add "HKLMSystemCurrentControlSetServicesNetBIOS" /v "Start" /t REG_DWORD /d "4" /f

rem NetBIOS over TCP/IP / Default - 1
reg add "HKLMSystemCurrentControlSetServicesNetBT" /v "Start" /t REG_DWORD /d "4" /f

rem Remote Desktop Device Redirector Bus Driver / Default - 3
reg add "HKLMSystemCurrentControlSetServicesrdpbus" /v "Start" /t REG_DWORD /d "4" /f

rem The framework for network mini-redirectors / Default - 1
rem https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/the-redirected-drive-buffering-subsystem
reg add "HKLMSystemCurrentControlSetServicesrdbss" /v "Start" /t REG_DWORD /d "4" /f

rem A little bonus - Disable IPv6/LMHOSTS lookup/NetBIOS and Set DNS Servers
netsh int ipv6 isatap set state disabled
netsh int teredo set state disabled
netsh interface ipv6 6to4 set state state=disabled undoonstop=disabled
reg add "HKLMSystemCurrentControlSetServicesTcpip6Parameters" /v "DisabledComponents" /t REG_DWORD /d "255" /f
wmic nicconfig where DHCPEnabled=TRUE call SetDNSServerSearchOrder ("1.1.1.1")
reg add "HKLMSystemCurrentControlSetServicesNetBTParameters" /v "EnableLMHOSTS" /t REG_DWORD /d "0" /f
wmic nicconfig where TcpipNetbiosOptions=0 call SetTcpipNetbios 2
wmic nicconfig where TcpipNetbiosOptions=1 call SetTcpipNetbios 2

      • Edited by
        TairikuOkami
        Saturday, June 9, 2018 12:08 PM

    • ‘ We don’t test in that configuration’ — very sad.   Maybe misleading.  Inconsistent.   Slightly arrogant.

      It is not just ‘protocols’.   It includes ‘service’ and ‘client’ network features.

      In the past some of these were not uninstallable.   And when you tried to uninstall the button to do so was greyed out.   Now items that in the past were uninstallable are not, the uninstall button does not grey out, and you get a silly
      error message.

      Someone dropped the ball at Microsoft.   Seems to happen a lot.

      Stan

    • Well said, like DNS Cache service for example, which can be disabled only via registry,, ofr now. Disabling it increases security by decreasing the attack surface on the client’s side, like DNS poisoning. DNS malware/attacks are on the rise. I disable it
      plus I use dnscrypt with DNSSEC servers.

      DNS Security

      • Edited by
        TairikuOkami
        Saturday, June 9, 2018 3:43 PM

    • Hi rbcarra,

      Based on my test, yes and I can reproduce your problem.

      It can be uninstalled on previous version, like Windows 10 1709, Windows 10 1607 etc. But when I uninstall it on Windows 10 1803, the result is same as yours:

      And I capture the activity on Windows 10 1709 and Windows 10 1803, nothing can be found:

      I will submit this feedback via our own channel. It’s also recommend you submit it via built-in Feedback app. If any update, I will post here.

      Please remember to mark the replies as answers if they help.
      If you have feedback for TechNet Subscriber Support, contact
      tnmff@microsoft.com.

      Have a look at this kb article — maybe the PowerShell workaround helps.

      1. Press Windows + X and invoke PowerShell console

      2. Enter Get-NetAdapterBinding and press Enter

      This lists all bindings of your network

      3. Enter the following command to remove a binding

      Disable-NetAdapterBinding -Name „Ethernet0“ -ComponentID ms_msclient


      Ethernet0 is the placeholder for your network adapter. Instead of ms_msclient you need to identify the component ID returned by Get-NetAdapterBinding and press Enter. QoS is ms_pacer imho.

      HTP

      Gruß/greetings G. Born — Blogs: http://www.borncity.com/blog (Ger) — http://www.borncity.com/win (EN)

      • Edited by
        Günter BornMVP
        Tuesday, June 26, 2018 1:38 PM
        added the PS commands

    • This is part of some workaround here: https://blog.olandese.nl/2017/05/03/solve-docker-for-windows-error-a-firewall-is-blocking-file-sharing-between-windows-and-the-containers/

      So by breaking existing functionality, you also broke workaround. Not cool.

    • Public KB

      Error 0x80071779 when removing network components in Windows 10, version 1803
      https://support.microsoft.com/en-us/help/4340181/

    • Some of the built-in drivers can be uninstalled as part of a larger «optional feature».  For example, you can get rid of the Virtual Switch driver by uninstalling the Hyper-V

      Wrong. I’ve uninstalled Hyper-V feature but it didn’t remove neither Hyper-V adapters nor v-switch driver from the OS. I’ve managed to remove NICs manually but can’t uninstall v-switch driver because of this error. There should be some solution to purge
      this garbage from the system.

    • I been a whole week that I’m trying to fix this, I got screwed using this garbage hyper-v that can not be cleaned from my computer, effectively wrecking any chance of using virtual-box. MS should get a damn checklist and work by it instead of half-fixing
      old issues.

    • Also trying to use the Docker workaround. Tried Gunter Born’s approach to disable and then re-enable the binding. Sadly did not work.

    • I have tried many of the above suggestions on Windows 10 Pro and no luck.

      I have tried using the disable-netadapterbinding on the file and print sharing service for the particular network but after that when i tried to install it again it doesn’t show up in the list as a service to pick.

      Also just tried the disable then enable netadapterbinding command and that didn’t work either.

      Any other ideas?

    Источник

    Error 0x80071779 in Windows 10 is usually found in version 1803. Windows contains a problem with network connections. For users of the network adapter, they are faced with the error code 0x80071779. For Microsoft networks.

    How To Fix Component Error 0x80071779 For Networks In Windows 10

    You will receive an error 0x80071779. Let’s see it below.

    Related :

    HOW TO FIX ERROR 0X80070017 IN WINDOWS 10

    You can use PowerShell to remove the protocol.

    Step 1. Click the Win + X key combination and select “Windows PowerShell (Administrator)”.

    Step 2. Now enter the command below and press Enter.

    Get-NetAdapterBinding

    the error 0x80071779 in Windows 10

    Step 3. This command will show you your network adapters and client for Microsoft networks (ms_msclient). You have the same as I may have a lot of connections, remember your main connection or the one in which you want to uninstall the client for Microsoft networks. In my case, this is Ethernet0.

    Step 4. To remove the network protocol, enter another command. Replace the Ethernet command with your own if you have a different adapter.

    Disable-NetAdapterBinding -Name “Ethernet” -ComponentID ms_msclient


    Back to top button

    Источник

    Понравилась статья? Поделить с друзьями:
  • Не удалось удалить код ошибки 0x80073cf6
  • Не удалось произвести проверочный звук windows 10 ошибка
  • Не удалось удалить выбранный раздел ошибка 0x8007045d
  • Не удалось произвести оплату код ошибки 220
  • Не удалось удалить выбранный раздел ошибка 0x80042405