but it keeps reappearing. The cause may have been tracked down by the brilliant Simby in this thread. He gives detailed instructions but in summary there is bug in Microsoft’s Windows 10 TCP/IP stack when using a static IP. The workaround is to edit the Advanced TCP/IP settings of each of your network adapters to “Disable NetBios over TCP/IP”;

Having disabled NetBIOS I find that I cannot resolve computer names on my home network. I had hoped that DNS would be used first but this was not working for my Windows 2003 server. I could put its details in an LMHosts file. I have reverted my configuration to use NetBios and will keep you informed of progress.