Weird fonts on Windows Server 2022

Windows Terminal version (or Windows build number)

1.10.1933.0

Other Software

Fresh install of Windows Server 2022 Evaluation, straight from https://www.microsoft.com/en-us/evalcenter/. Did not yet check for updates.

Steps to reproduce

Install latest preview appxbundle using Add-AppxPackage.
Running Windows Server on VMWare Workstation 16.1.2 build-17966106.

Expected Behavior

This is how cascadia code normally looks.

Actual Behavior

This is what I got. Doesn't quite seem right.

This looks it might be the same thing as #11017.

Frank M (@faxx1080)

This is wild that we got the same report 3 times in a week. Frank M (@faxx1080) what font are you using in the Terminal? What DPI scaling?

Hi Mike! I was using the default font that comes with Windows Terminal, Cascadia Code, and did not change any settings. I was using 100% DPI scaling; unchanged from out of box defaults (in a VMWare VM, running on a 96 DPI physical monitor).

**I'm not 100% sure it was Cascadia Code; it was whatever font is the default after installing the Appx package.

Note that I did this on the out of box Administrator account which has UAC turned off.

Okay this is wild. If you go into something like Microsoft Word, or anything that has a font picker, and go through that list, does "Cascadia Code" appear in that list? And does it appear in the dropdown list in the Terminal? We just got an internal report of the same thing that suggested that the font was uninstalled?

I'm having the same issue on a recently installed, non-domain joined, Windows Server 2022 Standard (version 21H2, build 20348.202) VM. It sure seems like whatever the default font is just doesn't get installed.

The Font face field in the Terminal appearance settings is just empty for the profile. It's also not listed in the picker. I haven't tried to make any settings changes yet.

WordPad doesn't show any Cascadia related fonts in the list.

I installed the Microsoft.WindowsTerminal_1.10.2383.0_8wekyb3d8bbwe.msixbundle via Add-AppxPackage. The only other things I currently have installed on this box are Pwsh 7.1.4, the latest VS Code (user install), and VMware Tools 11.1.

One more note. I had previously accidentally installed the Microsoft.WindowsTerminalPreview_1.11.2421.0_8wekyb3d8bbwe.msixbundle package which I uninstalled after realizing it was the preview instead of the release.

The Font face field in the Terminal appearance settings is just empty for the profile. It's also not listed in the picker.

WordPad doesn't show any Cascadia related fonts in the list.

WHAT THE

That's WILDLY unexpected, but definitely explains why you're seeing what you're seeing. It doesn't make sense, but that at least explains it. The Cascadia family of fonts should be shipping in our package:

terminal/src/cascadia/CascadiaPackage/Package.appxmanifest

Lines 140 to 149 in 6268a47

    
           <Extensions> 
        
             <uap7:Extension Category="windows.sharedFonts"> 
        
               <uap7:SharedFonts> 
        
                 <uap4:Font File="CascadiaCode.ttf" /> 
        
                 <uap4:Font File="CascadiaCodeItalic.ttf" /> 
        
                 <uap4:Font File="CascadiaMono.ttf" /> 
        
                 <uap4:Font File="CascadiaMonoItalic.ttf" /> 
        
               </uap7:SharedFonts> 
        
             </uap7:Extension> 
        
           </Extensions>

But if they're not getting installed when you install the Terminal, then a bunch of stuff will break. We pretty consistently rely on those fonts existing.

Frank M (@faxx1080)

but doesn't appear in C:\Windows\Fonts; nor does it appear in the old Fonts control panel.

Frank M (@faxx1080): IIRC, the old fontext.dll enumerated the registry itself directly rather than going through GDI or DirectWrite. So it would not know about "per user" fonts, unless additional work was done to it 🤔. I think the shell verb "Install" (forget which OS version this happened) now installs fonts into %LOCALAPPDATA%\Microsoft\Windows\Fonts\ (e.g. c:\Users\fdwr\AppData\Local\Microsoft\Windows\Fonts\NotoColorEmoji.ttf) using Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts, whereas "Install for all users" installs to the old c:\Windows\Fonts\ using Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts.

Use nearby fonts for font fallback (#11764)

Problem was solved for me on 2 Server 2022 installs after installing the Cascadia Code fonts: https://github.com/microsoft/cascadia-code

Use nearby fonts for font fallback (#11764)

Another attempt at fixing nearby font loading (#12904)

Navigation Menu

Repository navigation

Weird fonts on Windows Server 2022 #11032

Windows Terminal version (or Windows build number)

Other Software

Steps to reproduce

Expected Behavior

Actual Behavior

36 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	<Extensions>
	<uap7:Extension Category="windows.sharedFonts">
	<uap7:SharedFonts>
	<uap4:Font File="CascadiaCode.ttf" />
	<uap4:Font File="CascadiaCodeItalic.ttf" />
	<uap4:Font File="CascadiaMono.ttf" />
	<uap4:Font File="CascadiaMonoItalic.ttf" />
	</uap7:SharedFonts>
	</uap7:Extension>
	</Extensions>

Weird fonts on Windows Server 2022 #11032

Description

Windows Terminal version (or Windows build number)

Other Software

Steps to reproduce

Expected Behavior

Actual Behavior

Activity

j4james commented on Aug 25, 2021

zadjii-msft commented on Aug 26, 2021

faxx1080 commented on Aug 26, 2021

faxx1080 commented on Aug 26, 2021

zadjii-msft commented on Aug 30, 2021

rmbolger commented on Sep 2, 2021

zadjii-msft commented on Sep 2, 2021

36 remaining items

fdwr commented on Sep 10, 2021

elevul commented on Nov 23, 2021

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions