Elements: Something prevents the text engine from being initialized

  • 1
  • Problem
  • Updated 10 months ago
  • Solved
  • (Edited)
Hi forum friends!

I have bought Photoshop Elements 12 with an installation disc and I have been using PE12 for uears without any problens until the last major Windows 10 update in early July 2017.

Since then, I cannot use the text tool in PE12 anymore, this error message pops up:
" Could not complete your request because something prevented the text engine from being initialized."

If I re-install PE12 from disc, it works fine, but as soon as I re-boot my PC, the problem is back.

I have found discussions on the forum up to two years old on similar issues, but none of them with a working solution. I reported the problem to Microsoft a few weeks back, without any reply!


Thankful for any help!

KInd regards from Johan in Norway
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
  • frustrated

Posted 1 year ago

  • 1
Photo of mike.j.newman

mike.j.newman

  • 17 Posts
  • 1 Reply Like
Yes Johan, I, like so many, failed to find a solution to this problem. In the end I saw a reply saying that someone had upgraded to PE15 and the problem had gone away. So I did that, and have not been troubled since. Poor show by Adobe though not to have admitted the problem or found a work-around or solution.
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
Hello Mike!
Thank you so much for your reply! How did you do the upgrade to PE15 - did you have to buy the product once more? Furthermore, I do agree, that Adobe does not show much customer responsibility. To me it feels wrong, that we, as customers, continue buying more products from them, as a thank-you for them NOT helping us out!?
Kind regards from Johan
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
Hello again Mike!
Browsing a little more this afternoon, I found this thread: https://forums.adobe.com/thread/2303625
where Andreas in Germany had the same problem in his PSE15 in April 2017. Following his experience, I deleted the folder mentioned, and it works fine in my PSE12 case as well ??? !!!

This folder I deleted: C:\Users\[username]\AppData\Local\Adobe\TypeSupport

Best regards once more from Johan in Norway
Photo of mike.j.newman

mike.j.newman

  • 17 Posts
  • 0 Reply Likes
Thanks for this Johan. Glad it has solved your problem. I've made a note of it in case it comes back.
Mike
Photo of Langley Cornwell

Langley Cornwell

  • 1 Post
  • 0 Reply Likes
I'm trying to find this folder and delete it but it's nowhere to be found. I've been working on this problem, off and on, for several days. Grrrrr. I'm using PSE11.


ETA: Okay, so I did ultimately find the TypeSupport file, delete it, and reboot. This did not fix the error for me.
(Edited)
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
Hello Langley,
Set out below is my reply to Cheryl, I hope you find it helpful (it is still working for me)

Hi, Cheryl (and anyone else who may be interested),

After a number of attempts to sort out this problem, all of which have ultimately failed, the following alterations are currently working for me. I cannot guarantee it will carry on working and I do not know if it will cause any problems in the future, perhaps somebody could advise.

1. Open the TypeSupport folder, in my case it contained only 1 (LST) file named AdobeFnt13.lst which consisted of 147kb.

2. Rename this file AdobeFnt13OLD.lst.

3. Relaunch PSE. - this re-generates the AdobeFnt13.lst and in my case the new (re-generated) file was only 98kb. This file works OK but, again in my case, often reverted to 147kb and ceased working.

4. Right click on the AdobeFnt13.lst file (98kb) and then click on Properties followed by the General tab.

5. Towards the bottom of the tab there is a box which says Read only. Tick this box and then, at the bottom, click on Apply. Hopefully this makes it stay on 98kb (well, it has for me so far, anyway!).

6. Relaunch PSE.

7. As a precaution, I have taken a copy of AdobeFnt13.lst (98kb) on a stick so I can copy/paste it into the TypeSupport folder should it be required in the future.

 

Any comments (from anyone) would be appreciated.
Regards,
Rod Breeze
Photo of Michel BRETECHER

Michel BRETECHER, Champion

  • 1084 Posts
  • 227 Reply Likes
Not sure it's the same font problem, but there is an issue with the latest Microsoft updates:

Note from Dov Isaacs (July 13rd)

"

