Adobe Reader Error 1000
Contents |
ElementsAdobe Dreamweaver Adobe MuseAdobe Animate CCAdobe Premiere ProAdobe After EffectsAdobe IllustratorAdobe InDesignView all communitiesExplore Menu beginsMeet the expertsLearn our adobe application error 1000 productsConnect with your peersError: You don't have JavaScript
Adobe Reader Error 1000 Invalid Plugin Detected
enabled. This tool uses JavaScript and much of it will not work correctly
Adobe Reader Download Error
without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post
Adobe Reader 9 Error
a blank message. Please type your message and try again. More discussions in Acrobat Reader All CommunitiesAcrobat Reader 5 Replies Latest reply on Jun 17, 2011 4:57 AM by mattgoldey72 "Adobe Reader has stopped working" Windows 7 (32-bit) mattgoldey72 Jun adobe reader update error 14, 2011 11:15 AM Every single time I start Adobe reader, it crashes with "Adobe Reader has stopped working" and the below error message in the Application event log.I have removed and re-installed Adobe Reader X, but it still does this.Log Name: ApplicationSource: Application ErrorDate: 6/14/2011 12:50:06 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: redactedDescription:Faulting application name: AcroRd32.exe, version: 10.0.1.434, time stamp: 0x4d456f48Faulting module name: InkObj.dll, version: 6.1.7600.16385, time stamp: 0x4a5bda13Exception code: 0xc0000005Fault offset: 0x00052840Faulting process id: 0x1638Faulting application start time: 0x01cc2abb7f033340Faulting application path: C:\Program Files\Adobe\Reader 10.0\Reader\AcroRd32.exeFaulting module path: C:\Program Files\Common Files\Microsoft Shared\Ink\InkObj.dllReport Id: bccc55a5-96ae-11e0-810d-88ae1db2fa42Event Xml:
Installation > Acrobat X Professional crashes and crashes and crashes after updating 2011-10-12 14:28:50 StevenD Registered: Oct 6 2006 Posts: 368 I held of clicking the update notice that kept popping up until today. I should have followed my instincts adobe reader error 1014 to not do it. Now after the update Acrobat crashes every time I launch it. Acrobat adobe reader error 109 starts up and sits there for a few seconds then crashes. I have had it crash without fail for the last 5 times adobe reader error 1310 I have started it. Has anyone else experienced this and know of a solution? Arrg. I feel like makeing Acrobat X walk the plank. I have work to do on this computer and I can't do anything. Good https://forums.adobe.com/thread/864861 thing I still have Acrobat 9 on my main production computer. StevenD My Product Information: Acrobat Pro 10.1, Windows Top 2011-10-12 14:44:01 #1 KellyMcC Registered: Jul 11 2011 Posts: 389 Have you tried Help > Repair Acrobat Installation? Does it crash when opening a specific file, or just launch and bomb without you doing anything? Have you checked your PC for corrupt or damaged fonts? Kelly McCathran Adobe Community Expert Certified Technical Trainer+ Top 2011-10-12 14:54:52 #2 StevenD Registered: https://acrobatusers.com/forum/general-acrobat-topics/acrobat-x-professional-crashes-and-crashes-and-crashes-after-updating/ Oct 6 2006 Posts: 368 I have tried to open a document 2x and the other 4x just launching Acrobat and I get the same results. The first thing I tried was Repair Acrobat Installation but it crashes even after doing that. I have not checked my Windows machine for corrupt or damaged fonts. Everything was working just fine before I unwisely decided to update Acrobat. StevenD Top 2011-10-12 16:42:53 #3 KellyMcC Registered: Jul 11 2011 Posts: 389 So sorry this is happening. There may be more going on than just the update, or I would have seen a revolt of many users on the forums. Can you try to uninstall and re-install Acrobat? Kelly McCathran Adobe Community Expert Certified Technical Trainer+ Top 2011-10-13 01:48:43 #4 lingt Registered: Oct 10 2011 Posts: 3 I have used Acrobat Pro 10.0.1 for the last year and it has proven to be a good product. I updated to Acrobat 10.1 and now suffer crashes when opening files that have any page actions, which are used a lot within the companys electronic library. I use Windows XP, but when using 10.1 Reader on a Windows 7 computer, there appears to be no problem. I have reverted to Acrobat 10.0.1 and have restored sanity to the company. There does appear to be a snag within 10.1 that needs to be addressed. (see Acrobat 10.1 snags on this forum) Top
complaints from your users that Adobe Reader http://terenceluk.blogspot.com/2012/01/adobe-reader-x-1012-crashes-whenever.html X (10.1.2) crashes whenever they try to print from their Windows 7 32-bit workstations. As soon as the users try to open the print window, Adobe shuts down. Reviewing the event logs, you see event IDs 1000 and 1001 logged in the Application logs: Event adobe reader ID 1000 Error Faulting application name: AcroRd32.exe, version: 10.1.2.45, time stamp: 0x4f02e382Faulting module name: AcroRd32.exe, version: 10.1.2.45, time stamp: 0x4f02e382Exception code: 0xc0000005Fault offset: 0x0005e985Faulting process id: 0xe18Faulting application start time: 0x01ccdebd99cc2c22Faulting application path: C:\Program Files\Adobe\Reader 10.0\Reader\AcroRd32.exeFaulting module path: C:\Program Files\Adobe\Reader 10.0\Reader\AcroRd32.exeReport Id: e3486582-4ab0-11e1-a248-005056be608e Event ID 1001 adobe reader error Information Fault bucket 2778652943, type 1Event Name: APPCRASHResponse: http://oca.microsoft.com/resredir.aspx?SID=20173&iBucketTable=1&iBucket=-1516314353&BucketHash=562c3c70ba40be4a22c1f7dcbd9cc36cCab Id: 0 Problem signature:P1: AcroRd32.exeP2: 10.1.2.45P3: 4f02e382P4: AcroRd32.exeP5: 10.1.2.45P6: 4f02e382P7: c0000005P8: 0005e985P9: P10: Attached files:D:\Users\Miranda\AppData\Local\Temp\WER7845.tmp.WERInternalMetadata.xml These files may be available here:D:\Users\Miranda\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_AcroRd32.exe_273bd88dc0e0dbfc9662d58705c9fe14cef6039_086e9170 Analysis symbol: Rechecking for solution: 0Report Id: e3486582-4ab0-11e1-a248-005056be608eReport Status: 0 Solution With a bit of research and weeding through threads that had solutions such as checking the printer shared name, I finally found the solution here: http://forums.adobe.com/message/3499925 This problem is apparently caused by Adobe Reader X's Protected Mode at startup feature shown here: While disabling this feature is probably going to be a security vulnerability, I have 50+ virtual desktops that I need to fix before the weekend ends so I went ahead and applied the following registry change to the master image, recomposed my VMware View virtual desktops and was on my way: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\10.0\FeatureLockDown]"bProtectedM