Hi All,
I have just found a resolution to my issue (same as your issues)..
I manage IT at a school.
We have about 100 SP6 and 200 SP7.
All have a dock1. My last school had 1500 SP 4,5,6 (only a few docks). Had a fair bit of experience with issues with Docks and monitors.
The main cause (Microsoft told me this - not advertised anywhere) was a little known fact that you need an 'active' cable. On sale on their website for $65+. The Surface/docks1 do not translate the digital signal to HDMI but rely on the cables to do it. Odd, as some cables worked that were not active. Some don't.
I just bought five more SP7 (i7 + 16Gb RAM as the i5 + 8Gb do not cut it - awful performance issues when using TEAMS or ZOOM with any other program). The new docks are Dock2. I was hoping that the 199w power supply would have solved all the issues. They have not.
Issues:
- one monitor not displaying but still detected
- having to power cycle the dock every time I re-docked the device
- third monitor not working when plugged into the Surface
- fuzzy static on main monitor when turned on for the first time
- keyboard not getting power through USB - needing to replug it or powercycle dock2
Two weeks later, I am now on my third dock2, 6th cable and third SP7 (the first two were imaged using SCCM. This one is OOTB).
Awful experience with multiple monitors so far.
On each device I have updated to the latest version of Windows 10 2004.
This morning on my latest OOTB model (left at 1909) I installed the following (all the other models had it):
And after a number of reboots and updates to 1909 Win10, I am cautiously stating that all is good. I have three monitors and when I undock-redock, all works. No shimmering of monitor or fuzziness.
If I open the lid to try and get four monitors, the far left portrait one connected to the SP7 turns off.
Touch wood.
Perhaps the SP7 drivers in our SCCM image were causing the issue (but they had the latest Firmware included).
The OOTB model did not work well at first but after I installed updates work well.
I'm now going to update to 2004 and see if that is the issue. Will post if bad results. Perhaps that was the issue with the other two SP7s.
Good luck.