We have recently become aware of an anomaly that was introduced with the Windows 10 Creators Update affecting fonts that are installed via “shortcut.”

 

Most fonts are either installed by the operating system or applications directly into the C:\Windows\Fonts directory and users can install fonts into that directory by right-clicking on a font and selecting “Install.” However, Windows also offers the option to install a font but keeping the font file itself in some other location in the file system. This option is invoked by right-clicking on the font file and selecting the “Install as Shortcut” option. (Many of us use such “Shortcut” installation of fonts as a means of disciplined housekeeping for large numbers of fonts and font families!)

 

The anomaly is that after powering up / rebooting your system, fonts installed via “Shortcut” won't appear either in the Fonts Control Panel or in applications' font lists.

 

By simply rebooting your system, those installed by “Shortcut” fonts will reappear in the Fonts Control Panel and the applications' font lists. Thus, if you have any such installed by “Shortcut" fonts, you will always need to do a second boot of your computer system until Microsoft fixes this nasty bug. Alternatively, you can uninstall those particular fonts and reinstall them via the normal “Install” which places the font files themselves in the C:\Windows\Fonts directory.

 

Important Note — This anomaly does NOT appear to affect Typekit font synchronization in any way!

 

Microsoft is aware of the problem, but we have no ETA for a fix. (The July 11 Windows 10 update does not fix the problem!)

 

        - Dov Isaacs, Principal Scientist, Adobe Systems Incorporated

 

Please contact me directly if you need further assistance with this.

 

          - Dov

Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
Thanks so much to Michel and Dov!
Please see my message above about deleting this folder:
C:\Users\[username]\AppData\Local\Adobe\TypeSupport
Johan
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
Johan (or anyone),
I have the same problem with Photoshop Elements 11 but ,try as I might, I cannot find any similar files/folders (including 'hidden' files). Any ideas? Any help or advice would be greatly appreciated.

Rod
Photo of cheryl

cheryl

  • 1 Post
  • 0 Reply Likes
I also have PSE 11, and I did manage to find this folder and delete it.  My AppData folder had been hidden, but once I found that, the rest of the path was there to follow.  This trick then worked to solve the issue.  So anyone else with PSE11 that is having trouble should give this a try, it might work for you.
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like

Hi, Cheryl (and anyone else who may be interested),

After a number of attempts to sort out this problem, all of which have ultimately failed, the following alterations are currently working for me. I cannot guarantee it will carry on working and I do not know if it will cause any problems in the future, perhaps somebody could advise.

1. Open the TypeSupport folder, in my case it contained only 1 (LST) file named AdobeFnt13.lst which consisted of 147kb.

2. Rename this file AdobeFnt13OLD.lst.

3. Relaunch PSE. - this re-generates the AdobeFnt13.lst and in my case the new (re-generated) file was only 98kb. This file works OK but, again in my case, often reverted to 147kb and ceased working.

4. Right click on the AdobeFnt13.lst file (98kb) and then click on Properties followed by the General tab.

5. Towards the bottom of the tab there is a box which says Read only. Tick this box and then, at the bottom, click on Apply. Hopefully this makes it stay on 98kb (well, it has for me so far, anyway!).

6. Relaunch PSE.

7. As a precaution, I have taken a copy of AdobeFnt13.lst (98kb) on a stick so I can copy/paste it into the TypeSupport folder should it be required in the future.

 

Any comments (from anyone) would be appreciated.

 

Regards,

 

Rod Breeze
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
Hi Rod!
It may be different in PSE11, to me it appears to work in both the PSE12 and -15 cases.
I guess the root of the folder tree must point to where your Photoshop has actually been installed on your PC. If you (or someone else) have altered the actual installation location to some other place than the standard location on the C:-drive, you could try doing a file search for 'TypeSupport' (or 'Adobe') on the root directory 'My Computer', i.e. one level above the C:-drive, letting your PC do the search job itself. Maybe also try out some alternative search words like for instance 'text' of 'type' or 'font'. (And finally, if what I propose is just 'bullshit', then maybe someone else will pick up on this, first have a good laugh and then give you and me a better suggestion !?!)
All the best of luck from Johan in Norway.
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
Thanks, Johann. I have already tried the ideas you suggest with no luck and the installation was in the standard location. I also feel that PSE 11 is different to later versions and so I think all I can do is wait until either Adobe or Microsoft produce a fix. I might, and probably will, in due course upgrade to PSE 15 as previous posts indicate it seems to work OK. I will wait a while though and see if anything happens but I am not holding my breath!  Many thanks for your response.

Cheers,
Rod
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
OK, Rod! Personally, I am not a big fan of the 'waiting for someone' concept, so I thought about this problem a little further. First of all one question: Will you be able to re-install your PSE11 in order to see whether or not the problem is still there in the new installation - do not re-boot your system after the re-installation before you have tested it, even though Adobe will probably suggest exactly that! My thought is as follows: If the problem does not occur with the new installation (and no system re-boot), then you might try to use the approach we've been discussing, in the 'reverse direction', namely by creating your own private location/folder with a name of your choice, either on C: or on some other drive, and then install your PSE11 there. Hopefully you will be able to maintain the integrity of this new unique and 'secret' location through system re-booting and maybe even through Microsoft updates, simply because they don't know where your PSE11 is, and therefore cannot ruin it for you ... Just a thought, in the middle of the night. Cheers from Johan
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
Thanks, Johan. I have already re-installed it twice, the first time it worked OK until I rebooted, then the problem came back, the second time I forgot to try it before a reboot(!) but on reboot it failed again. In both these instances I re-installed it in the same (default) location on Drive C. Your suggestion of installing it on a different drive did not occur to me but I think it's a great idea and well worth a try. Unfortunately I have not got the time at the moment but I will try it later and let you know how I get on. Many thanks.

Rod
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
OK, Rod! When you do, please remember to tell me the outcome, if it works and also if it doesn't. Maybe it suffices to invent a new and 'secret' folder on C:, personally,I use a separate drive, which I have named D: where I do all of my own installations. This also reduce the filling up and clogging of drive C:. All the best and have a nice summer, Johan
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
Johann,

It works!! And I have rebooted and it still works. During installation I simply altered the recommended locaton from C:\ Program Files(x86)\Adobe\   to G:\   (this is a semi spare drive I hardly use).

Many thanks for your help and advice. Simple and brilliant!
Best Wishes,

Rod
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
Hi Rod!
Superb - very happy about that - hoping that many other forum members read this conclusion!
Johan
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
Johan,
Unfortunately the problem with the text appeared again. However I had a problem with Norton Internet Security which, on research, seemed to be caused by the 'Fast Start Up' in Windows 10 being enabled. I therefore disabled the Fast Start Up and cured the Norton problem. This research https://community.norton.com/en/forums/cannot-access-norton-run-scan indicated that Fast Start Up could cause other problems so I retried Photoshop and it now seems to work OK - I have re-installed it on Drive C. The Norton research also indicated that Microsoft updates re-enabled Fast Start Up automatically so it may need re-disabling after updates. The downside is that the computer takes a bit longer to start up!

Best wishes,
Rod
Photo of Ian Richardson

Ian Richardson

  • 7 Posts
  • 3 Reply Likes
I started getting the "something prevented the text engine from being initialized" error message immediately after the last Windows 10 update earlier this month. I managed to fix the problem when someone suggest I rename a couple of font files as "old", but a few days later the problem returned. No matter what I do, I can't fix it, which is immensely annoying as I can no longer put captions on my photographs and other Photoshop Elements 11 or 14 documents. I have uninstalled Photoshop 14 and reinstalled it, but the problem remains. Any suggestions?
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
Ian,
I have Photoshop Elements 11 and I believe the files you refer to above do not exist in this edition (see my previous posts). All I can suggest is that you disable Fast Start Up as outlined in my reply to Johan as stated above. Fast Start Up is not easy to find so if you need any help in this respect, please let me know. It seems that the return of the problem might well coincide with a Microsoft update as I describe above.

Regards,

