Skip to main content
Anonymous
January 10, 2020
Question

Adobe Reader X v10.1.3 Dutch

  • January 10, 2020
  • 7 replies
  • 1084 views

Hi all,

Since yesterday 1/9/2020 Adobe Reader X v 10.1.3 crashes.

I want to repair or reinstall this version but i can not find anywhere on the internet the Adobe Reader X v10.1.3 Dutch.

I know that this version is not supported anymore and needs an upgrade, but that is not possible because of the OS-version (on the local computer).

Is there any place on the internet of has someone this version?

Thanks in advance.

Mitchell

This topic is closed to new replies. Start a new post to keep the conversation going.

7 replies

Test Screen Name
Legend
January 15, 2020

Clearly if you did not update the application, then Adobe did not change it. The last changes to the application were with the final update, 10.1.16 in October 2015. But you did not install it: 10.1.3 was changed in April 2012. Many people have reported issues like this; the crashes seem quite random but most people find that a later version fixes it.

Acrobat Reader X does not update without permission. The current version Reader DC does this, certainly.

Many people have found that later versions of X fix the problem. So, it was probably a bug, Adobe fixed it, you never installed the fix. How could it happen? Well, here is an idea. It is just made up, but it shows what could have caused it. Maybe (imaginary speculation) Acrobat Reader connects to a server to get a list of updates. Maybe there was room for 144 updates, then a crash. Adobe noticed the problem and fixed it years ago. Maybe update number 145 appeared and unfixed software failed. 

Anonymous
January 10, 2020

Confirming I am also seeing Adobe Reader X 10.1.3 (English) crash with the error "The memory could not be read".

This started happening on multiple servers yesterday 1/9/2020.

Uninstalling 10.1.3 and installing DC Dec 2019 (19.021.20058) seemed to resolve it for me.

    Test Screen Name
    Legend
    January 10, 2020

    The "font capture" message is an interesting one. I wonder if there was a Windows update on the date where the problem started? If so, it may have added a font that causes problems. If it's Windows 10, Microsoft keep messing with the font machinery, and it isn't surprising that old apps break...

    Anonymous
    January 10, 2020

    Just to add some more context - in our case we were seeing the issue on Windows Server 2012 R2 and Windows Server 2016. Automatic Windows updates were disabled on these servers and we hadn't recently applied any manual Windows updates.

    Test Screen Name
    Legend
    January 10, 2020

    I've seen other reports that V10 has just stopped working.

    Anonymous
    January 10, 2020

    In the meantime i have found an alternative.

    I have uninstalled the v10.1.3 version, than installed v10.1.0 and used the update tool to install v10.1.2.

    Because any version higher than v10.1.2 gives an error.

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