I have the same problem. At this point I uninstalled CS5 to keep only CS6 and will try the reinstall Acrobat X pro and clear some files like sugggested.

exactly the same case - did reactivate as you instructed - now it works OK, thanks for the tip

Deactivation/Reactivation fix seemed to work...for now.

I have to say i'm really disappointed here. It seems like Adobe doesn't even recognize the full extent of the problem.

Maybe i've just been lucky, but this is the first time i've had to post/deal with an Adobe bug like this.

@Manish-Sharma #37 The link to this problem does not apply in any way to my situation. I installed CS6 on a brand new machine that never had CS5.5 on it. I still have the failure to launch problem with Acrobat X. I did do the deactivate/reactivate procedure (without deleting the cache file) and it is working for now. Do I need to wait 30 days to see if it is going to reappear?

Thank you very much, Matt! It seems to work an I will believe in the "permanent fix"

no problems

I am glad it is helping some people out.

I'd figure it would be best to post the official support answer so that everyone knows it's legit. 

So many people have answers but being in a large company, we cannot afford to guess which is a proper fix.

So we went direct!

I am so glad to have found this forum, Acrobat X just stopped working for me also.

I am on a Windows 7 64-bit, most recent service pack system.

Before I installed Design Premium CS6, on May 26th, I completely removed CS4 and CS5.5 except for the serial numbers, and ran a totally cleanup on my system.

It installed and has worked flawlessly until today.

I did the deactivate and reactivate function and Acrobat X now works, but instead of actually running the executable and opening the program I get the dialogue box asking if I want to run this program each and every time I open either the program, or a pdf file.

Does anyone have a fix for that issue?  I will try uninstalling and re-installing just Acrobat and see if that corrects the issue, will post results when done.

Thanks Mike, I turned it off and it does fix the problem, as yes, the program opens when you select yes.  Unfortunately it is a global change, you cannot select that option for just Acrobat.  Will try removing just Acrobat and reloading next.

Francie

Mike, thanks for posting the additional information, right now I am under a tight production deadline and keeping fingers crossed that Photoshop, InDesign and Illustrator stay stable.  Will definitely pursue the other possibilities when I get the chance!

Cheers!

Francie

Thanks for your help Amrita!

In my office we have some nfr licenses and, for policy, some computers have installed only Acrobat X of the CS6 suite (no Photoshop ecc...). There is a workaround in this situation?

Thanks

I've had exactly the same issue with Acrobat X Pro today. I followed the transcript Raghu - Matt.

The issue seems to have been resolved now.

Thanks - worked for me.

Thanks so much Amarita... followed through with instructions and fixed my problem with Acrobat X not starting!

On the Mac, in the applications folder are CS6 apps downloaded from Creative Cloud, and inside each products folder is that products uninstaller. That is the uninstaller I used the first time to remove Acrobat X Pro.

After removal by that means, Acrobat Application Manager was still verifying that my removed app was still installed. There was no way to reinstall (Acrobat).

What I was told by the chat tech I chatted with was to got to Applications > Utilities > Adobe Installers Which is from where he recomended I do all my uninstalls.

So, from there I clicked on Acrobat X Pro and followed the screen instructions.

When I then launched Adobe Application Manager, teh Install button next to Acrobat was active and I was able to reinstall Acrobat.

Because after removing a previous version of CS, my photoshop CS6 app was announcing a missing file and that I needed to uninstall and reinstall Photoshop - more an annoyance than an actual necssity since Photoshop CS6 was working fine despite the notification window alerting me to a missing file Photoshop needed to operate... Since the uninstall and reinstall of Acrobat went so well, I followed suit with Photoshop CS6, removing it from the Applications > Utilities > Adobe Installers folder. When I launched AAM, the install next to Photoshop was available. I downloaded it and intalled ... everything is working fine.

So... Here I am, back after another 30 day cycle! About 30 days ago I tried the deactivate/reactivate with assurances that I'd never see the problem again. Today I tried to open Acrobat X only to experience the exact same problem I had ~30 days ago.

Amrita: Please stop assuring us that the problem is really fixed if it actually isn't!!

Why are your legitimate, paying customers being punished by the methods you're using to stop software piracy?!? As a legitimate customer, I don't appreciate being punished for the crimes of others.

I used the deactivate/reactivate fix again today. For the moment, it's working again. But at this point I have ZERO confidence that I won't need to repeat this process in another 30 days.

Please get this problem fixed. Don't make me come back in another 30 days.

John

Will Adobe's solution address Creative Cloud subscribers as well? I'm experiencing the issue, but the "deactivate a separate product" solution is completely ineffective (and the cache.db fix, given to me by Adobe support, only fixed the problem for about 2 hours).

I followed the steps stated in 46. mattlok1010's transcript, which is similar to the "correct" answer here. And it worked for a little while then stoped working again when I went to open another PDF.

I re-read the answer and discovered:

In case you still face a problem , try relaunching the other CS6 app once more and then launch Acrobat.

This was an essential step for me as it completed the registration. As soon as I opened Photoshop, it came up with a bubble "registration complete" and Acrobat is working again.

So 2 months later is there still not an actual fix for this that does not involve deactiviating some other unrelated product? I'm guessing since we are not "cloud" users that we have perpetual serial numbers. Being told to mess with some unrelated application to fix another just seems like the wrong way of dealing with this. How about instead of hacking the symptom, we get a fix for the problem in the form of an update patch. This has beeing going on for over 2 months now and the only "official" fix is to hack away at the activation of another program to fix this one and now we are told that is really only a hacked up fix for "cloud" users. What about those who dropped nearly 2 grand at once for this suite?