starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal suddenly can't find the font Cascadia Mono #15731

New Issue
Closed
opened 2026-01-31 04:46:47 +00:00 by claunia · 26 comments
claunia commented 2026-01-31 04:46:47 +00:00
Owner
Copy Link

Originally created by @johan-byggtjanst on GitHub (Oct 29, 2021).

Originally assigned to: @lhecker, @miniksa on GitHub.

Windows Terminal version (or Windows build number)

10.0.19043.1288

Other Software

No response

Steps to reproduce

Just starting the Terminal on Windows 10. Not running as admin.

Expected Behavior

A new terminal window

Actual Behavior

Got this error

`Unable to find the selected font "Cascadia Mono".

"Consolas" has been selected instead.

Please either install the missing font or choose another one.`

Originally created by @johan-byggtjanst on GitHub (Oct 29, 2021). Originally assigned to: @lhecker, @miniksa on GitHub. ### Windows Terminal version (or Windows build number) 10.0.19043.1288 ### Other Software _No response_ ### Steps to reproduce Just starting the Terminal on Windows 10. Not running as admin. ### Expected Behavior A new terminal window ### Actual Behavior Got this error `Unable to find the selected font "Cascadia Mono". "Consolas" has been selected instead. Please either install the missing font or choose another one.`
claunia commented 2026-01-31 04:46:49 +00:00
Author
Owner
Copy Link

@ChameleonDevil commented on GitHub (Oct 29, 2021):

I added a comment on Cascadia Code font repo for a solution on the font installation, for Windows Terminal and VS Code:

https://github.com/microsoft/cascadia-code/issues/594#issuecomment-954565361

Please check there, I have discovered "Cascadia Mono" to be missing (can't even get it reinstalled currently), but show there how to update Windows Terminal and VS Code to use "Cascadia Mono PL"

@ChameleonDevil commented on GitHub (Oct 29, 2021): I added a comment on **Cascadia Code font repo** for a solution on the font installation, for Windows Terminal and VS Code: > https://github.com/microsoft/cascadia-code/issues/594#issuecomment-954565361 Please check there, I have discovered "Cascadia Mono" to be missing (can't even get it reinstalled currently), but show there how to update Windows Terminal and VS Code to use **"Cascadia Mono PL"**
claunia commented 2026-01-31 04:46:49 +00:00
Author
Owner
Copy Link

@Peru-S commented on GitHub (Oct 30, 2021):

Same issue: Windows Terminal automatically closed due to Windows Update (no restarts).
Opening Terminal again resulted in "Could not find Cascadia Code" issue that OP raised.

On 21H1 19043.1288

(The other problem is that Terminal arbitrarily closes even if Windows Update is configured to restart at a later date: All other apps function properly)

@Peru-S commented on GitHub (Oct 30, 2021): Same issue: Windows Terminal automatically closed due to Windows Update (no restarts). Opening Terminal again resulted in "Could not find Cascadia Code" issue that OP raised. On 21H1 19043.1288 (The other problem is that Terminal arbitrarily closes even if Windows Update is configured to restart at a later date: All other apps function properly)
claunia commented 2026-01-31 04:46:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 1, 2021):

this is the thread

We've tracked this in other threads in the past, and we've done work to mitigate this before, but we didn't get all of it. Every time we push an update, more folks start running into this again. We've got an idea of what's wrong here - one of the code paths does the right thing for the SxS font lookup, and the other path doesn't, and that leads to this warning.

In the past, we used #9375 to track this. #9734 attempted to mitigate. #10305 tracked the version of this that caused a crash on startup.

So this was the first thread for the issue during this update, congrats.

IF YOU'RE HITTING THIS

Try "Repairing" the Terminal app, by going to "Settings > Apps > {whatever Terminal Install you have} > Advanced Options > Repair". This shouldn't delete your settings. (But "Reset" will, so be careful!)

If you comment some variation of "me too" in this thread, you will be removed from the selfhost program your comment will be minimized as spam, thanks.

