Wrong DisplayName on protocols components, for ALL network adapters

Question

Hi,

In all my network adapters, the protocol components appear with wrong DisplayName

For instance I get :

• %systemroot%\system32\drivers\tcpip.sys
• instead of "Internet Protocol Version 4 (TCP/IPv4)

The issue is similar to this error-on-tcpip-properties but that fix doesn't apply, because in my case the DisplayName are wrong on all my network adapters.

I'm running a desktop with

• Windows 10 Pro x64
• version 10.0.19045 Build 19045

Here are the steps that I already performed :

• Running Full Antivirus Scan with Norton
• Run malware scans with MalwareBytes and RogueKiller
• Restore to a point previous to the issue occurence - Run Windows Updates and install Cumulative KB
• Delete and install of the Realtek driver
• Tcpip.sys driver repair, like here https://www.donationcoder.com/forum/index.php?topic=22598.0
• Uninstall/reinstall all network adapters
• Restore Default Startup Type of TCP/IP Protocol Driver, like here http://batcmd.com/windows/10/services/tcpip/
• Network cleaning and reset with "netcfg -d" , like here https://woshub.com/reset-network-windows/
• Copy the services DisplayName binding from a healthy Windows laptop HKEY_USERS.DEFAULT\Software\Classes\Local Settings\MuiCache\36\52C64B7E
• Copy the registry entries from a healthy Windows laptop HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock2

Two remarks :

1. I wanted to rebuild the entire tcpip stack, like here https://www.kapilarya.com/windows-sockets-registry-entries-required-for-network-connectivity-is-missing but I got an error "blocked by group policy"
2. The DisplayNames appear correctly when I run Windows in "Safe Mode with Networking" .... I've read somewhere that MSFT_NetAdapterBindingSettingData contains the DisplayName info. Could it be possible that the Adapter-Protocol bindings are applied well for "Safe Mode Boot" but don't apply for "Normal Boot" ? Anyway, any advice will be valuable please. Thanks in advance

Answer 1

Hi there,

Uninstall Citrix Workstation or revert to its earlier build that doesn't have this bug.

Answer 2

Great, glad that worked. Thanks for the update, Marc.

Answer 3

That did the trick : below a screenshot of the displaynames after uninstalling Citrix WS.

Citrix was certainly preventing all NetAdapterBindings to retrieve the correct DisplayName ...

Thanks a lot Ramesh ! 💪