Skip to main content
T
trevora76464419
Participant
July 6, 2017
Question

Adobe Acrobat Pro XI Crashes when Scanning

  • July 6, 2017
  • 13 replies
  • 11732 views

I am using Adobe Acrobat XI Pro and have done without issue for some time. As of yesterday when I am scanning from my Canon LIDE 220 Scanner the process crashes and I get the following message:

Adobe Acrobat has stopped Working - A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available"

No solution is provided.

I have done a "Repair Acrobat Installation" and ensured that I have latest version 11.0.20.

Please help. Work stops without the scanner!

This topic has been closed for replies.

13 replies

Show previous replies
B
brucec3319163
Participant
August 7, 2017

I have same problem, seems to have started when Windows 10 did an update a short while back. I have a Xerox printer/scanner that was trouble free till we went from Windows 7 to Windows 10.... perhaps a patch will be provided from Microsoft some day!

A
andywike
Participating Frequently
July 24, 2017

I have the same issue.  Started happening about 60 days ago.  Tried both the DC and $500 package of Adobe Acrobat Pro and same thing.  Using Samsung c1860FW with latest drivers.  Frustrating

    M
    Mark Pfeifer 2
    Participating Frequently
    August 15, 2017

    I'm having basically the same issue.  Started happening a couple of months ago.  I try to scan a document on my CanoScan 8800F, and most of the times I get an application crash.

    risharmaAdobe
    Adobe Employee
    risharmaAdobe
    Adobe Employee
    August 17, 2017

    Hi Mark,

    Could you too share the required info asked here?

    Thanks

    Rishabh

    mikeb86531431
    mikeb86531431
    Participant
    July 17, 2017

    Have same problem with Acrobat XI and a Canon 9000F Mark II scanner. For several years, this has been a rock solid reliable combination of hardware and software, but not in the last 30 days or so. Repaired Acrobat installation. Updated Canon driver, dated May 1, 2017, which could be the source of the problem. Very annoying.

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