Me - Prior Cascadia font problem. Windows 10, the newer devices interface to "font" , any interaction with Cascadia just crashes setup. Many random keystrokes on my part on clearing fonts, initially from c:\Windows\Fonts & later from c:\Users\..\AppData\Local\Microsoft\Windows\Fonts ( files open by foo , at one point I couldn't even find what had my file open, the tool I was using unhelfully said "the system" and/or some other fairy that isn't a real thing. Symptom: Windows 10. Fresh install of vs2022 "free version", on a system that has had vs before , that does have vscode , that does have microsoft terminal, most likely way of removing stuff is via the BCU tool. I load vs2022 c/o I happen to like the interface to Anaconda Python install c/o the way it interacts with the standard Python debugger. ( I ask ChatGPT to write some code, my prose is very long, prior art - I have zero expectation of the code presented doing what I want & if I debug by "print to stdout", I will get bored very quickly. What I get is vs being able to run a python script but the editor just isn't , nothing displayed, no ability to edit, just a tab saying my python file name and a message saying Cascadia Code isn't being used .. and a fib that some other font is being used. ( I don't remember the other font ). Google -> no clues. ChatGPT - a whole bunch of suggestions, all could be genuine, none got me any further. So ... interaction with settings and Cascadia Code crashed settings , any attempt to reinstall italic variants of Cascadia appeared to go into infinite loops ~ leave settings @ 100% of a single thread, go for coffee, go to the shops, come back , still 100% of a single CPU , force a stop of settings, repeat , pull hair out ..