@zadjii-msft commented on GitHub (Nov 1, 2021): ### this is the thread We've tracked this in other threads in the past, and we've done work to mitigate this before, but we didn't get all of it. Every time we push an update, more folks start running into this again. We've got an idea of what's wrong here - one of the code paths does the right thing for the SxS font lookup, and the other path _doesn't_, and that leads to this warning. In the past, we used #9375 to track this. #9734 attempted to mitigate. #10305 tracked the version of this that caused a crash on startup. So this was the first thread for the issue during this update, congrats. # IF YOU'RE HITTING THIS Try "Repairing" the Terminal app, by going to "Settings > Apps > {whatever Terminal Install you have} > Advanced Options > Repair". This shouldn't delete your settings. (But "Reset" will, so be careful!) <hr> <sub>If you comment some variation of "me too" in this thread, ~you will be removed from the selfhost program~ your comment will be minimized as spam, thanks. </sub>
claunia commented 2026-01-31 04:46:50 +00:00
Author
Owner
Copy Link

@Peru-S commented on GitHub (Nov 1, 2021):

I worked around by installing Cascadia manually. (Hopefully this message isn't marked as spam :)
I searched for this issue before (opening a new one ) / commenting here btw. So if possible please sticky this.
Also I wasn't sure if it was a Terminal issue or a Cascadia issue, so juggling between those two github repos as well.
This could avoid unintentional 'spam' comments.

@Peru-S commented on GitHub (Nov 1, 2021): I worked around by installing Cascadia manually. (Hopefully this message isn't marked as spam :) I searched for this issue before (opening a new one ) / commenting here btw. So if possible please sticky this. Also I wasn't sure if it was a Terminal issue or a Cascadia issue, so juggling between those two github repos as well. This could avoid unintentional 'spam' comments.
claunia commented 2026-01-31 04:46:50 +00:00
Author
Owner
Copy Link

@barkermn01 commented on GitHub (Nov 2, 2021):

I would also like to confirm this issue is now present in the Windows 11 Version after a windows update but I'm not sure if that is related or not I did not have this issue until a couple of days ago after a windows update, I'm currently running Terminal version 1.11.2921.0, I'm on the Insider program on the Beta Channel, so whatever this issue is it's now coming through to Windows 11 versions...

Windows 11 is currently on:
Edition Windows 11 Pro
Version 21H2
Installed on ‎27/‎08/‎2021
OS build 22000.258
Experience Windows Feature Experience Pack 1000.22000.258.0

I do have a Windows Update pending will update this message if this update resolves the problem for me...

@barkermn01 commented on GitHub (Nov 2, 2021): I would also like to confirm this issue is now present in the Windows 11 Version after a windows update but I'm not sure if that is related or not I did not have this issue until a couple of days ago after a windows update, I'm currently running Terminal version 1.11.2921.0, I'm on the Insider program on the Beta Channel, so whatever this issue is it's now coming through to Windows 11 versions... Windows 11 is currently on: Edition Windows 11 Pro Version 21H2 Installed on ‎27/‎08/‎2021 OS build 22000.258 Experience Windows Feature Experience Pack 1000.22000.258.0 I do have a Windows Update pending will update this message if this update resolves the problem for me...
claunia commented 2026-01-31 04:46:50 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 2, 2021):

In general: We don't really need to know anything more about OS version and Terminal version for this one. We've got a good idea of what's causing this.

The Windows 11 data point is a little interesting, we thought that the underlying bug in the OS for migrating the font files from one version to the next was fixed, but alas, it seems it also regressed since when it was first fixed in Windows 11. So this will continue to plague users at random till we fix this.

@zadjii-msft commented on GitHub (Nov 2, 2021): _In general_: We don't really need to know anything more about OS version and Terminal version for this one. We've got a good idea of what's causing this. The Windows 11 data point is a little interesting, we thought that the underlying bug in the OS for migrating the font files from one version to the next was fixed, but alas, it seems it also regressed since when it was first fixed in Windows 11. So this will _continue_ to plague users at random till we fix this.
claunia commented 2026-01-31 04:46:50 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Nov 3, 2021):

#11032's mitigation will likely mitigate this too.

@miniksa commented on GitHub (Nov 3, 2021): #11032's mitigation will likely mitigate this too.
claunia commented 2026-01-31 04:46:50 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 14, 2021):

This is still an issue and will continue to be an issue until we nail nearby font loading.

