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.}

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

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

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”

@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.

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.