Shortly after opening a document, Reader freezes for several seconds. Who knows why, it probably accesses the network, or tries to do something smart, which results in the user being unable to read the document for a while.

I have tried to disable as many "smart" options as I could, but without success. Could anyone work around this endless Adobe Reader bug?

I must admit I'm tired of this monster of a program, why can't Adobe keep the Reader a light application, instead of throwing all those unnecessary functions, ads and other uglinesses ... ?

I have the same problem. The document if opened locally (i.e. through the adobe application or direct from a pdf file saved on the computer) opens but after a few seconds the screen freezes the stops responding. I can close adobe down but cannot do anything else. When opening through the brower (I tried with the file in your message above) the file does not open, also a tab appears in the applications taskbar at the bottom of the screen which has a windows icon but no description.

I am having the same problem as other have experienced in this forum. I've uninstalled/reinstalled the latest version - Reader 10.1.3 - several times without the problem getting resolved. I'm using Windows 7 home on a new desktop computer with McAfee protection. Every time I attempt to open a .pdf it opens for a few seconds, freezes, and windows closes the program. I'm getting frustrated because I don't want to pay $39 for personalized support, and so much these days requires use of Adobe Reader.

I have the same program with the latest version of Adobe Acrobat X Pro. I am guessing Adobe is forcing itself to connect online, meanwhile happily has you wait 5-10 seconds or so, then decides all is well (or not... who knows what it is really doing) only then you can use the document as you intended. I wish there was a solution to this.

I have Adobe Acrobat Pro DC running on Windows 10 Pro (Enterprise) and I am connected to a corporate Network. After starting Acrobat (whether with or without opening a Document) it would run for around 15 seconds apparently normally. It would then hang / freeze / crash. If I tried to click on anything more than a few times then Windows would report that Acrobat is "Not Responding". It would recover on its own within around another 15 seconds. This is a common complaint from what I can see. I tried the following things without any success:

Things that didn't work:

Setting Recently Used Documents to only 1

Toggling Enhanced Security, Protected Views settings, etc.

Plug-Ins attempts: Holding Shift when Acrobat starts keeps the problems from happening (but I need many of the Plug-Ins).

Graphics (Multimedia) Settings changes: No effect for me.

Trying all kinds of permutations of settings in the Preferences settings had no effect for me.

My solution (works for me):

1) Close down Acrobat.

2) Fire up regedit (follow the usually cautions for dealing with the Registry)

I looked for this when I discovered that the problem had to do with one the Plug-Ins (as I mention above). I traced it to IA32.api. But, removing this Plug-In file crippled Acrobat in addition to keeping it from crashing. Adobe Support tried to help me but they couldn't figure it out and I couldn't spend any more time with them. These registry changes will stop Acrobat from going out to "the Cloud". This keeps it from hanging while it tries to get through the corporate firewall. My opinion is that it it very poor design and maybe insufficient testing that would cause this unresponsiveness to happen and go undetected. I have been unable to find a non-registry way to get this result.