ClearType and Segoe UI - Why does Microsoft hate us?


Recommended Posts

Edit: new solution here: https://www.neowin.net/forum/topic/890802-windows-aero-tahoma-font/

Well, I think it's fair to say that Microsoft has put those of us who aren't fans of ClearType in quite a situation, and the key to that is Segoe UI. ClearType really doesn't agree with my eyes, it's not an option for me to have it enabled - the only font that it actually makes look good is Segoe UI. So I turn it off and ironically now Segoe UI is the only font that looks absolutely horrible, because it was obviously created FOR ClearType - it's very, very rough without it and the standard Windows smoothing makes it look overly fuzzy and blurry.

So what options do I have? I can turn off all smoothing, but that just makes things worse - Segoe UI looks horrible, like a 1980s video game font, and now everything else that is bold or larger size looks rough and pixelated too. I love the XP-style smoothing that was carried over to Vista and 7, it works and makes things look good unlike ClearType which adds additional colors. So that's not an option either.

My only other option is to try to eliminate Segoe UI. I can change all the fonts to Tahoma 8pt from Personalize -> Window Color -> Advanced Appearance Settings. But that hardly changes half the text out there, Segoe UI is still everywhere. I can eliminate more of it by switching to the Classic theme, which I have, and that takes care of about 70% of it maybe but it's still in a LOT of places.

So my last resort is to go into the registry and replace all Segoe UI fonts with something else. Ideally that would be Tahoma 8pt, which is XP's and 7's Classic theme default font. However, the default system font is Segoe UI 9pt and while you can change the font itself, you cannot change the size. So, after doing that all Segoe UI becomes Tahoma 9pt, which is significantly larger than Tahoma 8pt and that not only looks bad but it messes up a lot of applications where the text cannot fit in well. So I end up changing it to MS Sans Serif which is a system font that does not have a 9pt size, so it defaults to 8pt and it looks somewhat normal. That's my only option really - all the other fonts look too ridiculous and/or are too big at 9pt.

So I'm thinking I finally solved this - it doesn't look nearly as well as Tahoma 8pt, but at this point I'm fine with that. The problem though is that MS Sans Serif is a .fon font so it's impervious to ALL smoothing - so whenever I'm online and there is something written in larger Segoe UI or wherever 9pt+ of it is present in the system, Windows defaults to MS Sans Serif the larger sizes of which look really bad un-smoothed. And even though it is 8pt, it's just not the intended system font for the OS, so every now and then there are irregularities. The Windows 7 calculator, for instance, does not agree with it, so I've been using Windows XP's calc.exe on Windows 7...

But at this point there is no other solution, so I'm just gonna live with it until one of two things happen - Microsoft gives us the option to change the system font to Tahoma 8pt or another font that does not look horrible without ClearType, which is about 1% likely to happen, or until the regular smoothing gets improved to be able to handle non-ClearTyped Segoe UI and make it look good. I think there's a high probability the latter will happen actually - I'm pretty sure I read something about a significant improvement in smoothing coming with the final version of .NET Framework 4.0 but we'll see...

Anyways, I don't know why I'm posting this, I know there isn't a solution other than the one I described. And I know from spending a few days googling this issue and trying to figure out a solution, that there are a lot of people in a similar situation. So why Microsoft would force this on us is beyond me. There are a ton of people out there who don't like ClearType, but like traditional smoothing, and there just isn't a viable option for us at this point. When Vista came out most people were like oh well, screw it I'll just stick with XP for now they'll fix it eventually. Now 7 is out, the pressure is there to move on, people are getting 4GB+ RAM, DirectX 11 is out and this issue is still there.

Blah, sorry for the long pointless post, I just spent a few days trying to come up with a solution and that's all I got, so... Just wanted to post something somewhere about it I guess.

Edited by Colin-uk

The XP style smoothing is ClearType. Unless you're referring to the greyscale anti-aliasing which dates back to NT4/Win95. The greyscale rendering won't be improving much, since if it was going it it would have happened sometime in the last decade or so.

Have you tried adjusting the ClearType settings? you shouldn't be seeing the colour fringes unless you're looking at the monitor on a bad angle or your eyesight is different to the majority of the population (which does happen)

