The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
100%, 150%, and 200% work on W10
125% exists as an option but is broken, a similar effect can be reached by taking off your glasses (if you need them) or looking through fog. It used to work on 7 (maybe?) and 8 (definitely), and that old way of "actually working" can be resurrected with some weird 3rd party program that applies a registry setting at boot (Windows really likes to un-apply the setting).
Microsoft introduced (with W8) a new method to work with DPI - they call it High DPI. It targets high resolution monitors and became the default method in W10...
So older software - and that includes software from Microsoft - will display blurred fonts (fonts only not any other graphics) when picking larger font size... And now you have to tell to Windows about each and every software not to use the new method, but fall back to the original...
As one use W10 for work only I have no gain from this High DPI method - which should be spectacular fro games and video - but I can't turn it off only software-by-software...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
Well...all I can say is that I'm not using any custom resizing or fiddle with per-app settings, and use each of my monitors' native resolution...and everything looks fine on all of them. Although I do keep hearing about some of the things you mention. If I had to guess, I'd say it all starts to surface once you start customizing things.
I've had a Windows Server 2019 VM refuse to install updates for quite a while now. Since today's patch Tuesday, figured I'd try to dig a little more into it since I'm going to be looking at that machine again sooner or later.
MS has made it clear for a while now that, with Cumulative Updates, you can take a brand new OS install, and immediately bring everything up to date just by installing the latest available Cumulative Update. Since this particular VM refuses to install the latest CU for Server 2019 (KB4522355, which came out October 24th) directly from my WSUS server, I figured I'd download the offline installer, and run that locally (more often than not this solves this type of problem).
Nope, "this update is not applicable to your computer". Tried many things, no change.
On a hunch, I tracked down the CU prior to that one--from October 8th (KB4519338). That one didn't complain, and is now in the process of being installed (as I'm writing this).
If these CUs are truly "cumulative", why does the newer one insist it's not applicable...? Windows Update itself insisted I needed it...
Does anyone else find it to be a pita to get pestered by the annoying system modal 'Updates are Available' screen where the only option is to 'View Available Updates'! Where is my 'Ignore Again' option?