Just starting out, with latest FontCreator, on Win7. Built the suggested quickStart font, per tutorial, but when FontCreator tries to install the font, I get the following error:
Could not complete font installation. The activation requires a display name to be present under the CLSID key.
I hunted around the settings and couldn’t find anything associated with a CLSID (class ID, presumably). The font might be installable by simply putting it into the system fonts folder, but I’d like to understand what’s going on here, and it’s more convenient to use the Install Font button in FontCreator.
Thanks in advance for the support,
Allen
Please uninstall your current version of FontCreator. Then download and install version 6.0.5:
http://www.high-logic.com/fontcreator/FontCreatorSetup6.0.5.126.exe
Do let us know your results.
I uninstalled FontCreator, installed the new version, removed the test font from Windows/Fonts folder, and tried again to install it from within FontCreator. I got the same error message as before.
The font does work as expected when installed manually by dragging it into the Fonts folder.
Allen
It looks like the old dll is still active. Do contact us by email and we’ll sort it out.
Unfortunately I have to admit it is indeed not fixed with this new fontinstaller dll. We won’t be able to find a solution in the near future due to a major upgrade of our development platform.
I hope we are able to release an update within a couple of months, so for now please use the workaround.
Not a problem. I can just drag fonts into the system font folder, so the inconvenience is trivial.
Thanks for looking into it.
Allen
It is embarrassing, as it took over 3 years to localize the cause of this bug. 
However, although it took way too long, we have finally found and solved the bug.
Please download and install the fix from this url:
http://www.high-logic.com/utils/FontInstallerSetup.exe
Do let us know your results.
It looks like it’s working. I don’t have any test fonts handy, but I’ll try to locate the specific one that was causing problems when this originally came up.
Thanks for following up!
Allen
Thank you for your patience. I’m glad to hear things seem to work as they should.