I did exactly the same as you OP. Changed all my fonts to Tahoma in Appearances settings and the registry and turned cleartype off, which fixes about 90% of it. Action Center and similar windows are still in segoe/cleartype tho, but thankfully I don't look at those screens much. Just dealing with some cut-off text can be a bit annoying yes :(

The XP style smoothing is ClearType. Unless you're referring to the greyscale anti-aliasing which dates back to NT4/Win95. The greyscale rendering won't be improving much, since if it was going it it would have happened sometime in the last decade or so.

Have you tried adjusting the ClearType settings? you shouldn't be seeing the colour fringes unless you're looking at the monitor on a bad angle or your eyesight is different to the majority of the population (which does happen)

Yes, I was referring to the gray-scale AA, the one you can uncheck from System -> Advanced -> Performance. What you're saying makes sense... I hope they come up with some sort of an alternative though. For instance, an option to enable ClearType ONLY on Segoe UI, but disable it on everything else, that would be perfect. Or offer Tahoma 8pt. as an alternative, which I think is much less likely.

I've tried adjusting it of course, and some combinations look much better than others, I can manage to make Segoe UI look great, but as soon as I open a web page everything else that ClearType touches is quite literally a pain to look at. :(

I did exactly the same as you OP. Changed all my fonts to Tahoma in Appearances settings and the registry and turned cleartype off, which fixes about 90% of it. Action Center and similar windows are still in segoe/cleartype tho, but thankfully I don't look at those screens much. Just dealing with some cut-off text can be a bit annoying yes :(

Yep... I might switch to Tahoma as well. Pt. 9 looks enormous, but it's better to deal with that than large non-smoothed pixelated MS Sans Serif .fon from the days of Windows 3.1... So many people have done this now, I can't believe we have to be dealing with this crap...

Here's another guy who asked Microsoft the exact same question:

http://social.technet.microsoft.com/Forums...77-18ff1803c9ce

"I will report it to our feedback team"... Good luck with that.

Edited by WinClassicFan
Yes, I was referring to the gray-scale AA, the one you can uncheck from System -> Advanced -> Performance. What you're saying makes sense... I hope they come up with some sort of an alternative though. For instance, an option to enable ClearType ONLY on Segoe UI, but disable it on everything else, that would be perfect. Or offer Tahoma 8pt. as an alternative, which I think is much less likely.

I've tried adjusting it of course, and some combinations look much better than others, I can manage to make Segoe UI look great, but as soon as I open a web page everything else that ClearType touches is quite literally a pain to look at. :(

...

This issue can get muddled with some of the terms, for example ClearType is really just the sub-pixel anti-aliasing, it's applied equally to Segoe and Tahoma, the only difference in their rendering is due to hinting. And the hinting is pretty much the same between no AA, greyscale AA and sub-pixel AA.

The difference doesn't come from the hinting or the anti-aliasing used, it comes entirely because Segoe and Tahoma are 2 different fonts that looks different.

don't know if this is relevant but you can change the system font, just not the size.

I hate the Segoe font as well so I entered the following into my registry...

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]

"Segoe UI (TrueType)"=""

"Segoe UI Bold (TrueType)"=""

"Segoe UI Italic (TrueType)"=""

"Segoe UI Bold Italic (TrueType)"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes]

"Segoe UI"="Tahoma"

I still wasn't happy with Tahoma at 9pt but found out there is a 'light' version of Segoe called

'Segoe UI Light" and have been happy ever since. Replace "Tahoma" with any font you like.

Hello Everyone,

I'd like to offer my solution, which, I believe, is an improvement upon that which phatphunky offered. phatphunky's solution is exactly the same as NoSegoe, which I explain in the next paragraph. However, I have figured out a way to use Tahoma at 8pts.

In Windows 7 and Vista, one has the option to change portions of the user interface (UI) to whatever font he or she desires. Unfortunately it is not an option to change certain parts of the interface. After having thoroughly searched for a solution to change all instances of the Windows 7 UI font from Segoe UI to Tahoma (the old default in previous versions of Windows), I eventually found Steve Halpern?s NoSegoe solution. It simply uses the Registry to specify Tahoma (or any other font of your choosing) an alternative to Segoe. More information on NoSegoe can be found here: http://steve.fsxtreme.com/blogs/2008/01/16...rtype-on-vista/. While this completely clears up the interface on screens that cannot properly render Cleartype and Segoe UI, things still look awkward. This is due to the fact that Segoe is generally used at a font size of 9pts, whereas Tahoma was always displayed at 8pts.

