MS Wireless Display Adapter: Trouble after Surface Pro 3 Firmware/TPM and Windows 10 1803...

Hi together,
I have (also) trouble with the MS Wireless Display Adapter (MWDA).

About 3 weeks ago I done all available firmware and TPM updates on the Surface Pro 3 (i7-4650U / 8 GB), Windows 10 Pro 64 Bit (Version 1803 Build 17134.319) and the MWDA are set to the current software state.

<<< Before the surface Pro 3 updates it works all fine >>>

After trying out all the tutorials and troubleshooting guides on 2 weekends, I'm now at the end and really annoyed. The display and Wi-Fi driver has been uninstalled and reinstalled. The VPN software is completely removed. The Norton Security software was also completely uninstalled and Windows Defender was temporarily switched off. Also the MWDA was reset several times. All this bring not the desired success...

I see the Surface with the MWDA connecting via a Wireless DIRECT Network, but it seem´s this connection breaks after a while AND...

<<< Now the display on the TV Screen always does NOT appear >>>

In this cases I see the Surface Wireless DIRECT Network over a Wi-Fi analyser, also on the Surface with the Powershell command "Get-NetAdapter -IncludeHidden | sort MacAddress" you can see that the Wi-Fi DIRECT Network is go to up state. You can also see a Network Adapter within the network connection" section with the Name of the Wi-Fi DIRECT Network - after the connection is terminated the adapter is disappears. In the registry I also can see under Network Profile Section, that a new network profile (felt) for every new DIRECT Network will be created with every connection / abort.

<<< That the connection is established also proves that I could make a software update over this short connection from the MWDA App from the Surface to the MWDA ! >>>

By the way, with other Devices, for example with my Android phone the MWDA works fine...


I think this must really be an Firmware or Windows update problem.

It would be great if someone can support here. I can pull all necessary logs, debugs or whatever is needed.

Regards

Thomas