Hope everyone is having a good day. Today, we have a guest among us. Steve Wright is a Senior Program Manager in the Developer Platform Group. He is authoring this blog regarding scaling in Windows 10 with how it works and how users will benefit from the work we have done with scaling.
Overview/Introduction
Windows 10 is an important release for Windows display scaling. It implements a unified approach to display scaling across all SKUs and devices aimed at these goals:
1) Our end users enjoy a mix of UWP and classic desktop applications on desktop SKUs which reliably provide content at a consistent size
2) Our developers can create UWP applications that deliver high quality reliably-sized content across all display devices and all Windows SKUs
Windows 10 also delivers desktop and mobile UI which looks polished and crisp across a wider range of display densities and viewing distances than we have ever before supported on Windows. Finally, Windows 10 drives support for high quality multi-monitor scaling for docking and projection into more of both our desktop and our mobile UI.
This article covers the basics of scaling in Windows 10, how it works, and how users will benefit from the work we have done. It wraps up by charting the course forward and show what we want to tackle in future updates to Win10.
Our vision for display scaling
For our end users, display scaling is a platform technology ensuring that content is presented at a consistent and optimal–yet easily adjustable–size for readability and comprehension on every device. For our developers, display scaling is an abstraction layer in the Windows presentation platform, making it easy for them to design and build apps, which look great on both high and low density displays.
Basic concepts and terms
We need a basic glossary of terms and some examples to show why scaling is important:
While these examples use phones for the sake of simplicity, the same concepts apply to wearables, tablets, laptops, desktop displays and even conference room wall-mounted TVs and projectors.
Dynamic scaling scenarios
Note that more than one display may be used on the same device—either all at the same time, or at different times in sequence. Scale factor and effective resolution are therefore dynamic concepts and depend on where content is displayed at a particular time.
Some everyday scenarios where this dynamic scaling can take place include projecting, docking, moving apps between different monitors, and using remote desktop to connect your local display to a remote device.
Who does the scaling, and how do they do it
Because Windows supports many different kind of applications and presentation platforms, scaling can occur in different places. This table illustrates the major scaling categories:
|
Scaling Class |
Examples |
Pros and cons |
|
Dynamically scaling apps:
|
UWP apps
Desktop UI built on XAML and HTML
Some classic desktop apps
|
+ Crisp and right-sized content everywhere + Very easy to support for UWP apps (developer can rely entirely on framework support) – Very hard to support for Win32 apps |
|
“System scale factor” apps:
|
A small number of top-tier classic desktop apps–about 50% of them, weighed by user “face time”:
WPF apps: all WPF apps support this |
+ Crisp and right-sized on primary display – Right-sized but somewhat blurry on other displays – Moderately hard for Win32 developer + Comes for free in WPF apps |
|
“Scaling unaware” apps:
|
Majority of classic apps, weighed by app count
|
+ Crisp and right-sized on low DPI displays – Right-sized but somewhat blurry on any high DPI display |
What this means for the user:
- UWPs and most Windows UI looks great on high DPI displays and in any multi-monitor scenarios where different display scale factors are in play
- A few important classic desktop apps (and all WPF apps) look great on high DPI primary displays but a little blurry on other secondary displays
- A large number of older classic desktop apps look blurry on high DPI displays.
What we have done in Windows 10
Now we can talk about the work done in Windows 10 to improve our support for both high DPI displays and for dynamic scaling scenarios. This works falls into several major areas:
- Unifying how content is scaled across all devices running Windows to ensure it consistently appears at the right size
- Extending the scaling system and important system UI to ensure we can handle very large (8K) and very dense (600 DPI) displays
- Adding scaling support to the mobile UX
- Improve Windows support for dynamic scaling: more OS and application content scales dynamically, and the user has greater control over each display’s scaling
Let’s take a closer look at each of these.
Unified and extended scaling system
In Windows 8.1 the set of supported scale factors was different for different kinds of content. Classic desktop applications scaled to 100%, 125%, 150%, 200% and 250%; Store apps scaled to 100%, 140% and 180%. As a result, when running different apps side by side in productivity scenarios, content could have inconsistent sizes in different apps. In addition, on very dense displays, the scaling systems “capped out” at different points, making some apps too small on them.
This chart shows the complexity and limits of the 8.1 scaling systems:
For Windows 10, we unified all scaling to a single set of scale factors for both UWP and classic applications on both the Desktop and Mobile SKU:
In Windows 8.1 all scaling topped out at 180% or 250%. For Windows 10 we knew that devices like 13.3” 4K laptops and 5.2” and 5.7” QHD phones would require even higher scale factors. Our unified scaling model for Windows 10 runs all the way to support 450%, which gives us enough headroom to support future displays like 4K 6” phones and 23” 8K desktop monitors.
As part of this effort, Windows 10 has polished the most commonly used desktop UI to look beautiful and clear even at 400% scaling.
Making the mobile shell scalable
We have also overhauled our Mobile SKU so that the mobile shell UI and UWP apps will scale to the Windows 10 scale factors. This work ensures that UWP apps run at the right size on phones and phablets as well as desktop displays, and that the mobile shell UI is presented at the right size on phones of different sizes, resolutions and pixel densities. This provides our users with a more consistent experience, and makes it easier to support new screen sizes and resolutions.
Improve Windows’ support for dynamic scaling
When we added dynamic scaling support in Windows 8.1, there was relatively little inbox UI that worked well with dynamic scaling, but in Windows 10, we have done work in many areas of the Windows UI to handle dynamic scaling.
UWP application dynamic scaling
As noted above, UWP HTML and XAML apps are designed to be dynamically scalable. As a result, these applications render crisply and with the right size content on all connected displays.
Windows “classic” desktop UI
Windows 10 makes large parts of the most important system UI scale properly in multi-monitor setups and other dynamic scaling scenarios so that it will be the right size on any display.
Start Experience
For example, the desktop Start and Cortana experiences are built on the XAML presentation platform, and because of that, they scale crisply to the right size on every display.
File Explorer
File Explorer—a classic desktop application built on the Win32 presentation platform—was not designed to dynamically rescale itself. In Windows 10, however, the file explorer app has been updated to support dynamic scaling.
Windows Taskbar
In Windows 8.1 the Windows taskbar had similar historical limitations. In Windows 10, the taskbar renders itself crisply at every scale factor and the correct size on all connected displays in all different scenarios. Secondary taskbar UI like the system clock, jumplists and context menus also scale to the right size in these scenarios.
Command shells et al.
We have done similar work elsewhere in commonly used parts of the desktop UI. For example, in Windows 10 “console windows” like the command prompt scale correctly on all monitors (provided you choose to use scalable fonts), and other secondary UI like the “run dialog” now scales correctly on each monitor.
Mobile shell and frameworks
In Windows 10 the mobile platform also supports dynamic scaling scenarios. In particular, with Continuum, the phone can run apps on a second attached display. In most cases external monitors have different scale factors than the phone’s display. UWP apps and shell UI can now scale to a different DPI on the secondary display applications so that Continuum works correctly at the right size on the Mobile SKU.
User scaling setting
Windows 8.1 users reported frustration with the user setting for scaling:
- There was a single slider for multiple monitors. The slider changed the scale factor for every connected monitor, making it impossible to reliably tweak the scale factor for only one of the displays.
- Users found it confusing that there were two scale settings, one for modern apps/UI and another for classic apps/UI, and that the two settings worked in significantly different ways.
In Windows 10, there is a single scale setting that applies to all applications, and the user applies it to a single display at a time. In the fall update, this setting has been streamlined to apply instantly.
What we didn’t get to
We are already seeing a number of common feedback issues that we’re working on for future releases of Windows. Here are some of the biggest ones we are tracking for future releases:
Unscaled content: Lync, desktop icons
Some applications (for example, Lync) choose to disable bitmap scaling for a variety of technical reasons, but do not take care of all their own scaling in dynamic scaling scenarios. As a result, these apps can display content that is too large or too small. We are working to improve these apps for a future release. For example, desktop icons are not per-monitor scaled in Windows 10, but in the fall update they are properly scaled in several common cases, such as docking, undocking, and projection scenarios.
Blurry bitmap-scaled content: Office apps
Although the UWP Office applications are fully per-monitor scaled in Windows 10, the classic desktop apps are “System scale factor apps”, as described in the table above. They generally look great on a high DPI device, but when used on secondary displays at different scale factors (including docking and projection), they may be somewhat blurry due to bitmap scaling. A number of popular desktop applications (Notepad++, Chrome, Firefox) have similar blurriness issues in these scenarios. We have ongoing work on improving migration tools for developers with these complex Win32 desktop applications.
Conclusion
Scaling is a complex problem for the open Windows ecosystem, which has to support devices ranging in size from roughly 4” to 84”, with densities ranging from 50DPI to 500DPI. In Windows 10 we took steps to consolidate and simplify our developer story for scaling and to improve the end-user visual experience. Stay tuned for future releases!
Thanks for a great explanation, very informative, display scaling has certainly improved since Windows 8.1. If I understand correctly, it is going to be difficult to implement having different scaling factors for each screen, since some applications only
look at the primary screen at startup? In the scenario where connected displays have very different resolutions and display densities (i.e. a Surface Pro 3 and a couple of 24" 1080p monitors), having to use the same scaling factor on all displays is a compromise.
Either things will be a little too big on the monitors or too small on the high-density-but-small-size Surface Pro 3 screen. Being able to set different scaling factors, would solve this problem. Thanks again.
Thanks for the explanation – a very informative overview article, it's difficult to find this sort of introductory information so this it definitely helpful.
One area that still needs work is RDP sessions. If I connect from a Surface Pro 3 to a PC in Windows 10 everything scales pretty well (thank you!), but then if I later reconnect to the same session from a PC with a conventional display, everything is way too
magnified. Windows needs to re-scale on every RDP connect!
Top notch content!! All the major topics that our customers required to understand a bit more the new variables introduced by increased resolutions and pixel density!
Thanks Steve!
What do you have to say about the need for these tools? Lots of people are still complaining
http://windows10_dpi_blurry_fix.xpexplorer.com/
http://forums.mydigitallife.info/threads/62528-SOLVED-Windows-10-higher-DPI-Win8DpiScaling-problem
http://www.tenforums.com/general-discussion/11079-fix-windows-10-blurry-text-windows.html
When is it planned to get the classic desktop layout (including right click menus etc) to scale properly?
It is currently unworkable going from logging on a 27" WQHD screen as primary, unplugging and keep working on the laptops 15.6" QHD+ screen without logging out and in again. Some things are utterly small and some elements big with small text etc etc.
Same thing goes when connecting via RDP, scaling is all over the place so I agree with Mike's comments.
The Windows Update version 1511 has created some issues with scaling on my Surface Pro 4, especially in the Jagex MMORPG Runescape. When I first got my Surface, it worked fine with the game, but now the in-game text is so tiny as to be unreadable. I have
a work around that is less desirable so that I can still use my surface pro, but I am not happy that this scaling change has so negatively affected my game play, one of the primary reasons I bought the surface in the first place.
Thnaks for explanation. But there are two serious problems with scaling to High DPI (UHD):
– almost all monitors upscale screen very poorly. Instead multiplying pixels to match higher resolution, they interpolate them. Result is that FHD desktop / game displayed on UHD are blurry. It is more problematic for gamers, because UHD resolution require
strong (and expensive) graphics card.
– many legace apps do not scale well with High DPI, and of these app won't be upgraded at all.
Solution to successfully fix these two problems is to introduce two new modes to Win 10: Double Pixels and Double Pixels With Scaling. Mode Double Pixel just upscale screen 2x, so if user choose FHD resolution with Double Pixel, then Windows upscale everything
to UHD without use interpolation, so everything will be crisp as with FHD monitor. Second mode – Double Pixels With Scaling – is bit more advanced, because it renders all scalable elements (fonts, lines, geometric shapes, etc) with double resolution, to provide
smooth edges.
These two modes are completely transparent to apps, and may resolve many scaling problems.
I have exactly the same problem
My laptop is Asus G501jw with a 4K resolution on a 15.6 inch screen. so the dpi is high
most of softwares doesn’t support 4k screen well.
when i switch the resolution to FHD, texts and icons get blurry.So a FHD screen would have much better qulaity than my 4k screen with resolution set on FHD
I agree with Tristan that just doubling the pixels will fix this specific problem easily.
We are finding all sorts of long-standing flaws buried in the OLE/ActiveX infrastructure that misreport DPI-related metrics. For example at 200% DPI there are tons of places where it gets handled as if Twips/Pixel is 7.0 instead of 7.5, and this flaw is
carried for any absolute units (HiMetric, HiEnglish, etc.). Many of these errors carry over into GDI as well. Your own Office folks (among others) must be tearing their hair out. I know we sure are.
Visio 2016 appears to have got dynamic scaling wrong in a small detail – the resizing indicator when expanding the Shapes window. This works fine unless you move the window onto a display at different DPI.
You have done a poor job with scaling.
It is full of bugs and makes my Surface Pro a nightmare to use with external monitors.
I have Office 2013 on Windows 10.
My main monitor (HiDpi) is set to 200% scaling. My external monitor (1080p) is set to 100% scaling.
If the preview pane is active in the File Explorer then the scaling on the external monitor is not working correctly:
Everytime I open an Office document on the external monitor it it scaled to 200% and not 100%.
The only way to make it work is:
– Close the Office app (eg. Word)
– Disable Preview Pane in File Explorer
– Close and re-open File Explorer
– Reopen the Office app.
But now I cannot use the Preview Pane at all…
I am working on dynamic scaling support for my Win32 desktop app, and I find the documentation terrible. Or, better say, I find no documentation at all.
In my app manifest I have True/PM.
Here are my basic woes:
Standard message boxes (AfxMessageBox /MessageBox) are not scaled.
Who could scale them if not you?
How to scale CFileDialog and CFontDialog? Notepad scales them. How??
How to scale menus? You draw them, not I. Is it so difficult?
How to scale non-client area (title bar)? Notepad does it. How?
This may be a good resource for you:
https://msdn.microsoft.com/en-us/library/windows/desktop/dn469266(v=vs.85).aspx
You can call me blind, but I do not see anything there related to my questions: scaling standard message boxes, menus, common dialog boxes.
Would you be so kind to give me a relevant section name there?
I see they’ve now added EnableNonClientDpiScaling to handle the non-client area, including menus.
I still can’t see how MessageBox and the file dialogs should be scaled, or even PropertySheet. As you say, Notepad and Command Prompt support them in Windows 10.
I suspect there could be some as-yet-unreleased API calls being used.
“Scaling unaware” apps shouldn’t be blured and compressed on 200%/400% etc scale.
They should be displayed natively in 1080p on 2160p screens. Using 4 pixels to display 1 pixel.
Helpful to have this explanation and to see the extraordinarily complicated work in progress. I want to report some bugs from the field, in case their helpful. I’m working with a Lenovo Yoga 900 laptop (native screen resolution 3200×1800) and a Samsung external monitor (native resolution 1920×1800).
Word scales properly if:
– the session is freshly booted, but not after waking up from sleep
– the external monitor is plugged in and turned on at boot up, but not if the external monitor is plugged in subsequently (even if it’s plugged in before opening Word)
– the file is opened initially through Word but not through file manager
Power Point doesn’t scale at all, and is unresponsive to changes on the slider bar for the external monitor (i.e., it looks like it’s on 175% no matter where the slider is set). Same is true for Acrobat Reader.
Excel and Chrome sometimes scale and sometimes don’t; I haven’t had a chance to explore them yet.
Quicken and QuickBooks get bizarrely distorted. For example, in a table, the numbers scale differently than the gridlines in the table; they’re too big and are competely unreadable.
I hope these observations give you useful clues and that you can address these issues soon. The workarounds are clumsy and diminish the user experience of machines that are otherwise quite remarkable. Thanks.
I note several problem in browsers. Some text and images are blurry.
I wrote about this issue in this post:
http://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/blurry-imagesicons-on-browsers-windows-10-dpi/ed12f34c-85c7-48b4-a62d-4a318523dc4b
Please upgrade the DPI system
Thanks
Thanks for the explanation, and I’m glad to hear it’s still being improved. I think Windows 10 is definitely moving in the right direction in how it handles scaling, but I still find it has issues that need improving. Here’s my situation:
I have a high DPI laptop which I routinely dock with larger, lower-DPI monitors. I’ve tried the following configurations, none of which are ideal:
1) Laptop set to native resolution, scaled to 150%. Looks great on laptop, but when I connect external monitors, the text in apps like Chrome, Visual Studio, etc. on these external monitors is blurry. The size of these programs/text is correct (ie, not too large), and native stuff (like the start menu) looks great on all monitors, but lots of apps are uncomfortable to use due to this, making this unsatisfactory.
2) Laptop set to lower resolution that is usable at 100%. Laptop looks ok but obviously lacks the crispness of higher-DPI. External monitors look correct (no blurry text). This is the only satisfactory configuration I’ve found.
3) Combination. I tried setting my laptop to native resolution when it’s not docked, but lower-than-native with no scaling when docked. Windows does appear to switch the resolution when I connect my dock, which is great, but unfortunately the external monitors still look blurry even if everything is at 100% scaling, until I log off/on. So this doesn’t work either.
It seems to me that Windows applies some filter to text when scaling is enabled (ClearType, perhaps?), but it applies this to all monitors, regardless of their scaling setting. Thus, when everything is not scaled, things look correct, but when there’s a mixture of scales, the unscaled monitors look bad. It seems to me this could be fixed by making sure all these display tweaks are applied on a per-monitor basis, rather than some things being global while others aren’t.
Another more minor quibble: When I have mixed scaling, Windows ignores the scaling when determining the relative physical sizes of the monitors in the Display Settings view. What I mean by this is, my physically small but high-resolution laptop screen is shown as larger than my physically larger, but lower-res external monitors, even when the laptop screen is set to 150% scaling (which should make it be treated as a smaller physical size). This causes annoying alignment issues when I move my cursor from monitor to monitor. This too is resolved by configuration #2 above, but again, it’s a waste of my high DPI screen.
why cant i get 115% display in win10. only 100 or 125.
The Windows 10 per-monitor DPI setting is a big improvement that I had been asking for a while. However, there is a missing use-case for those of us trying to automate test – there is no documented way for automation to change the DPI setting (per monitor) on-the-fly. This is needed to test applications and rendering correctly. There have been no answers to posts on Windows Insider or emails to the developers that I was told to contact. An official answer would be really appreciated.
I used to be fluent in computer speak, but have been very ill for a couple of years and… Why can’t there be simple answers? Everything is blurry and hurts my eyes, Like XP, Vista, & 7 but this is silly. Microsoft has tried to get closer to Mac for years so why can’t they make it easy and great?
Windows 10 scaling across multiple displays is a bit broken, is there any plan to fix this?
On my setup, I have 2x 27″ displays, one at 5k resolution and one at WQHD. Windows sees the 5k monitor as a physically larger monitor, so the mouse jumps to the wrong location when moving from one monitor to the other
My Mac has no such issue. It reads both monitors as the same size, while giving me the benefit of higher resolution on one monitor. No mouse jumping at all
Great rounup. Glad to see the Windows team is well aware of all the issues, is listening to user complaints and working on improving the situation.
Scaling in Windows 10 is actually quite workable already. I just hope applications get updated to support dynamic scaling and that you can somehow make this transition easier for developers, so we get great visuals when working on multi-monitor setups with mixed pixel densities.
Cheers!
We’re working on it!
https://blogs.technet.microsoft.com/askcore/2016/08/16/display-scaling-changes-for-the-windows-10-anniversary-update/
There are these 4 manifest configuration options for dpiAware; none, false, true, true/pm;
apparently both false and true result in blurred font rendering,
while none and true/pm result in sharp fonts but wrong window decoration scaling.
This does not seem to be documented anywhere and the logic behind it is obscure.
Why isn’t there simply a combined mode to achieve what is now supposed
to be enabled with a separate API (EnableNonClientDpiScaling)?
And why, in the first place, do false and true yield blurry fonts at all;
why, rather than scaling up the rendered text, can’t Windows scale the
font size first (under the hood, if DPI-scaling is effective), then render properly?
Adding to my previous comment:
Some users of my application report that the font blurring does not occur if they use MacType for font rendering instead of ClearType. So obviously the blurring is not an inevitable consequence, and not even anchored in the Windows core system.
Please fix ClearType to render fonts properly in auto-scaled windows.
Scaling for PowerPoint 2016 was supposed to be fixed by now?
See “Enable system scaling for PowerPoint 2016 on Windows 10 version 1607” according to this site: https://support.office.com/en-us/article/Office-apps-appear-the-wrong-size-or-blurry-on-external-monitors-bc9f7279-4e42-4b15-a949-46ab8bcfe44f?ui=en-US&rs=en-US&ad=US&fromAR=1
I have updated PP2016 and to W10 version 1607 get PP2016 is still not rendering correctly on my external monitor. What gives?! Anyone else experiencing the same? Was the fix not implemented with W10 version 1607?
I’m still having the same problem as above for all the Office 2016 suite.
Funny that my inbox in Outlook is blurry, while the file explorer is sharp as a knife on my external monitors.
Good Day!
If a .RDP icon is saved to a desktop it will not function/open when it is clicked on nor will it allow you to edit it, if custom scaling is initiated in Windows 10 via: Control Panel, Display, Custom Scaling Level, and a custom number like 115% is keyed in.
So the desktop can and will custom scale to 115%. However, if a remote desktop connection is saved to the desktop, clicking on the icon has no response, and it cannot be edited.
If custom scaling is turned off, or a standard scaling entry like 125% is chosen, the .rdp icon will open and prompt for login info and it can be edited, so it will function as normal. I have tested this on several Windows 10 systems.
I unfortunately have some ACT! users that need a more custom scaling like 115% to get ACT! to display everything properly.
My first investment in a HD screen on a 15″ notebook which I thought would be great. has been not so great given that if you keep DPI at 100% everything looks great, but some text is far too small for my 50 something eyes. then I raise DPI to 125% and most things look great but some menu’s, older programs and their menu’s look blurry, which hurt my eyes again. Of course my Wife is having worse problems running similar resolution and 150% DPI and felling like Office was not even aware of how to deal with this issue completely. I feel bad I even bought her such a HD resolution notebook now, thinking she would have been happier with a 1366 X 768 notebook or something similar. My Daughter a huge Apple Mac fan does have a advantage from what I can see, which is I can see her notebook screen better than mine even with higher resolution and DPI settings. It looks better, all apps appear better and in general Apple must have put the screws to their native app developers within Apple to make scaling work perfect. I hope eventually Windows 10 and its ecosystem can copy this success.
With all the effort to address “Large Monitors” by scaling “up”, the behavior is now often quite “broken” when the reverse is true.
I have a six monitor setup for my desktop. All the monitors are 1080p. All is good “except” when I RDP into a machine with a “high-resolution” monitor. Then “all” is “bad”!
From what I can “infer” the remote-deskop scaling fixes are not doing what is “appropriate”. I.e., the rdp-server is windows-10, the rdp-client is windows 8.1 (because for various reasons not all machines should be upgraded in our environment).
Without understanding which side determines the remote computers DPI settings it is a little hard to determine what is happening.
However, the “appropriate” answer is that the RDP-server video monitor device should be reporting the resolution provided by the RDP client AND the “dpi” scaling desired by the RDP client.
What appears to be happening is that the RDP-server reports the monitor devices (6), but DOES NOT provide client-side information about the monitor-scaling. So the apps running on rdp-server see SIX monitors, but (in my case) scale them all using the “scaling-settings” for the remote-computer’s monitor setup.
In and of itself, this would “all be ok” except that the Control-Panel for Display Settings will NOT allow any display settings to be changed from a Remote Desktop Connection – which is super broken.
So I have a horrible scenario of needing to walk to the physical-remote-machine, login in, set the display resolution to 100% (making it unreadable on the high-resolution monitor of the remote machine). Then logout.
Then go to the client-machine with 6x1080p monitors and login. Only by doing that will the client see the correct scaling for the client.
What is “appropriate” is to allow the RDP client to not only report the number of monitors and their resolution, but to also allow it to set the scaling to be used by the RDP server video driver setup.
In other words, the “changes” made to support “high-resolution” monitors in RDP are “half-correct”. Currently the address the problem of a RDP-client that is high-resolution (3860x…) etc by scaling up. But I, for the life of me, can’t get them to override the remote side’s scaling down of simply scaling off.
So what I get when connecting to a remote Windows 10 computer with a high-resolution monitor where the remote machine has defaulted to something like scaling 150%, is that my local RDP client with 1080p monitors at 100% scaling gets all the RDP client content scaled monstrously large making it totally unusable. In some cases you cannot even access critical buttons because the window is so large it is off screen and cannot be adjusted.
I am working on one of the UWP applications. I have found that if i run the application on my desktop, in the task manager menu, the icon of my app is appearing blurred. On analysis i found that, its only the Square44x44Logo.scale-100.png which is getting reflected over there. The icon that i am providing is perfect but i am not able to understand why it is getting blurred in the task manager menu. I also found that the icon i am using has few circles which is really small hence is not clear. Please guide me with some suggestion.
I hope this is still being worked on and will improved. I’m newly on Office 365 and the fuzziness with Office applications, Word and Outlook in particular, is pronounced and frustrating. I’m using it with a new ASUS laptop and two high-end external monitors. Everything else looks great. The Office 365 apps are the outliers.
Hi,
Windows 2008R2 has had its RDP “dpi scaling” hotfix.
W2012R2 as well : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\IgnoreClientDesktopScaleFactor
Since everything RDP dpi scaling seems to require a hotfix, when will we get the one for W2016 so we can change dpi scaling at will ?
Ops Manager 2016 interface does not scale.
Sorry, but it’s pathetic that there is no possibility to properly scale the aspect of Windows that is literally staring me in the face every time I start Windows. When my high pixel density laptop is connected to my lower pixel density monitor, the desktop icons I see are microscopic on the laptop screen. I can change the size of “text, apps, and other items” for each monitor, which is nice/essential, but that has no affect on the desktop icons. I can choose a larger size for icons on both screen, but then they look ridiculous on one or the other. I can also use custom scaling (at my own risk) to set a larger text size for desktop icons, but that is for both monitors, doesn’t change the icons themselves, and is accompanied by warnings that some software (which we are now apparently required to call “apps”) may not work well with that setting. Sad.