Notes from discussion:

But the heart of the issue is that our system collection contains a pointer to a font that is locked for deletion, because the app platform locked it for deletion since it's part of our package
We needed to do fallback when we failed to actually load the font, to a collection that doesn't have the issue

@DHowett commented on GitHub (Dec 14, 2021): This is still an issue and will continue to be an issue until we nail nearby font loading. Notes from discussion: > But the heart of the issue is that our system collection contains a pointer to a font that is locked for deletion, because the app platform locked it for deletion since it's part of our package > We needed to do fallback when we failed to actually load the font, to a collection that doesn't have the issue
claunia commented 2026-01-31 04:46:51 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 14, 2021):

:tada:This issue was addressed in #11764, which has now been successfully released as Windows Terminal Preview v1.12.3472.0.🎉

Handy links:

@ghost commented on GitHub (Dec 14, 2021): :tada:This issue was addressed in #11764, which has now been successfully released as `Windows Terminal Preview v1.12.3472.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.12.3472.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 04:46:51 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 14, 2021):

:tada:This issue was addressed in #11764, which has now been successfully released as Windows Terminal v1.11.3471.0.🎉

Handy links:

@ghost commented on GitHub (Dec 14, 2021): :tada:This issue was addressed in #11764, which has now been successfully released as `Windows Terminal v1.11.3471.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.11.3471.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 04:46:51 +00:00
Author
Owner
Copy Link

@srdjanjovcic commented on GitHub (Apr 13, 2022):

This is not fixed on Windows 10 in 1.13.10983.0

@srdjanjovcic commented on GitHub (Apr 13, 2022): This is not fixed on Windows 10 in 1.13.10983.0
claunia commented 2026-01-31 04:46:51 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 14, 2022):

Reopening because I found a flaw in my implementation.
In case people wonder how we're failing so hard at fixing this: It's partially my inability in figuring this out, but also partially because we're simply unable to repro this issue. All fixes are purely theoretic. Even my new fix is just made on an assumption (a pretty good one this time if I may say so). I'm really sorry about this! ☹️

@lhecker commented on GitHub (Apr 14, 2022): Reopening because I found a flaw in my implementation. In case people wonder how we're failing so hard at fixing this: It's partially my inability in figuring this out, but also partially because we're simply unable to repro this issue. All fixes are purely theoretic. Even my new fix is just made on an assumption (a pretty good one this time if I may say so). I'm really sorry about this! ☹️
claunia commented 2026-01-31 04:46:51 +00:00
Author
Owner
Copy Link

@tylerszabo commented on GitHub (Apr 14, 2022):

I'm not sure if it helps but the issue seems to be system-wide when it happens. This causes crashes in gVim when attempting to load "Cascadia Code" after Windows Terminal has updated on my Windows 11 box. I worked around using @Mindfulplays' suggestion to install manually.

I suspect the issue is less with loading the font incorrectly and something to do with installing the font incorrectly. I tend to be using the font somewhere at all times so perhaps there's some kind of issue with replacing it when it's being used in some way.

@tylerszabo commented on GitHub (Apr 14, 2022): I'm not sure if it helps but the issue seems to be system-wide when it happens. This causes crashes in gVim when attempting to load "Cascadia Code" after Windows Terminal has updated on my Windows 11 box. I worked around using @Mindfulplays' suggestion to install manually. I suspect the issue is less with loading the font incorrectly and something to do with installing the font incorrectly. I tend to be using the font somewhere at all times so perhaps there's some kind of issue with replacing it when it's being used in some way.
claunia commented 2026-01-31 04:46:52 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 14, 2022):

