I installed Adobe Reader X yesterday (2/15/2011). Today I uninstalled it and then reinstalled it. My operating system is Windows 7. EVERY TIME I exit Adobe Reader X, this message pops up, which requires me to cancel or wait, Adobe Reader has stopped working. This is really frustrating as I am unable to find a solution to this problem on the internet. Additionally, Adobe Reader X is the ONLY version of Adobe Reader offered on the Adobe website (unless I am not looking in the right place).
Anybody have a suggestion as to the solution?
This is quite strange behavior. Did you face any problem while installation of Reader X? Do you face this problem only while exiting from Reader? Did you try repair from Add Remove Programs?
You can try Reader lower versions which you can download from below link
Thanks for the link to v9.4.0. I think I will continue to use this version until my problem is solved with X. As I mentioned in the initial post, I uninstalled and reinstalled the software and the same problem occured. I was surprised that nobody else posted the same problem.
What does the Event Viewer show as the cause of the crash? I am seeing a slightly different problem. I installed Adobe Reader X (10.0.1) on February 16th. Over the last few days, I noticed that it crashes all by itself if I leave it up for more than 45 seconds. The Event Viewer shows:
Faulting application AcroRd32.exe, version 10.0.1.434, time stamp 0x4d456f48, faulting module WININET.dll, version 8.0.6001.19019, time stamp 0x4d0c5473, exception code 0xc0000005, fault offset 0x0002387b, process id 0x1cd8, application start time 0x01cbd4f5394c39e0.
I have not had a chance to do basic problem determination (reboot, re-install).
I'm having exactly the same problem as MrDavie.I've "chatted" to user support but all they could do was create me an account and send me here! Anyone got any answers yet? Seems crazy to have to go back to v.9...
I reverted to v9 and am just fighting Adobe's upgrade agent to prevent X from being
reinstalled on my computer. This problem is clearly in the ball park of the developers. If they monitor these forums, someone should have the courtesy
to acknowledge or deny this problem, letting us know if they care at all about our plight.
And while they are at it, perhaps someone at Adobe could get this forum website to respond a little more quickly. I would think it is embarassing to Adobe to have such a slow site.
I have a similar problem. I have Windows 7 SP1 and Adobe Reader X. Whenever I click on a link
on a page or from an email, it either says "Done" at the bottom of IE or it says Adobe has stopped working. I can't open any PDF files. I've tried uninstalling and reinstalling and also repairing the Reader X to no avail.
I'm going to try the Adobe Reader 9.40 installation provided on this page. This is definitely a problem with Reader X because my older version of Reader worked fine.
Can you please post crash log? It will be helpful for further investigation.Do you face this issue with only when trying PDF in browser or this issue comes every time? What are the other applications installed on your computer.
I, too, have had the same experience.
An alternative is http://www.nitroreader.com/
You can enter text and add highlights to .pdf files with this appication.
If Adobe reads their own forum, seeing their competition recommended might get their attention. : - )
If not, you still win. : - ))
I had the same problem. Currently X is working.
I uninstalled with the windows control panal
I manually tracked down every version of reader and removed
I used the easy cleaner program to remove last traces of the programs
I uninstalled Adobe Air using the same methods
I then reinstalled X
Crossing my fiingers
I had the same problem, windows task manager said adobe x not working, I kept the program running and after a 10 minute delay , voila , it is working. I have no idea what happened but I will keep my fingers crossed.
mrdavie: If error message is seen only when you exit Adobe Reader X are you able to view PDF files without any issue? can you provide the crash log?
NH12345: How did you update Reader to 10.0.1? can you provide the crash log.
Inayal/was able to view and work with PDF files, both in the standalone Adobe Reader X and inside the browser. The failure occurred in both situations about 60 seconds after Adobe Reader X started. A typical crash log from the Event Viewer:
The Microsoft report file contains:
Sig.Name=Fault Module Name
Sig.Name=Fault Module Version
Sig.Name=Fault Module Timestamp
DynamicSig.Name=Additional Information 1
DynamicSig.Name=Additional Information 2
DynamicSig.Name=Additional Information 3
DynamicSig.Name=Additional Information 4
UI=C:\Program Files\Adobe\Reader 10.0\Reader\AcroRd32.exe
UI=Adobe Reader has stopped working
UI=Windows can check online for a solution to the problem.
UI=Check online for a solution and close the program
UI=Check online for a solution later and close the program
UI=Close the program
AppPath=C:\Program Files\Adobe\Reader 10.0\Reader\AcroRd32.exe
Strangely, the problem disappeared sometime after 09:17 yesterday for no reason that I can see. I rebooted my laptop later that day and the problem has not yet re-occurred.
I am running Vista Ultimate 64-bit with the latest maintenance.
I have been having the exact same problem. I can only open a link to a pdf by saving it first
on my computer. Then when I close the article, it tells me it has stopped working and it searches for a solution but there is none.
I've also tried to repair it from within the program but that did not fix anything.
So it looks like the only fix is to go back to an old version and ignore the update pestering.
Also agree that this site is HORRIBLY slow. I couldn't get into any forum topic this afternoon it was so slow. Tonight it eventually goes into the topice but it is super slow. Something is not working with your site as well as your program Adobe!
Hey, folks, I found a quick and easy solution to this major annoyance:
Evidently, Adobe programmers are still primarily targeting Windows Vista instead of Windows 7 (probably because Vista still outnumbers 7 in installations...go figure).
I'm positively flabbergasted that no one else, either at Adobe or Microsoft, seems to have noticed this straightforward route to a solution and posted it on the Web. You can Google for hours (I did!) and not run across any such obvious fix.