Unable to enable Net BIOS over TCP/IP in PowerShell

You probably should reboot after making an changes to registry like that.

Yea ... I hear you. If there is a another setting that controls it, I don't know what it is. Appears you've done all the usual checks/repairs, so you may be looking at doing an in-place upgrade/repair to get things working again, but only you can make that call ... Sorry I couldn't help ...

See this tutorial - Repair Install Windows 10 with an In-place Upgrade | Windows 10 Tutorials

Ouch.

Glad you got it sorted.

FWIW ...
I've been curious as to why ipconfig /all shows NetBIOS over TCP/IP as disabled when it's actually not according to the settings (adapter properties and registry). I've run across a couple of things that it appears can cause this. However, the fix is way more involved than the average user can or is willing to do. So, if you having this issue your best bet is an in-place repair install or a clean install.

Note:
1. Since I don't have this issue, there isn't anyway for me to confirm these.
2. It appears that a Network Reset doesn't fix these.
3. Attempt these manual fixes at your own risk !!!

Possible causes for NetBIOS over TCP/IP showing as Disabled in ipconfig /all ...
1. It appears that there can be more interfaces created than NetBT can handle. What the number is ... I don't know.

"I finally got the problem solved! Your suggestion of checking the NetBT keys in the registry steered me in the right direction. There were a huge number of interfaces in there, way more than the number of network adapters shown in device manager. It turns out that Windows Mobile Device Center had been creating a new hidden network adapter every time a new device was connected, eventually creating more adapters than the NetBT service could handle. They showed up in WMI using "wmic nicconfig get" but could not be removed. Finally I was able to use devcon to enumerate their device IDs, then I created a batch file to use devcon to get rid of them. Everything's working now!"
Reference (dingusdongus) - Cannot Enable NetBIOS over TCP/IP : techsupport

2. It appears that you can loose active adapters GUID from some of the registry keys responsible for binding adapter to services.

"In my case the the problem was caused by loosing active adapters GUID (e.g. WLAN) from some of registry keys responsible for binding adapter to services. I had to review them and add GUID manually to ensure that all keys contains my GUID."

Code:

[HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Linkage]
 "Bind"=multi_sz: \Device\NetbiosSmb \Device\NetBT_Tcpip_GUID 
"Export"= multi_sz: \Device\LanmanServer_NetbiosSmb \Device\LanmanServer_NetBT_Tcpip_GUID 
"Route"= multi_sz: "NetbiosSmb" "NetBT" "Tcpip" "GUID" 

 [HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\Linkage]
  "Bind"=multi_sz: \Device\NetbiosSmb \Device\NetBT_Tcpip_GUID 
"Export"= multi_sz: \Device\LanmanWorkstation_NetbiosSmb \Device\LanmanWorkstation_NetBT_Tcpip_GUID 
"Route"= multi_sz: "NetbiosSmb" "NetBT" "Tcpip""GUID" 

[HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Services\NetBIOS\Linkage] "Bind"=multi_sz: \Device\NetBT_Tcpip_GUID 
"Export"= multi_sz: \Device\NetBIOS_NetBT_Tcpip_GUID 
"Route"= multi_sz: "NetBT" "Tcpip" "GUID"

[HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Linkage]
"Bind"=multi_sz: \Device\Tcpip_GUID 
"Export"= multi_sz: \Device\NetBT_Tcpip_GUID 
"Route"= multi_sz: "Tcpip" "GUID" 

[HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\Tcpip_GUID]
"NameServerList"= multi_sz:”” 

 [HKEY_LOCAL_MACHINE\vzVEID\MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage]
"Bind"=multi_sz: \Device\GUID 
"Export"= multi_sz: \Device\Tcpip_GUID 
"Route"= multi_sz: GUID 

Reference (Nikriaz) - Can not enable NetBios over TCP/IP on shared network interface