This update enables the Large Address Aware (LAA) state for the 32-bit version of Outlook 2016 and Outlook 2013 on a 64-bit operating system. This causes a fragmented and non-rendering UI.
Even if you have moderate memory use, the contiguous free memory space is exhausted. Less SummaryĪssume that you use Microsoft Outlook 2016 or Microsoft Outlook 2013 for some time.
On a custom built desktop system with a i7-9900K, 32 Gb ram, AMD Radeon Pro WX 5100 (latest driver: 19.Outlook 2016 Outlook 2013 More. Other Office apps do not show this kind of behavior. In Outlook, letter types and icons are all scaled as if the screen setting is at 100%. When opening Outlook, everything looks as to expected in my Inbox, but whenever I access Sent Items or any other field The result is not a blurry though, but Outlook seems to only partially accept my screen settings, when displayed at the primary screen. Then my employer gave me a 27" screen, with a QHD resolution (2560x1440).
The blurry second/extended/external screen issues bothered me after I installed the 1903 Windows update, I finally saw it resolved when every software relatedĭriver was updated to current (latest) driver set. Stumbled upon this topic after being referred towards this platform via a Dutch MS Help portal. Mess around with fixing problems a big company could/should fix is blatantly wasteful and unethical. None of the rest of us have time for this. So, that leaves us with an MS with decades of experience having made an OS, applications and hardware.same problems exist, despite all of that. Making matters worse, we get this problem sometimes on Stop making users go through all of this by wasting resources on features we actually DID NOT ask for and fix the stuff that should have been fixed long ago. Like many things I'm finding consistent across various machines, this one is not MS has the resources to buy a bunch of various makes/models of machines and test this. Standard for machines, so MS uses that as an excuse not to find this stuff. It's a big company with a big staff and a big budget and doesn't force one Stop telling people MS is working issues they clearly don't test at all before pushing out. It's now ing Office 2016 still produces this problem on some machines. You may have a look at the following article for more info about upcoming improvements and possible solutions until the update is released: Microsoft is aware of the problem and is actively working on improving this in Office 2016.