Monitor stuck on displayport with 640x480

Anonymous
2020-02-02T03:26:26+00:00

Hi all.. Today after I updated my surface pro, my monitor is stuck in a 640x480 resolution. Which is no good with a 49 inch Samsung monitor. If I plug in the HDMI, it works, but, resolution is not that good like it was on the Displayport. Any tips or tricks to get it working again? For some reason it shows 'Flat Panel, 640x480' when using display port, but the samsung drivers when using HDMI. 

I am using the surface dock as well. I tried the displayport of the monitor with other computers and it's working fine. Not with surface. Really need help with this one!

Surface | Surface Pro | Install and update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

315 answers

Sort by: Newest
  1. Anonymous
    2022-01-11T10:59:19+00:00

    I've finally found a mitigation.. (I still refuse to call this a solution, but I want to share this because it might help someone else)

    After having been stuck on this since forever, I've managed to update my setup so I can now use my monitor on 4k60hz

    Setup: surface pro 7 => dock 1 (docking connector) => mini-DP male to HDMI female (Microsoft) in dock => HDMI 2.0 cable to monitor (Philips 436m6)

    Note: do make sure to use a HDMI cable that you know is capable of giving out 4k60Hz before writing off this workaround.

    Sidenote: the only reason I tried this, is because I've lost all faith that anyone will ever provide us with a solution and I was really sick of the driver issues in the november 2019 version. (intermittent black screens when sharing in Teams, pixel-shifts, fuzzy text, etc)

    (sold out) connector in question is the Model 1819 Mini Displayport HDMI adapter: Buy Surface Mini DisplayPort to HDMI 2.0 Adapter  - Microsoft Store

    I still had it in my drawer from a previous surface model, so I didn't have to buy it.. I just spent 4 hours searching for it, but that's on me. Serves me right for not cleaning up after myself.

    Honestly, I don't know if this is a vendor specific (Microsoft-connector only) mitigation and I don't have any alternatives to test, but it might be something to to investigate.

    I've updated my graphics driver to the following version: 27.20.100.9621 date 15/06/2021

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-01-03T16:18:56+00:00

    Yes, Microsoft is dropping the ball HARD.

    And their so called Tier 3 support is avoiding having a paper trail, and insist on phone calls to "troubleshoot" the problem, which so far is a total waste of my time.

    Now, they just keep asking me to contact LG without providing any further details and very keen to "re-schedule" the next call.

    Am not giving up just yet... maybe I'd pick up the pen and write to Mr. Satya Nadella directly and hope the stars align...

    Cheers.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-01-03T00:24:24+00:00

    I fixed my problem. I guess the surface to my wife - she only wanted a laptop. I bought myslef a Lenovo Yoga Titanium about four months ago and am happy to have my dual monitors back!

    I have owned every Surface from the 3, but will never own another. That was a terrible 2 years!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-01-02T16:18:00+00:00

    So, now, in 2022, 2 years later, am still stuck with old driver, which puts up significant limitations with the latest Da Vinci Resolve.

    LG support seems to have no clue and MS "tier 3" support just shrugged their shoulders and hope I go away for good.

    THANK YOU, MICROSOFT, HAPPY NEW YEAR.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-12-27T13:17:50+00:00

    Come to think of it, it seems to be a rather lame excuse by Microsoft that it's a monitor issue when the problem was introduced by their driver "update".

    Was busy and didn't think it through.

    Cheers.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments