Jean-Cyprien Posted July 21, 2017 Report Posted July 21, 2017 Hi, For several members of the French forum it is now impossible to change the font name because PTE stops and freezes with an error "Frame Engine Exception" .The problem happens after a Windows 10 update. It seems that PTE can not read the list of fonts ?A forum member reports that a Windows updating has deleted some of his font files. Thanks - Jean-Cyprien Quote
Igor Posted July 21, 2017 Report Posted July 21, 2017 Hi Jean-Cyprien, We still can't reproduce this problem on our computers with Windows 10 and latest updates. I suppose that this problem can be linked with specific font(s). Quote
Igor Posted July 24, 2017 Report Posted July 24, 2017 On 21.07.2017 at 10:52 PM, Jean-Cyprien said: For several members of the French forum it is now impossible to change the font name because PTE stops and freezes with an error "Frame Engine Exception" .The problem happens after a Windows 10 update. It seems that PTE can not read the list of fonts ?A forum member reports that a Windows updating has deleted some of his font files. Thanks - Jean-Cyprien Jean-Charles, Please ask users which discovered this problem right the following test application: http://files.wnsoft.com/test/FontTest1.zip 1. Unpack the ZIP archive (it's important!) 2. Run ComboFont1.exe file 3. Click Font List button (it should display a list with fonts). 4. Test application will create a new file fontlog.txt in the same folder. Regardless a result, please send me this file. Thanks in advance, Quote
Jean-Cyprien Posted July 24, 2017 Author Report Posted July 24, 2017 Hi Igor, Thank you for your research and your proposal. At the same time it seems the solution was found by DenisB by deleting the file FNTCACHE.DAT (in C:\Windows\System32 ) Jean-Cyprien Quote
Urmas Posted July 25, 2017 Report Posted July 25, 2017 Although, I have not experienced font oddities personally, there are numerous reports and hints about the Fonts and Creators update. Quote
Igor Posted July 25, 2017 Report Posted July 25, 2017 20 hours ago, Jean-Cyprien said: Thank you for your research and your proposal. At the same time it seems the solution was found by DenisB by deleting the file FNTCACHE.DAT (in C:\Windows\System32 ) Jean-Cyprien, Thanks for this information! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.