Rod Breeze
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
Hi Rod & Ian!
I was wondering what I could possibly reply to Rods previous message from July 29 (or maybe 28th), which I find most disturbing. Then I saw Ian's message and Rod's reply today. It worries me a lot, that the problem re-appears and may be connected to Norton and/or Fast Start Up, This is/was new to me. To re-iterate some of my thinking: If your PSE is installed in a 'secret', non-standard location, or if you haven't re-booted your PC after installation, then I cannot offer any further explanation, except that some 'silly' program tells the Photoshop text engine to look elsewhere for for setup parameters (it may even be Photoshop itself, for what I know). Personally I run PSE 12 on the latest update of Windows 10, I deleted the '...TypeSupport'-file as discussed some two weeks ago and it works fine, I tested it just now July 30th 2017 at 15:20 CET=GMT+1. I do not use Norton, but I (guess that I) use the Fast Start Up, since I haven't disabled it. Maybe someone up-stairs in Adobe or in Microsoft should start worrying about this by now ???
Johan Møller-Holst
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
Johan,

Thanks for that - as you will see below from my reply to Ian it seems that I am back to square one! If I could find a 'Type Support' file I would delete it but Ian's response in this respect is a bit worrying. 

Rod Breeze
Photo of Ian Richardson

Ian Richardson

  • 7 Posts
  • 3 Reply Likes
Thanks for those comments.

I deleted TypeSupport and is just made things worse. I use Windows Defender on my machines.

Whatever the problem, I am increasingly irritated by not being able to use captioning on Photoshop Elements. I am reluctant to mess about with the files any more -- as it appears certain that the problem is not with me, but with Photoshop and Windows 10.

Ian R
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
I think you are right. Even my latest 'solution' of disabling Fast Start Up has stopped working and I am back to no text. Sorry.

RB
Photo of Ian Richardson

Ian Richardson

  • 7 Posts
  • 3 Reply Likes
It may be unrelated to the Photoshop Elements problem, but the last Windows 10 update earlier this month also wiped out my Epson scanner software and it took me a long while to fix this. Grrrrrr!
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
When I bought myself a new Canon iP7250 printer earlier this year, I had some serious trouble making PSE recognize and accept it. Grrrrrr - square!
Photo of Johan Møller-Holst

Johan Møller-Holst

  • 12 Posts
  • 1 Reply Like
Hello Rod and Ian!
As already indicated earlier in this discussion, I think that you should NOT give up! If you are afraid of deleting a directory like TypeSupport, then why don't you just rename it to TypeSupport_old? Then its still there, and you reame it back if you must!? Furthermore, when installing your PSE from from disc and you are prompted for a location, like C:\ Program Files(x86)\Adobe\ ... or something ..., why don't you simply change it to C:\ Program Files(x86)\Adobe_new\ before hitting 'Enter', and see if it works for you. As I explained a few hours ago, it works for me - and it still does right now, this very minute. Hello there guys, don't let those silly ba...rds ruin your joy and options with PSE!
All the best from Johan in Norway!
Photo of Ian Richardson

Ian Richardson

  • 7 Posts
  • 3 Reply Likes
Many thanks, Johan. I will have a look at setting it up in a new area.

I don't have a disc. I have a download, which I used yesterday to re-install, but as I have explained, it didn't fix the problem.

Ian R
Photo of Ian Richardson

Ian Richardson

  • 7 Posts
  • 3 Reply Likes
Tried to download to another area as suggested by Johan, but problem remains. I might now go to system restore and take my laptop back to before the latest Windows 10 download, which seems to be the cause of my text engine problems.
Photo of Rod Breeze

Rod Breeze

  • 12 Posts
  • 1 Reply Like
I hadn't thought that the cause might be the latest Windows update, I assumed it was the Creator's Update which I didn't install until quite recently (but before the latest update). Please let me know how you get on if you decide to go ahead.

Rod Breeze
Photo of Ian Richardson

Ian Richardson

  • 7 Posts
  • 3 Reply Likes
I did a System Restore to the last Windows 10 update earlier this month and that fixed the problem. Text engine now working fine on Photoshop Elements 14. Let's hope it stays that way!