@tylerszabo Yes, we know that the actual underlying issue certainly isn't our fault. I'm not sure what the current state of an fix for that is (I can faintly remember hearing it's fixed in a newer Windows 11 build?), but in the meantime we'd of course want to fix it ourselves as quickly as possible.

@lhecker commented on GitHub (Apr 14, 2022): @tylerszabo Yes, we know that the actual underlying issue certainly isn't our fault. I'm not sure what the current state of an fix for that is (I can faintly remember hearing it's fixed in a newer Windows 11 build?), but in the meantime we'd of course want to fix it ourselves as quickly as possible.
claunia commented 2026-01-31 04:46:52 +00:00
Author
Owner
Copy Link

@ilor commented on GitHub (Apr 14, 2022):

Happened for me again on 1.13.10983.0 on Windows 10 21H2, making for roughly the fourth time in a year I had this. Some additional data points:

  • I've rebooted a few hours ago to install Windows updates
  • This didn't break right on startup. In fact I have two shell tabs open where the font is okay, and only now (a few hours later) opening a new tab of the same type complains about the Cascadia Mono being MIA.
@ilor commented on GitHub (Apr 14, 2022): Happened for me again on 1.13.10983.0 on Windows 10 21H2, making for roughly the fourth time in a year I had this. Some additional data points: * I've rebooted a few hours ago to install Windows updates * This didn't break right on startup. In fact I have two shell tabs open where the font is okay, and only now (a few hours later) opening a new tab of the same type complains about the Cascadia Mono being MIA.
claunia commented 2026-01-31 04:46:52 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 24, 2022):

:tada:This issue was addressed in #12904, which has now been successfully released as Windows Terminal v1.13.1143.🎉

Handy links:

@ghost commented on GitHub (May 24, 2022): :tada:This issue was addressed in #12904, which has now been successfully released as `Windows Terminal v1.13.1143`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.13.1143) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 04:46:52 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 24, 2022):

:tada:This issue was addressed in #12904, which has now been successfully released as Windows Terminal Preview v1.14.143.🎉

Handy links:

@ghost commented on GitHub (May 24, 2022): :tada:This issue was addressed in #12904, which has now been successfully released as `Windows Terminal Preview v1.14.143`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.14.143) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 04:46:53 +00:00
Author
Owner
Copy Link

@AlpineWeezl commented on GitHub (Oct 14, 2022):

Unfortunately, this issue still exists with completely updated system. I also did the reset as mentioned in the second post of this thread.

@AlpineWeezl commented on GitHub (Oct 14, 2022): Unfortunately, this issue still exists with completely updated system. I also did the reset as mentioned in the second post of this thread.
claunia commented 2026-01-31 04:46:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 25, 2023):

@lhecker You wrote:

because we're simply unable to repro this issue

