Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 19, 2018 3:35 AM | 3 votes
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]
All replies (22)
Friday, April 20, 2018 3:09 AM | 6 votes
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 [email protected].
Tuesday, May 1, 2018 4:18 PM | 1 vote
Same here. Upgrade or even fresh install of 1803 borks this feature.
Tuesday, May 1, 2018 8:51 PM
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.
Tuesday, May 1, 2018 9:16 PM | 1 vote
It is unspecific to the protocol. You cannot remove any protocol at the moment.
Wednesday, May 2, 2018 3:38 PM
Hi rbcarras,
Try to change the TCP/IP properties in the Registry with the following path:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.SQL2012\MSSQLServer\SuperSocketNetLib\Tcp]Momominta
What if i don't even have this entry?
Wednesday, May 2, 2018 6:47 PM
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.
Thursday, May 3, 2018 12:03 AM | 1 vote
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...
Thursday, May 3, 2018 7:48 PM | 3 votes
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
Monday, May 7, 2018 9:33 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.
Sunday, May 13, 2018 7:29 PM | 1 vote
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 ?
Sunday, May 13, 2018 8:08 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 ?
Monday, May 28, 2018 10:16 PM | 2 votes
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.
Saturday, June 9, 2018 12:08 PM
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 "HKLM\System\CurrentControlSet\Services\rspndr" /v "Start" /t REG_DWORD /d "4" /f
rem Link-Layer Topology Discovery Mapper I/O Driver / Default - 2
reg add "HKLM\System\CurrentControlSet\Services\lltdio" /v "Start" /t REG_DWORD /d "4" /f
rem Microsoft LLDP Protocol Driver / Default - 2
reg add "HKLM\System\CurrentControlSet\Services\MsLldp" /v "Start" /t REG_DWORD /d "4" /f
rem Microsoft Virtual Network Adapter Enumerator / Default - 3
reg add "HKLM\System\CurrentControlSet\Services\NdisVirtualBus" /v "Start" /t REG_DWORD /d "4" /f
rem QoS for storage I/O traffic / Default - 2
reg add "HKLM\System\CurrentControlSet\Services\storqosflt" /v "Start" /t REG_DWORD /d "4" /f
rem QoS Multimeda Class Scheduler / Default - 2
reg add "HKLM\System\CurrentControlSet\Services\MMCSS" /v "Start" /t REG_DWORD /d "4" /f
rem QoS Packet Scheduler / Default - 1
reg add "HKLM\System\CurrentControlSet\Services\Psched" /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 "HKLM\System\CurrentControlSet\Services\npsvctrig" /v "Start" /t REG_DWORD /d "4" /f
rem NetBIOS Interface / Default - 1
reg add "HKLM\System\CurrentControlSet\Services\NetBIOS" /v "Start" /t REG_DWORD /d "4" /f
rem NetBIOS over TCP/IP / Default - 1
reg add "HKLM\System\CurrentControlSet\Services\NetBT" /v "Start" /t REG_DWORD /d "4" /f
rem Remote Desktop Device Redirector Bus Driver / Default - 3
reg add "HKLM\System\CurrentControlSet\Services\rdpbus" /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 "HKLM\System\CurrentControlSet\Services\rdbss" /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 "HKLM\System\CurrentControlSet\Services\Tcpip6\Parameters" /v "DisabledComponents" /t REG_DWORD /d "255" /f
wmic nicconfig where DHCPEnabled=TRUE call SetDNSServerSearchOrder ("1.1.1.1")
reg add "HKLM\System\CurrentControlSet\Services\NetBT\Parameters" /v "EnableLMHOSTS" /t REG_DWORD /d "0" /f
wmic nicconfig where TcpipNetbiosOptions=0 call SetTcpipNetbios 2
wmic nicconfig where TcpipNetbiosOptions=1 call SetTcpipNetbios 2
Saturday, June 9, 2018 2:59 PM | 2 votes
' 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
Saturday, June 9, 2018 3:42 PM
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.
https://www.dts-solution.com/solutions/infrastructure-security/dns-security/
Tuesday, June 26, 2018 1:22 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 [email protected].
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)
Monday, July 2, 2018 11:28 AM | 1 vote
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.
Tuesday, July 24, 2018 8:39 PM | 1 vote
Public KB
Error 0x80071779 when removing network components in Windows 10, version 1803
https://support.microsoft.com/en-us/help/4340181/
Saturday, August 11, 2018 9:41 AM | 2 votes
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.
Monday, September 10, 2018 11:45 AM
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.
Friday, October 5, 2018 11:28 PM
Also trying to use the Docker workaround. Tried Gunter Born's approach to disable and then re-enable the binding. Sadly did not work.
Wednesday, November 28, 2018 1:14 PM
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?