FolderItem.FontActivateMBS not working anymore on Windows

The simplest way to verify if the font is valid, is to double on it, and click “Install”.

A solutions update:
It was not the designer, it was not the font. It is that some part of Windows blames the font depending on its location as written. I followed a lot of wrong tracks – enabling/disabling firewall, debugging registry and services – until I realised I could use InnoSetup to replace the font in my app‘s resources folder with one I unpacked on the Windows exclusive file partition side.
Why Windows behaves this way: Still no clue. But a working workaround.

That’s not a solution for me, this project intentionally does not use an installer.

If you should ever find out, please let me know (and feel free to update).
I wish I knew the right answer myself.

1 Like