@foone hey wait, I think this happened to me once. It had something to do with it being unable to find the Cascadia font. Forcing it to default to a different font was a workaround, if you're still trying to fix it.
@foone I’m happily not subjected to all the Windows improvements anymore (‘Pray we do not improve them further’)
but all the recent news makes me vaguely nostalgic for Windows 2000 Professional, with which I was very happy through 2012 at least
@foone possibly the reboot would have fixed it all on its own. I thought it was fixed but for a LONG time VS exposed a Windows font rendering bug that acted like this 😕