It was first that i did.

 

@DanielFaraday Check if you have these installed:

MSXML 4.0 SP3 Parser

MSXML 4.0 SP3 Parser (KB2721691)
They're around 5 mb each.

LexChamber presets are in .XML format. I have them installed and my Lexicon plugs are fine.

 

Didn't work for me.

 

Can you please write step by step manual for humanitarian like me?

 

1. All your fonts are installed to C:\Windows\Fonts. Those you may be interested in are TrueType (*.ttf) and OpenType (*.otf) (or collections with a *.ttc extension). However, it may be easier for you to manage your font collection via the Control Panel (Appearance and Personalization -> Fonts). If you installed any extra fonts manually, try removing them (start with the ones whose names begin with 'A'). Be careful and don't remove anything that came with your Windows installation* or which might have been installed with applications you're using. As far as I can tell, Lexicon should pick Arial Narrow (it seems to do so on my system at least) so narrowing the investigation to an excessive 'A'-something.ttf/otf may be a good starting point.

* For the reference, don't remove anything from this list.

2. How to rebuild the font cache a.k.a reset font settings in Windows 10.

It is possible that your font cache is simply messed up so before you dive into your font collection, rebuild the cache. If it doesn't have any effect, go to point 1 and have fun. ;-)

I hope it helps a little bit.

 

Yes. It works. Thanks mate. I wanna kids from you! I removed every font that was installed july 4th, and deleted fntcache.dat from windows\system32. Now my lovely lexicon works as it should without screwed fonts.

 

I bet you don't. ;-)) I'm glad everything is working correctly now.

 

That was very entertaining and informative. Glad everything worked out. I learned a fair bit too.

 

When someone puts a 'disagree' mark to a comment, for merely asking a pertinent question, there can really only be one of two reasons for it. Either they are deliberately trying to instigate a negative response, OR they are the lowest form of human life in the known universe.

Which one is it Sinewave?

 

I didn't find a way to see what fonts have I installed manually. Actually, I know that I haven't installed any font (or collection) myself, but some apps might have. Non of these font files had "date created" info, and deleting files by the "date modified" info didn't make the change to the right font (font in lex was changing randomly as in, when I delete font that it used, it goes to another, also wrong font)

What I have done to fix this is:

1. I made a backup of the Fonts folder.

2. Then deleted ALL the fonts that system let me delete from the Fonts folder (a lot of fonts still remained unable to be deleted)

3. I downloaded this:
http://www.withsteps.com/3483/windows-10-pro-default-fonts-download.html

4. Copied (installed) all files from this download to Fonts folder.

5. And finally I copied backup font files back to Fonts folder (didn't overwrite anything, just new files copied so I have everything that I had before...just in case something is needed).

Now it works as suppose to.

 

Hi,
I would like to thank people who gave all this information. I followed your advice, I deleted all the .dat files, but also install the msxml application. Just one thing, to remove the .dat files if Windows tells you that they are used by "nis.exe" (Norton Internet Security) you can't stop the process, restart Windows 10 in Safe mode. For help at this address : https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode
https://www.microsoft.com/en-us/download/details.aspx?id=15697
Big thanks, my presets work fine !
L.

 

For me, it was Ample Sound Guitar font

 

But this is caused simply because Lexicon loads latest font installed in Windows 10. So if you install any application with fonts included that font will be used.
This can be solved like:
- copy Arial font from fonts folder to desktop
- remove Arial from fonts
- move Arial from desktop to fonts folder
That way Arial will be latest installed. OMG what a nonsense

 

I disagreed because it is a completely off idea. Defragging a drive cannot do anything serious like this to programs. In 20+ years with computers I've never encountered any problem with defragging a drive, even with various defraggers like JKDefrag or Defraggler. :shrug:

btw. this is one more reason why it is a good idea to use CCleaner regularly. It can also refresh the font cache amongst other things, like keeping the registry tidy and hard disk clean.

Cheers!

 

No. I did some mess with fonts (for the purposes of photoshop) and seems like my lexicons still fine. There must be other reason (I guess).

 

Maybe latest font installed which started on letter "A".

 

just ########### select all fonts and delete all #########keep a backup first ####
windows wou;ld not delete some of them......at all ....these are the really required
run the thing
you are done...