Perhaps the steps below will help reproduce the issue. (Although @zadjii-msft mentioned you don't really need to know anything more about OS version, I should say I use Windows 11 ARM in a Parallels virtual machine on an M1 Mac).

STEP 1: Download and unzip Cascadia Mono PL:

# Download the archive file
$downloadsPath = "$Env:USERPROFILE\Downloads"
$zipFileName = "CascadiaCode-2111.01.zip"
$zipFilePath = "$downloadsPath\$zipFileName"
$url = "https://github.com/microsoft/cascadia-code/releases/download/v2111.01/$zipFileName"
Invoke-WebRequest -Uri $url -OutFile $zipFilePath

# Expand, then delete, the archive file
$expandedDirectoryPath = "$downloadsPath\CascadiaCode-2111.01"
Expand-Archive -Path $zipFilePath -Destination $expandedDirectoryPath
Remove-Item -Force -Path $zipFilePath

STEP 2: Copy and register the font such that it causes the issue in Windows Terminal:

# Ensure destination directory exists
$fontsDirectoryPath = "$Env:LOCALAPPDATA\Microsoft\Windows\Fonts"
if (-not (Test-Path $fontsDirectoryPath))
{
    $directory = New-Item -Force -ItemType Directory -Path $fontsDirectoryPath
}

# Copy font file
$fontFileName = "CascadiaMonoPL.ttf"
$fontFileSourcePath = "$Env:USERPROFILE\Downloads\CascadiaCode-2111.01\ttf\$fontFileName"
$fontFileDestinationPath = "$fontsDirectoryPath\$fontFileName"
Copy-Item -Path $fontFileSourcePath -Destination $fontFileDestinationPath

# Ensure the registry key exists
$fontsKey = "HKCU:\Software\Microsoft\Windows NT\CurrentVersion\Fonts"
if (-not (Test-Path -Path $fontsKey))
{
    $key = New-Item -Force -ItemType Directory -Path $fontsKey
}

# Add the registry key for the font file
$value = New-ItemProperty -Force -Name "Cascadia Mono PL Regular (TrueType)" -Path $fontsKey -PropertyType $type -Value $fontFileDestinationPath

STEP 3: Verify that Windows Terminal is not able to find the font.

STEP 4: Properly install the font such that it does not cause the issue in Windows Terminal:

(The Windows Shell should ask if you want to replace the 'Cascadia Mono PL Regular' font when you run the script below. You should answer Yes.)

# Create the Windows Shell's automation object and use the fonts namespace
$shell = New-Object -ComObject "Shell.Application"
$fonts = $shell.Namespace(0x14)

# Copy font file
$fontFileName = "CascadiaMonoPL.ttf"
$fontFileSourcePath = "$Env:USERPROFILE\Downloads\CascadiaCode-2111.01\ttf\$fontFileName"
$fonts.CopyHere($fontFileSourcePath, 20)

STEP 5: Verify that Windows Terminal is able to find the font.

STEP 6: Restart Windows.

STEP 7: Verify that Windows Terminal is again not able to find the font.

Hope this helps!

@ghost commented on GitHub (Feb 25, 2023): @lhecker You wrote: > because we're simply unable to repro this issue Perhaps the steps below will help reproduce the issue. (Although @zadjii-msft mentioned you don't really need to know anything more about OS version, I should say I use Windows 11 ARM in a Parallels virtual machine on an M1 Mac). **STEP 1**: Download and unzip Cascadia Mono PL: ```PowerShell # Download the archive file $downloadsPath = "$Env:USERPROFILE\Downloads" $zipFileName = "CascadiaCode-2111.01.zip" $zipFilePath = "$downloadsPath\$zipFileName" $url = "https://github.com/microsoft/cascadia-code/releases/download/v2111.01/$zipFileName" Invoke-WebRequest -Uri $url -OutFile $zipFilePath # Expand, then delete, the archive file $expandedDirectoryPath = "$downloadsPath\CascadiaCode-2111.01" Expand-Archive -Path $zipFilePath -Destination $expandedDirectoryPath Remove-Item -Force -Path $zipFilePath ``` **STEP 2**: Copy and register the font such that it causes the issue in Windows Terminal: ```PowerShell # Ensure destination directory exists $fontsDirectoryPath = "$Env:LOCALAPPDATA\Microsoft\Windows\Fonts" if (-not (Test-Path $fontsDirectoryPath)) { $directory = New-Item -Force -ItemType Directory -Path $fontsDirectoryPath } # Copy font file $fontFileName = "CascadiaMonoPL.ttf" $fontFileSourcePath = "$Env:USERPROFILE\Downloads\CascadiaCode-2111.01\ttf\$fontFileName" $fontFileDestinationPath = "$fontsDirectoryPath\$fontFileName" Copy-Item -Path $fontFileSourcePath -Destination $fontFileDestinationPath # Ensure the registry key exists $fontsKey = "HKCU:\Software\Microsoft\Windows NT\CurrentVersion\Fonts" if (-not (Test-Path -Path $fontsKey)) { $key = New-Item -Force -ItemType Directory -Path $fontsKey } # Add the registry key for the font file $value = New-ItemProperty -Force -Name "Cascadia Mono PL Regular (TrueType)" -Path $fontsKey -PropertyType $type -Value $fontFileDestinationPath ``` **STEP 3**: Verify that Windows Terminal is **not** able to find the font. **STEP 4**: Properly install the font such that it does not cause the issue in Windows Terminal: (The Windows Shell should ask if you want to replace the 'Cascadia Mono PL Regular' font when you run the script below. You should answer Yes.) ```PowerShell # Create the Windows Shell's automation object and use the fonts namespace $shell = New-Object -ComObject "Shell.Application" $fonts = $shell.Namespace(0x14) # Copy font file $fontFileName = "CascadiaMonoPL.ttf" $fontFileSourcePath = "$Env:USERPROFILE\Downloads\CascadiaCode-2111.01\ttf\$fontFileName" $fonts.CopyHere($fontFileSourcePath, 20) ``` **STEP 5**: Verify that Windows Terminal is able to find the font. **STEP 6**: Restart Windows. **STEP 7**: Verify that Windows Terminal is again **not** able to find the font. Hope this helps!
claunia commented 2026-01-31 04:46:53 +00:00
Author
Owner
Copy Link

