OCR: "No languages installed"

[na_at]

hello everybody

my OCR Tool does not work anymore, as it say no languages installed, even though they are installed. It used to work great, but it just stopped working, as i noticed the "OK" Button being greyed out:

image(1).png

I can't open the drop down, as it is empty. But apparently the necessary languages are installed:

image(2).png

I looked at the other threads, but I am not super versed on the technical side, so I could not try all the offered suggestions.

I also downloaded the language pack Europe West here: https://www.pdf-xchange.com/pdf-xchange-ocr

and it changed nothing.

Thank so much for the help.

-nagua

[Stefan - PDF-XChange]

Hello na_at,

Welcome to our forums!
Can you please check under Help -> About for the version of our Editor currently installed on your end?
We had some such reports with some older builds so I suspect you might be using one of the affected ones.

If you can - please download and install the current latest version from our website:
https://www.pdf-xchange.com/product/downloads
And all should be well!

Kind regards,
Stefan

[na_at]

it worked!

Thank you so much

Have a nice day!

[Stefan - PDF-XChange]

[sunshineweb]

I am on 9.5.368 and I cant't update. other pcs with that ocr work fine.
i tried to uninstall every setting (with revo) but every setting is preset at new installation.

Has anyone ideas what are my options?

[sunshineweb]

I uninstalled the programm
then deleted in both the folder "Tracker Software" in
C:\Users\...my path ...\AppData\Roaming
and C:\Program Files

reinstalling, the software still knows my product key. and my settings. (but forgot at least my recently used files)

here it is described with solution:
viewtopic.php?p=185415&hilit=language+ocr#p185415

[Stefan - PDF-XChange]

Hello sunshineweb,

Thanks for sharing the link to the other topic. Indeed the solution proposed there is the one we can offer in these scenarios where an older version of our software is used on the latest Win 11.

Kind regards,
Stefan

[sunshineweb]

with an update I think the language broke again - I had to uninstall and reinstall pdfpro (just an update of the language pack didnt help). well, it works now.

maybe this was caused by an not correct installed language (German, old spelling)

on the other laptop it worked seemless.

[Stefan - PDF-XChange]

Hello sunshineweb,

If you are updating to the current latest version - it should not have the issue with the missing languages. If reinstalling some older builds - I can not really comment on why it behaved the way it did, but glad that at the end you now seem to have it working as needed on all your machines!

Kind regards,
Stefan

[sunshineweb]

I updated from the previous version to this one, and after that, OCR started failing again on one PC with an error message.
Also, the German language pack seemed outdated — it could be updated easily, but this didn’t fix the issue. The error persisted.

To solve it, I had to uninstall PDF-XChange and reinstall it. After that, OCR worked again (in both PDF Editor and Tools).

Please check if updates can potentially break OCR functionality.

[Daniel - PDF-XChange]

Hello, sunshineweb

We are investigating it, but so far everything points to the issue being external errors, most commonly items like permissions issues, or third party apps having a handle on the folder (when they really shouldn't) preventing proper removal and re-creation of folders and their permissions, etc. While some of the possible causes are errors that could come about during the installation process, not all of them are, and in many cases, we see users report this happens a few days after installing, without any warning or explanation. The best theory I have is that security software might eb involved, perhaps there is some unique interaction with opening the OCR during a background scan or some such that leads to this, but in the end, no errors appear, so that is still speculation.

Sadly, it is not a consistent enough issue to reproduce readily, and testing on our end has been fruitless. For now, if you do encounter it again, a quick reinstall should resolve the issue, but with a lack of anything indicating the root cause in the logs we have seen, I cannot be sure that it is possible to prevent this from our end.

Kind regards,