Surface Pro Miracast Connection Problem

I am essentially re-asking the same question, but in a different manner as it has been two weeks and the problem of the Surface Pro 2 not connecting to our new LG OLED, Miracast-compatible TV remains unresolved.  They do attempt to negotiate a connection, but they fail to connect.

I ran dxdiag on the Surface Pro 2 running Windows 10 with all the latest updates, and the results show the computer is Miracast compatible.  I have also separately checked for updated drivers and the result was that the drivers are up-to-date.

System Information

      Time of this report: 1/25/2018, 09:54:36

      ...

                 Miracast: Available, with HDCP

     ...

Display Devices

           Card name: Intel(R) HD Graphics Family

     ...

            Miracast: Supported

Initial attempts failed every time, even when the Surface is just a few feet from the TV.  Conversely, our HP laptop connects flawlessly every time.  This tends to suggest that the problem is within the Surface computer - not the TV.

I read Barb Bowman's informative article describing how Miracast negotiates a connection and, as a result, I checked the visible 2.4GHz networks around here.  There are four weak ones (~20% strength) on CH1, our own 'main' network on CH6 all by itself, and our own secondary network and two other weak ones on CH11 (78% and ~20% strength, respectively).  I presume the Surface and the TV being just a few feet apart, the related signal strengths would be adequate to override the weaker network signals on CH1 and, therefore, Miracast should be able to negotiate a connection.  The HP computer is 6x further away from the TV and, as mentioned, it connects flawlessly every time.

However, I did spot a difference between our two computers when connecting - namely the IPv4 address indicated for the direct-connection 'adapter'.  The IPv4 Address was 192.168.137.1 for the HP computer (and it was the same for my various acquaintances' computers as well), whereas on the Surface it was indicated as Autoconfiguration IPv4 Address 169.254.56.231.  The IPv4 Subnet Masks were 255.255.255.0 and 255.255.0.0, respectively.

As Miracast is essentially a peer-to-peer connection without a DHCP server to provide an IP address, on the virtual wireless adapter that is active during Miracast connections, I configured the IPv4 'Alternate configuration' to an address of 192.168.137.1, the same IP address that works every time when the HP laptop connects.

I thought I had found the answer as it worked briefly (during a 20-minute test period), and the results were very good .

However, the next day when there was something my wife actually wanted to see on the big-screen TV, she tried again and it failed to connect.  Several attempts were made - all unsuccessful.

A few days later a friend suggested that I try adding the same IP address for the Default gateway and DNS server.  I wasn't sure what good this would do, but I tried and it worked again during an hour of testing (to see if it would drop out - it remained solid).

However, once again, while it worked for the hour or so of testing, later it again failed to connect.  We tried several times throughout the day and again over the next couple of days, but no luck.

I have tried shutting off Bluetooth, and even shutting off the HP computer to eliminate any impact they may have, but the Surface and TV will NOT connect.

The issue is almost certainly within the Surface computer, and I have no idea where else to look.  Can someone from Microsoft please shine some light on this?  There are so many discussions on the web about this problem with Surface computers; so, it must be very widespread and there must be a lot of frustrated Surface owners out there!

Any expert assistance would be appreciated.  Thank you.