Visual Studio 2019 bug when using two screens with different resolution

Andrew Innes 46 Reputation points
2021-02-17T16:08:39.23+00:00

I have two screen on is 4k resolution and the other (the laptop screen) is high defintion.

When using both screens to edit code and forms in VS 2019, the outlines of the buttons and textboxes etc frequently do not match the location of the underlying graphic. It is very annoying to say the least. If I click around I can get them to match up temporarily, but it does not stay.

If I run the code on just the laptop screen, there is no issue.

My computer is using Windows 10 enterprise which is updated regularly to the current version. Visual Studio is also updated to the most current version.

My laptop is an MSI GP63 Leopard 8rd and it has a good graphics card. It easily drives both screens and I did not have this problem with VS 2017.

So clearly there is a bug in Visual Studio that is causing the problem.

Please fix and advise. Thank you.

Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,631 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Andrew Innes 46 Reputation points
    2022-02-04T12:08:29.457+00:00

    I have the same problem when using Visual Studio 2022. That version also wrecked my computer from properly saving Word Documents as PDF files when using debug. My underlying code is still working fine on other machines, that only impacts the debugging functionality on both 2022 and 2019 on the computer with the version 2022 on it.

    1 person found this answer helpful.
    0 comments No comments

  2. Raffaele 6 Reputation points
    2022-05-18T07:58:51.243+00:00

    Same problem on the latest version of VS 2022

    1 person found this answer helpful.

  3. Daniel Nordh 1 Reputation point
    2021-10-05T11:48:07.757+00:00

    I would just like to add in that I'm experiencing the same thing when I hook up my laptop to my monitor and start working from there while Visual Studio is up and running.

    My solution is just to restart Visual studio after I've hooked up the monitor (or removed it since the same thing happens then).