@cmschlenke commented on GitHub (Aug 16, 2023):

If any poor soul has found their way here wondering why Windows Terminal can't find their font, let me assure you that this is actually not a Windows Terminal bug, or even a Windows bug. This behavior is caused by not having the font installed for all users. Follow these steps to remedy the problem... https://answers.microsoft.com/en-us/windows/forum/all/solution-installed-fonts-disappearing-after/146f4039-47c3-4017-a9b1-76f72badce39

@cmschlenke commented on GitHub (Aug 16, 2023): If any poor soul has found their way here wondering why Windows Terminal can't find their font, let me assure you that this is actually not a Windows Terminal bug, or even a Windows bug. This behavior is caused by not having the font installed for all users. Follow these steps to remedy the problem... https://answers.microsoft.com/en-us/windows/forum/all/solution-installed-fonts-disappearing-after/146f4039-47c3-4017-a9b1-76f72badce39
claunia commented 2026-01-31 04:46:54 +00:00
Author
Owner
Copy Link

@psxlover commented on GitHub (Oct 23, 2023):

I just run into this issue. Version 1.18.2822.0. Windows 10. According to the Microsoft Store Terminal was updated today.

The previous comment does not apply in my case, there is no Fonts folder in %appdata%..\Local\Microsoft\Windows.

What's even more confusing is that in "Fonts" they are "there" but are invisible until I hove over them with the mouse in which case only the names appear:
image
image

@psxlover commented on GitHub (Oct 23, 2023): I just run into this issue. Version 1.18.2822.0. Windows 10. According to the Microsoft Store Terminal was updated today. The previous comment does not apply in my case, there is no Fonts folder in %appdata%\..\Local\Microsoft\Windows. What's even more confusing is that in "Fonts" they are "there" but are invisible until I hove over them with the mouse in which case only the names appear: ![image](https://github.com/microsoft/terminal/assets/1429524/79156cf0-a39b-44df-bb9a-9afed26e887e) ![image](https://github.com/microsoft/terminal/assets/1429524/d65ae2e1-5f58-4219-a4a8-d6f0867221e2)
claunia commented 2026-01-31 04:46:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 23, 2023):

This was an issue on Windows 10 that Terminal had worked around. We recently (accidentally) broke our workaround. Stay tuned. 😄

@DHowett commented on GitHub (Oct 23, 2023): This was an issue on Windows 10 that Terminal had worked around. We recently (accidentally) broke our workaround. Stay tuned. :smile:
claunia commented 2026-01-31 04:46:54 +00:00
Author
Owner
Copy Link

@psxlover commented on GitHub (Oct 23, 2023):

Glad to hear it is a known issue and not just something wrong with my PC.

@psxlover commented on GitHub (Oct 23, 2023): Glad to hear it is a known issue and not just something wrong with my PC.
claunia commented 2026-01-31 04:46:55 +00:00
Author
Owner
Copy Link

@barkermn01 commented on GitHub (Nov 7, 2023):

@DHowett i believe there is a specific term for that it's called a Regression :D

@barkermn01 commented on GitHub (Nov 7, 2023): @DHowett i believe there is a specific term for that it's called a Regression :D
claunia commented 2026-01-31 04:46:55 +00:00
Author
Owner
Copy Link

@stevenwong commented on GitHub (Nov 30, 2023):

If anyone needs a temporary fix, uninstalling then reinstalling the Terminal app solved it for me. Neither repair or reset worked.

@stevenwong commented on GitHub (Nov 30, 2023): If anyone needs a temporary fix, uninstalling then reinstalling the Terminal app solved it for me. Neither repair or reset worked.
claunia commented 2026-01-31 04:46:55 +00:00
Author
Owner
Copy Link

@IMB11 commented on GitHub (Sep 7, 2024):

I fixed this issue by making sure that the font being used was installed for all users instead of locally just for my user.

@IMB11 commented on GitHub (Sep 7, 2024): I fixed this issue by making sure that the font being used was installed for all users instead of locally just for my user.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Fonts Issue-Bug Priority-1 Product-Terminal Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15731
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?