I have a 1 TB Surface Pro 4 and Surface Book (with Performance Base). My problem is, text on these devices are blurry. First off, I don't use my screen in large fonts mode. I installed the standard Intel driver for the "GPU" so I could create a custom resolution of 1152x768 (Pro 4) or 1280x800 (Book). This works really well, as Windows is plain ugly with large fonts. In previous Surface generations, this did not cause any display issues at all. I've been on every version faithfully since the original Pro, and including the Pro 2, Pro 3, etc. However, in this generation, I have been unable to solve a very irritating issue of Blurry Text. Now, this issue happens only with *some* apps, and is more pronounced as you approach the corners of the screen. For example: 1) Windows File Explorer - File menu. Totally blurry. Right-click on the middle of the File Explorer, and the context menu is crystal clear. 2) Outlook 2016 - in-line email preview. Quite blurry. When scrolling with finger, crystal clear! The moment I let my finger go, or pause scrolling with my finger still on display; gets blurry again. 3) Generally, the ribbon UI on all system apps (including Paint) is affected. 4) Most non-system and non-office apps are *not* affected. Ready for the shocker? The issue does *not* happen when I am docked using the Surface Dock, and when I am using the Surface built-in display. I've searched on the Internet for issues similar to mine - if anything, people are reporting the exact opposite. The issue happens when they are docked on their secondary monitors and such. For me, I get a crystal clear view on my built-in display while docked. The moment I yank the docking cable, the screen blacks out, then comes back again - with the blurriness problems as described earlier. I've tried high DPI fixes, various cleartype settings - all to no avail. This is getting to the point where it is now hurting my vision. It is not a device-related issue, as I have sent back a Pro 4 for repair (due to a battery bulge problem) and got it replaced. Same issue on the new device. I am waiting for my Pro 2017 but I'm not counting on it that they've solved this issue they introduced with the Pro 4 generation. Has anybody run into this? Know of any way to fix the issue?