Skip to main content
D
davej63258672
Participant
October 30, 2017
Answered

My text engine will not initialize?

  • October 30, 2017
  • 2 replies
  • 1903 views

When I select the text it comes up with the message text engine is prevented from initialized. any thoughts?

    This topic has been closed for replies.
    Correct answer Anwesha Dev Chaudhary

    Please go to location:

    C:\Users\[user_name]\AppData\Local\Adobe\TypeSupport\PSE<version no>

    and rename the files present there.

    AppData folder is hidden by default.

    You can turn on viewing of hidden files and folder or simply type the complete location C:\Users\[user_name]\AppData\Local\Adobe\  on Windows explorer search.

    Thanks,

    Anwesha

    2 replies

    K
    kArthurII
    Participant
    June 24, 2023

    Was having the same issue.  Did these steps, but it did not go away until I powered down the computer and restarted.

    Before doing this, close Photoshop.

    1. Deleted the PhotoShop Font Cache.

    2. Deleted the System Font Cache.  In order to do this, I had to go to windows services and stop the service "Windows Font Cache Service".

    3. Some instructions say to delete the Photoshop font cache at C:\Users\[user name]\AppData\Roaming\Adobe\Adobe Photoshop <version>. Delete the CT Font Cache folder and empty the Recycle Bin. I did not have this folder.

    4. Power down and restart computer.

    5. No more issue.

     

    Reference this article:

    https://helpx.adobe.com/photoshop/kb/troubleshoot-fonts-photoshop.html#

     

     

     

    A
    Community Manager
    Anwesha Dev ChaudharyCommunity ManagerCorrect answer
    Community Manager
    October 31, 2017

    Please go to location:

    C:\Users\[user_name]\AppData\Local\Adobe\TypeSupport\PSE<version no>

    and rename the files present there.

    AppData folder is hidden by default.

    You can turn on viewing of hidden files and folder or simply type the complete location C:\Users\[user_name]\AppData\Local\Adobe\  on Windows explorer search.

    Thanks,

    Anwesha

    MichelBParis
    MichelBParis
    Legend
    October 31, 2017

    This error message generally appears after a recent Windows 10 Creator update. There are posts which  confirm that updating to the latest Windows 10 Creator version (1709) solves the problem.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices