03-17-2017 07:45 AM
When I boot up without a connection to an external monitor I experience some display issues with text sizing of certain objects within certain applications (e.g. Microsoft Visual Studio). In these applications parts of the User Interface display perfectly. Other parts of the same application will have vastly oversized objects and text. And, in another application the text is greatly undersized in certain portions of this app.
When I boot up while connected to an external monitor everything displays perfectly on the external monitor. This happens without making any changes whatsoever to system display setting or application configuration settings. If I disconnect the external monitor the X1's internal monitor still displays everything perfectly. But if restart while disconnected from an external monitor I experience the same display issues as described in the 1st paragraph.
I don't think this problem was always there, but I cannot say for sure. It just got so annoying that I finally decided to write to the forum today. I would guess that the problem has been this way for 1-2 months.
The Lenovo System Update app tells me that everything is up to date. Is there some setting or perhaps driver that needs to change?
03-20-2017 03:12 AM
Thanks for using the Lenovo forums.
Try to download the Video and Chipset drivers for the unit from the support page.
See if these will make any difference.
Make sure to reboot after an update.
Are you able to send a screenshot of these problems by any chance?
Hope this helps, let us know how you get on.
Did someone help you today? Thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
03-20-2017 09:23 AM
I explicitly applied all of the Chipset and Video drivers. However,there was no change in my display issue after the drivers were applied and the system rebooted.
I attached some screen shots of the issue. Note once again, the application in the screen shot with this problem is Visual Studio 2015. But, I have experienced the same problem in other applications.