SERIOUS ADOBE ACROBAT PROFESSIONAL 8 ERROR

I had this error as well, but solved it on Vista x64

1. Have deactivated CS3 Web Premium via Photoshop,
2. made a full CS3 uninstall (Adobe did not uninstall correctly)
3. run CS3Clean.exe available from Adobe site
4. run TuneUp Utilities utility called Registry Cleaner
5. restart
6. deleted all Adobe folders under c:\programdata, c:\users\USER\AppData\Roaming, c:\Program Files (x86)\Adobe and c:\Program Files (x86)\Common files\Adobe
7. some files (Adobe PDF!) had ownership set SYSTEM, so I could not delete it, but changing ownership and permission helped:

takeown /F * /R /U "rADo" /S "NOTEBOOK"
icacls * /grant rADo:(F) /C /T /Q

8. installed CS3, including Acrobat 8 Pro
9. run manually Updater5/AdobeUpdater.exe, as Administrator, 3 times
10. everything works now :-)

Kevin:

I did as you suggested but it does not create a log file.

I did find the aum.log file which indicates that after I applied 8.1 Acrobat: "Could not load adobe_aum2pcd.dll"

The other strange thing about the log file is that while the day stamp is correct, the actual time stamp is out by +4 hours.

I can currently create PDFs from some documents, but not all documents, it is really a hit and miss venture.

I also have my activation menus greyed out, but this happened in V7.

Running Vista Ultimate 32 & 64, I am actually doing better under 64 for some reason.

For any designer, Acrobat is pivotal in the proofing process. Maybe I've been lucky all these years, but this is a real mess.

How absoutely wonderfull. I have been struggling with this issue since June and have constantly been checking the web for solutions. I thought I was alone in the woods. Thank you everbody for all of your hard work and I look forward to seeing the patch come out soon.

I'm pleased that there has been progress on this issue (or "these issues" as the case may be <smile>), at least as they're experienced by people with Vista installed.<br /><br />Has there been any further work done to isolate the problem as experienced by people using XP? As I previously mentioned, because I experienced this problem on my XP laptop, when I later installed CS3 with Acrobat 8.0 (from media, with a serial number) on my new, clean-install XP desktop I turned off the Adobe Updater (by having Zone Alarm automatically deny it all access), and Acrobat 8.0 works fine. I'd like to keep current with updates -- but don't dare turn on the updater, until I'm certain that it won't break my currently working installation. So I hope that once the Vista-related problems are patched, some effort will be put into figuring out the XP-related problems too.

All,

Today I worked with Kevin Cheng of Adobe to allow him remote access to my system, facilitating the testing of a fix. I am pleased to report, that it appears that Kevin and the team are near to being a a position wherby they can can release a patch that fixes this issue. Whilst, the patch worked flawlesly on my PC, and imeadiately post applying it, we were able to verify that Acrobat no longer hangs on startup, and that activation functioned as described, I believe that all of you will appreciate that we should allow the team at Adobe, to continue honing down and certifying that the fix, is indeed robust enough to be released. Whilst you all want and need this patch ASAP, clearly you would want that it is tested sufficiently and to a standard that will resolve this issue. Whilst of course there is no gurantee that it will fix all and each of your problem (as individual issues reported here, might not be the same issue), I can assure you that the explanation given by Kevin to me as to the cause of this problem, is credible and also explains the reason as to why this has taken so long to isolate (also why it was not reproducable in-house for them). Patience is a virtue > I am sure that they will shortly post a fix/patch for this issue. My thanks and admiration to Kevin and the entire team there at Adobe, who diligently and patiently worked to track down this issue.

Best regards
Mark Levinsohn

Adobe's download manager tells me that there are no new updates.

The problem has been solved on my system! Acrobat Pro 8.0, the 8.1 update, and a further update downloaded from within ver 8.1 have all installed successfully and Acrobat opens and apparently functions as it should. This was just accomplished within the last half hour. Here's how:

I had a similar problem with another application that I use frequently. It also had a "stopped working" problem under Vista. I tracked the problem down by uninstalling software items one-by-one through the Add/Remove function followed by starting that application after each uninstallation until it worked. The application started and runs normally after uninstalling Windows Mobile Device Center 6.1.

I took a chance on reinstalling Acrobat. Windows Mobile Device Center remained uninstalled. Acrobat installed, started, and activated smoothly and now runs normally.

So, I'm wondering whether others with this "Acrobat stopped working" problem have Windows Mobile Device Center (WMBC) installed on your systems and whether uninstalling WMDC will allow Acrobat to activate and function on your systems as it did on mine.

Hi all,

I was bought Adobe Acrobat 8 in Slovenian Language, but when I run it, I receive error "A serious error has been detected...."
So I call local support in my country, and they told me, that I need to change language from Slovenian to English, and now is working!!
How to change language: Press and hold Ctrl and then double click on Acrobat. A window will show, where you can change language.

Hope, this will help to someone who is using non-English version of Adobe.

Hi all,

I am in the progress of validating the solution / workaround for addressing this issue (on Vista). But I need more volunteers to work with me directly on testing the simple patch.

For those who still experience the issue on Vista (Not XP) and are willing to help, please drop me an email "kcheng@adobe.com"

Thanks again for your patient.

Best regards,
-Kevin Cheng
ALM Quality Engineering Manager

Enough. We don't need a "thread cop."