Since Command sees the correct filename - it's only File Explorer which uses .... fonts - so if fonts are corrected so should the Explorer display anomaly ... it looks as though it only affects folders, the font names in post 8 look fine
Now, I'm really bowing out - another thread deserves my attention
Make sure you don't have Hide fonts based on language settings checked, then try running the following in cmd prompt:
fsutil resource setautoreset true c:\&fsutil usn deletejournal /d /n c:&Dism.exe /online /Cleanup-Image /StartComponentCleanup&&sfc /scannow&Dism.exe /Online /Cleanup-Image /RestoreHealth&sfc /scannow&Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase&pause
Then post what it shows. I nned to know if it completes, or if any portion didn't. If something failed to run, we'll need to run it through a mounted ISO.
It's just one line. Just copy and paste it in(middle click)
I finally finished the first phase of help on another member's thread.
Not to interrupt what Cliff has already started ...when you get the chance
Please follow this tutorial to provide the current operating environment of your machine.Thanks
Speccy - Publish Snapshot of your System Specs
I found the culprit! Yipppppeeeeeeeeeeeee!!!!!!!!!!
It's Avenir font. Just now I have removed all type of Avenir fonts from my system and the problem has been solved. Its a very good font that I've been using a lot in my work since the days of Windows 7. It runs fine on windows 8.1 too but looks like that it's incompatible with Windows 10. It has given trouble to other users as well whose posts I read and got the idea!
Check this post!
Thanks everyone for your support!
Heheh, yeah,compatible fonts. For the first time in my life I've encountered a font incompatible with the most recent operating system. I've been using Windows from 95 version and never faced issues of font incompatibilities!!