I was able to create my own solution to this problem by modifying the default Aero theme. The only changes made in my theme were to the font settings. All instances of Segoe UI where changed to Tahoma. Additionally, all 9pt instances (which constitutes most of them) were set to 8pts, the others were left at their default font size. The Aero theme was modified using Vista Style Builder (http://vistastylebuilder.com/).

My fixed Aero theme can be used by itself, however it will only replace instances of Segoe in the Windows user interface. External programs that are hard coded to use Segoe UI, even ones included with Windows 7, such as Calculator and Resource Monitor, will continue to use Segoe. For best results, and in order to completely eliminate Segoe UI, I recommend using NoSegoe in conjunction with the fixed Aero Theme. The Aero Theme (Fixed) package only works with Windows 7, however NoSegoe works with both Vista and 7.

Attachments (Alternative Links)

NoSegoe: http://www.megaupload.com/?d=ADESI1N8 (Updated to fully remove Segoe UI)

Aero Theme (Fixed): http://www.megaupload.com/?d=EX347PJL

NoSegoe.zip

Aero_Theme_Fixed.zip

It's a matter of opinion. You might not like it but it looks like the majority of computer users love cleartype. Maybe you have ****ty hardware. It's designed for LCD monitors in mind, not CRT. On CRT, everything would look blurry or badly rendered like you are describing, so are you using a CRT monitor at all?

I don't know about Windows 7, but for me I've been using GDI++ as I cannot stand ClearType's normal rendering. Everything looks so thin and on my 26" @ 1920x1200 everything is a pain to read and focus on.

Here is wikipedia with ClearType:

cleartype.png

and here it is with GDI++:

gdi.png

Can ClearType on Windows 7 get any where near what GDI++ does?

there is something wrong with ur cleartype.. im sorry.. its not like that on my pc and im using default cleartype..

but yes i did notice if u go to control panel to setup the cleartype it messes it up completely and it becomes weird..

leme show u my cleartype pic ..

and no!!.. cleartype is not blurry on a CRT.. i use a CRT and its fine..

and one more thing.

i use internet explorer.. no firefox for me.. i used it in the vista era.. not anymore as internet explorer is good enough.

post-285248-1261036535_thumb.jpg

cleartype%20differences.png

All 3 of those lines use "ClearType", yet all 3 look different, there's more to rendering text that just what kind of AA there is.

...

Can ClearType on Windows 7 get any where near what GDI++ does?

No, you can't make it that ugly.

and no..

i would recommend.. dont use the control panel thingy..

ull notice a weird thing after u change the settings..

when the glass of a window has text underneath it will show weird red and blue color around it..

but it wont if u dont touch the control panel settings for cleartype.

Have you tried using "Adjust ClearType text" in the control panel? You should be able to make it a bit closer to GDI++.

Sorry should of said, I'm on XP. I was just wondering for the future.

No, you can't make it that ugly.

How is making the text more readable "ugly"?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft: Windows 11 KB5094126, KB5093998 finally stops trusting a critical system threat by Sayan Sen This week Microsoft released the Patch Tuesday updates for June 2026 with KB5094126 on Windows 11 25H2, 24H2, and KB5093998 on Windows 11 23H2. On Windows 10 22H2 it's under KB5094127. Alongside the announced release notes for the new builds, Microsoft has revealed another change that is coming to Windows with these new releases. It has been confirmed that custom folders are getting a significant change with the June 2026 updates as such folders or folder names defined by desktop.ini will no longer appear after this update is successfully installed. While you may inititally think this is a bug with the new release, Microsoft has stated that this is in fact "expected behaviour" in its new support article regarding this which Neowin spotted today while browsing. Essentially it's a security hardening measure such that custom folder presentations are treated as potentially unsafe whenever Windows is not sure about their origin and whether that desktop.ini folder can be trusted or not. Here is list of such untrusted files and folders: Files downloaded from the internet that carry Mark-of-the-Web (MOTW). Files copied from certain remote locations, such as some WebDAV or HTTP-based locations. Files on network paths that are not classified as intranet or trusted by zone policy. For those who may not be familiar, Desktop.ini is a special configuration file used by Windows to customize the appearance and behavior of individual folders. Basically Windows can read specific instructions stored in Desktop.ini instead of displaying every folder with the same default settings. This can be used to apply custom icons, thumbnail images, localized folder names, and such informational tooltips (infotip). The file can also influence certain folder-specific behaviors and properties. It is typically stored as a hidden system file within a folder that has been designated to support Desktop.ini customization. However, because Windows Shell automatically reads and applies these attributes whenever a customized folder is opened, they have historically (since the Windows XP days) presented an attack surface as a result of an unchecked buffer in the Shell component responsible for extracting custom attributes from Desktop.ini files. As such an attacker could create a specially crafted Desktop.ini containing a malicious or corrupted attributes and place it on a network share. So if a user were to browse that folder, Windows would automatically process the file, potentially triggering a buffer overflow. This could allow arbitrary code to run with the same permissions as the logged-in user. Hence a seemingly harmless folder could become a security risk when their contents are not properly validated. For admins and users alike looking to manage this behaviour, Microsoft has shared a few ways. One of them is to assign a trusted mark on the folder in case you are sure of its source. Secondly a policy can be used to revert back to the previous state. Finally, the MOTW can be removed too to indicate to Windows that this is a safe file. The company explains: Option 1: Add the source to Trusted Sites (Recommended) If the affected content is stored on a known internal or managed source, add that source to the Trusted Sites list. Once the source is treated as trusted, Windows processes desktop.ini from that source normally. This keeps the protection in place for other locations and is the lower-risk option. Option 2: Use policy to restore previous behavior Organizations that need broader compatibility can enable the policy Allow the use of remote paths in file shortcut icons.Enabling this policy restores the pre-June 2026 behavior for affected remote or untrusted scenarios. Option 3: Check for and remove the Mark of the Web (MotW) If the desktop.ini file has a Mark of the Web (MotW), Windows may treat it as coming from an untrusted source and block customization. Verify whether MotW is present and, if appropriate, remove it from the desktop.ini file. This can restore expected behavior, but should only be done for trusted content, as it removes the associated security protection. To remove the MotW tag, open PowerShell and run one of the following commands: For a single desktop.ini file: Unblock-File "C:\Your\Folder\Path\desktop.ini" For all desktop.ini files in a folder: Get-ChildItem "C:\Your\Folder\Path" -Recurse -Filter desktop.ini -Force | Unblock-File Microsoft has warned though against using a broad opt-out using the provided policy as it reduces protection against potentially malicious remote folder-customization content. As such the tech giant recommends trusting only controlled internal sources and keeping trust settings as strict as possible. You can check out the official support article here on Microsoft's website.
    • LAV Filters 0.82.0 by Razvan Serea LAVFSplitter is a multi-format media splitter that uses libavformat (the demuxing library from ffmpeg) to demux all sorts of media files. LAV Splitter is a Souce Filter/Splitter required to demux the files into their separate elementary streams. LAV Audio and Video Decoder are powerful decoders with a focus on quality and performance, without any compromises. Supported Formats: MKV/WebM, AVI, MP4/MOV, MPEG-TS/PS (including basic EVO support), FLV, OGG, and many more that are supported by ffmpeg! LAV Filters are based on ffmpeg and libbluray and is aimed to offer a all-around solution to perfect playback of file-based Media as well as Blu-rays. LAV Filters 0.82.0 changelog: LAV Splitter NEW: Support for demuxing Dolby Vision Enhancement Layer streams NEW: Support for Animated WebP images Changed: When demuxing Blu-ray discs, Dolby Vision metadata is available on the primary video stream LAV Video NEW: Support for Animated WebP images Changed: Hardware decoding support for DVDs has been removed Download: LAV Filters 0.82.0 | 15.5 MB (Open Source) View: LAV Filters Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • For some reason when EU forced Microsoft to allow users to change the default browser and search provider in Windows (also no ads for Office and the likes) - it was good. But when it comes to Apple - then it's bad. BTW, Apple would have gone out of business if Microsoft wasn't pressed by US government several decades ago. 😉
  • Recent Achievements

    • One Month Later
      Sopa flores earned a badge
      One Month Later
    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      506
    2. 2
      PsYcHoKiLLa
      207
    3. 3
      +Edouard
      156
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      79
  • Tell a friend

    Love Neowin? Tell a friend!