Recommended Posts

HI

I'm brand new to this forum, so please bear with me. After quite a bit of on-line research, I discovered that it is possible to change the default system faults in xp by entering new values for "MS Shell Dlg" and "MS Shell Dlg2" in the registry editor. (HKEY_LOCAL_MACHINES\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes).

I changed "Microsoft Sans Serif" to "Calibri" for "MS Shell Dlg" value, and "Tahoma" to "Segoe UI" for "MS Shell Dlg2". Well, the Calibri one worked great...everywhere I used to see the dreaded Microsoft sans is now cool, clean, Calibri. However, Segoe UI barely shows up anywhere in the system. Tahoma still seems to be everywhere, including the "system tasks, file and folder tasks," etc. Segoe UI only shows up in a few drop-down menus (like in the "appearances" dialog box) and the occasional (seemingly random) menu tab.

Is there some other place that needs to be changed to give Tahoma the burial it so richly deserves? You can't delete it from the fonts folder (I made a back-up copy and tried- nothing doing). Maybe I'm obsessing too much, but I really don't like Tahoma! :wacko:

  dreamz said:
have you tried overwriting the tahoma font with a calibri one renamed to 'tahoma' (you may need to edit the actual font to change the name)?

Would that work? Would I just create a copy of the calibri font (or whatever I want to replace tahoma with) and rename it? Also, if I put it in the fonts folder, there's already a "tahoma" in there and I can't remove it.

Ihave attached a screen shot showing the mix of fonts. Notice Tahoma still showing up on the left-hand links menu. The other image shows the advanced appearance window...notice that Segoe UI shows up here.

Thanks.

post-221556-1178035882_thumb.jpg

I create a reg file to change my default font to Segoe UI (size 8) everywhere on XP ... But something I don't get it it's not here (HKEY_LOCAL_MACHINES\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes)

That you can modify the default font ... cos with my reg file I modify [HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics] and change the code for :

"CaptionFont"

"IconFont"

"MenuFont"

"MessageFont"

"SmCaptionFont"

"StatusFont"

:whistle:

  bentonton said:
I create a reg file to change my default font to Segoe UI (size 8) everywhere on XP ... But something I don't get it it's not here (HKEY_LOCAL_MACHINES\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes)

That you can modify the default font ... cos with my reg file I modify [HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics] and change the code for :

"CaptionFont"

"IconFont"

"MenuFont"

"MessageFont"

"SmCaptionFont"

"StatusFont"

That's nice to know, but I know nothing about changing code...it took a bit of investigation just to find the "easy" registry hacks. The ones in "FontSubstitutes" simply consisted of typing in the font name, there was no code involved.

Edited by leafdesigner
  leafdesigner said:
That's nice to know, but I know nothing about changing code...it took a bit of investigation just to find the "easy" registry hacks. The ones in "FontSubstitutes" simply consisted of typing in the font name, there was no code involved.

Me again...I took a look at the font codes in the registry under "WindowMetrics". I was at least able to tell which ones were still Tahoma. It looks like "SmCaptionFont" is the only one. Would that possibly explain all the instances of Tahoma still on my system? However, I'd still be uncomfortable changing the code. Any advice?

  martin10018 said:
The settings in 'advanced appearance' overwrite the registry values. You must change all fonts in 'a a' also.

Yes, I am a aware of the advanced appearance settings...I changed those long ago. It was only after that when I noticed Tahoma was still present. I changed every possible font in advanced appearance, plus the fonts in MS Shell Dlg & MS Shell Dlg2. Tahoma is still everywhere (see screen shot above). So obviously there is still some hidden location that insists on Tahoma being applied to certain system windows, etc.

  leafdesigner said:
Yes, I am a aware of the advanced appearance settings...I changed those long ago. It was only after that when I noticed Tahoma was still present. I changed every possible font in advanced appearance, plus the fonts in MS Shell Dlg & MS Shell Dlg2. Tahoma is still everywhere (see screen shot above). So obviously there is still some hidden location that insists on Tahoma being applied to certain system windows, etc.

Dumb question: Did you reboot after changing MS Shell Dlg?

I'm also having troubles changing a font. After installing a theme the font used for directory trees and file names as well as icons on the desktop has changed to "trebuchet ms". I've the only instance where i can still find "trebuchet ms" being mentioned is the "WindowsMetric" section in the registry, and there it's found under "IconFont". Is there a way to change this font without hacking the hex code in the registry? Thx.

  elpres said:
I'm also having troubles changing a font. After installing a theme the font used for directory trees and file names as well as icons on the desktop has changed to "trebuchet ms". I've the only instance where i can still find "trebuchet ms" being mentioned is the "WindowsMetric" section in the registry, and there it's found under "IconFont". Is there a way to change this font without hacking the hex code in the registry? Thx.

Sometimes when I install a new theme, fonts change as you described and I can usually make those changes in "advanced appearance." However, it doesn't always work. Right now I'm using Microsoft's new Zune desktop theme, and I changed all the fonts to Calibri. However, the font in the task bar still shows up as Tahoma. In other themes, the taskbar font will change to whatever is called out under "icon" in aa. So, there seems to be no rhyme or reason to it all. And after all this, I still have Tahoma in too many places.

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

    • No registered users viewing this page.
  • Posts

    • Finally the tasteless sound is replaced with the good old pleasant sounding one.
    • Surface Pro 11 and Laptop 7 get big firmware updates that fix shutdowns, black screens, more by Taras Buria Microsoft has released major firmware updates for some of its ARM-powered Copilot+ PCs. The Surface Pro 11 and the Surface Laptop 7 can now download the June 2025 firmware updates. These updates address a wide range of issues, including abrupt shutdowns when playing Netflix, black screen flashes, bugs with the Slim Pen haptics in OneNote, incorrect battery indication on the taskbar, and various performance improvements. Here are the changelogs for both devices: Surface Pro 11 Surface Laptop 7 Reliability: Improves system stability and reduces the frequency of unexpected shutdowns or the occurrence of a black screen while watching Netflix. Mitigates the issue that could cause screen flashing or a blank display during power state transitions. Improves the touch experience by resolving an issue where touch functionality could be lost after the device remained in Sleep mode for an extended period. Addresses an issue with Slim Pen losing haptic or Side button functionality in Microsoft OneNote. Resolved an issue where the battery icon incorrectly displayed the device as plugged in after waking from Sleep mode, even when it was not connected to a power source. ​ Performance and usability: Resolves the issue that caused authentication failures while using Windows Hello when waking from Sleep mode. Improves camera stability by reducing unexpected crashes and addressing issues, including freezing in video calls when HDR is enabled, errors when launching the Camera app or taking photos, and problems switching between front and rear cameras in some apps. Mitigates an issue where the Settings app could crash when setting up Fingerprint recognition. Interoperability: Resolves connectivity issues that caused the device to lose wired network access or fail to detect external monitors when connected via USB-C. Reliability: Improves overall stability, reducing occurrences of unexpected crashes and error screens. Reduces the occurrence of crashes during audio streaming sessions. Minimizes display timeout events and reduces the frequency of recovery cycles. Resolves an issue that caused the screen to remain black when resuming from Sleep mode. Performance and usability: Addresses an intermittent audio disruption experienced during video playback with Bluetooth headsets. Resolves a problem that caused Teams audio to drop during transitions between Bluetooth and built-in speakers. Addresses a startup issue that prevented USB Type-A devices from being recognized on the first boot. Interoperability: Resolves an issue introduced in the April 2025 release that prevented Thunderbolt 4 monitors from functioning when connected to the host device. You can get these updates by heading to Settings > Windows Update. Like Windows updates, Surface firmware releases are cumulative, which means a single download contains every update released so far. While the latest firmware updates for the Surface Pro 11 and the Surface Laptop 7 do not contain any known issues, keep in mind that firmware is not uninstallable, so back up important data to keep it safe before updating. You can find release notes for the Surface Pro 11 here and the Surface Laptop 7 here. Note that these updates are only available for Snapdragon-based versions, not those with Intel processors.
    • Here’s some history of this nonsense for people with short memories. https://www.neowin.net/amp/windows-next-hate-is-nothing-new/
    • 7 worked because vista cleared the way for it. Hardware manufacturers stopped making the “vista capable” machines, the updated secure drivers were released, and the issue with software manufacturers making everything with admin privileges was sorted. Vista took the reputational damage to do what was necessary so that 7 could be beloved.
    • You don’t remember the people who swore they were going to stay on 98se/2k because of windows xp’s “fisher price” interface/bloat.
  • Recent Achievements

    • One Month Later
      Jdoe25 earned a badge
      One Month Later
    • Explorer
      Legend20 went up a rank
      Explorer
    • One Month Later
      jezzzy earned a badge
      One Month Later
    • First Post
      CSpera earned a badge
      First Post
    • One Month Later
      MIR JOHNNY BLAZE earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      617
    2. 2
      ATLien_0
      277
    3. 3
      +FloatingFatMan
      178
    4. 4
      Michael Scrip
      151
    5. 5
      Steven P.
      117
  • Tell a friend

    Love Neowin? Tell a friend!