Update. Clearing all cache, running disk cleanups, etc etc and rebooting has solved this one! Perhaps a memory issue? ... View more

I've had the same problem for over a year, despite hours spent trying to fix the non-starting Acrobat X Pro (and hours with Adobe tech taking over my computer). After every reboot, Acrobat does nothing (no error message, just does not start up). Uninstall, reinstall, nothing helps. Solution on Win 7 64: start up Task Manager, select the Processes tab and find one or more instances of Acrobat running (if you tried to start Acrobat, more than if not). Highlight each and stop (ignoring warnings). Now Acrobat will start up normally, but with no preferences (you have to redo those each time) and works fine until another reboot. Really annoying. ... View more

A long session with Adobe tech may have cured this - related in thread 5213799 ... View more

Nothing works for me - none of the fixes make a difference. I have to get this solved, as I'm losing hours of work time and cannot send Indesign files to print without Acrobat. Part of CS6 suite (installed, not Cloud), installed way back in 2012 and everything worked fine till a week ago. Acrobat Pro X now returns a spinning wheel, then times out without starting; not a 30 day issue unless it's 30 days from some patch. Acrofix patch doesn't make a difference. Uninstall/reinstall made no difference. Deactivate and reactivate then reboot (only after a reboot) worked a couple or so times, but now makes no difference. The Properties start in box for the link was empty - typed in that to replace it but no difference. This is nuts - how do I fix it? ... View more

I'm also going around in circles with this. CS6 suite installed in 2012, everything worked fine until a couple of weeks ago, when Acrobat Pro X refused to start on Win 7 (64) system. Spinning wheel, nothing happens. Reading all the fixes: I've been through the Acrofix route (didn't help). Deactivate and reactivate; worked but only until a reboot. After any reboot, back to the start again (and potentially fails between reboots, which forces the whole attempt to get it going again). Tried uninstall / reinstall Acrobat - no change. Tried updating the Application Manager (following another suggestion online), then the deregister/register route again. No difference. It isn't viable for me to keep having to deregister/reregister and reboot continuously just to retain the use of my Acrobat X installation. And now I find that even going through the deactivate/reactivate process won't work after a reboot. Nothing restores functionality. What on earth do I try now? ... View more

An excellent question. I don't intend to upgrade to the .5 version, as from what I've seen so far it doesn't offer me enough incentive to do so. But if the bug is not fixed in the current CS5 (as opposed to fixing it in 5.5) I'll be most upset. It's cost me around eight work days in time seeking workarounds, trying to fix it and rebuilding templates in CS4, and I've now reverted to CS4 in frustration. That reversion was interesting though. The CS5 installation was on a clean, new computer so CS4 was not present. I thought I'd try loading it (Indesign alone), without removing CS5 (having seen reports that they had to be installed in the correct order). It went in fine (demanding to add Bridge CS4, which wasn't wanted) and both it and CS5 work without problems, and no reloading CS5. Chris Howes ... View more

Thanks for doing this - it works for me and removes one annoyance from CS5, that I would forget to open the window before exporting (and finding that the background export had hung, while I waited for something to happen). Now I have an immediate heads up! Thanks for sharing. ... View more

Mine was a recent installation - this is the only version of Suitcase that I have installed (from a download rather than an older disk), with no updates. ... View more

I loaded the CS5 suite as a clean install on a new computer (Win7, 64 bit) and also installed Extensis Suitcase Fusion 3 (showing version 14.0.5.93). This installed auto activation plugins in several of the CS5 applications, including Indesign. At that point there was very little on the computer: CS5, Suitcase, Office 2010. Despite assurances from Extensis that the application was 'good', the plugins caused *all* my CS5 applications to crash - actually, they refused to start up - apart from Photoshop 64 bit (the 32 bit installation also failed). Removal of the plugins from all CS5 applications enabled them to start and run properly (ignoring the fact that bits of Indesign don't work as they should, which is the subject of this thread). In my case, these plugins caused a failure in the software, as opposed to a crash once the software was running. None are now installed, though Suitcase (other than this factor) appears to run correctly. Chris ... View more

Seconded. I'm one of those affected by lock-ups when producing a pdf in the foreground (the fault is reproducible by Adobe and they have my files ...) and hopefully one day it will be solved. Looking forward to the day when the full functionality I had in CS4 is returned to me, I have already found that in trying to work in CS5 I kept forgetting to open the background processes panel to see what is happening, so if something can do that for me or remind me what is going on, seems useful to me. ... View more

Peter - I saw in a previous mail your suggestion of reinstalling CS4 to help with older files, but that it had to go in before CS5 and thus the latter should be uninstalled first as they have to be loaded in the correct order. Makes sense. In my case, it's a newly built computer so CS5 is a clean install (or else my older software would still be on it as I don't uninstall it). But, to put in CS4 Indesign must the whole Creative Suite be uninstalled, or only the CS5 Indesign component? The latter might happen, but I can't see me removing the whole suite ... ... View more

I'll look back at that earlier post asap - thanks for that note ... I've been experimenting. Don't know how much this might reveal to anyone with more knowledge than me, but here goes with some (to me) odd results; someone might benefit. Recap: my problem file is one started in CS4 and worked on in CS5. It will export pdf with a foreground script and a saved preset, but not the 'proper' export using saved presets and a background export. I went back to CS4 and opened the original file. I stripped out all content from every page (guidelines, anything) but did not touch anything on master pages (there are about 12 of these in pairs, with linked graphic content and footer text and tint boxes and so on). I exported that as .inx and brought it into CS5. The background pdf creation worked fine (though I'd much rather have the older foreground where I could watch the export for a few seconds until the pdf automatically opened in Acrobat). I then opened the CS5 file with page content and began copying/pasting each page into the new file. After every page, which variously contain linked photos, graduated tints and all sorts of elements, I ran the pdf creation and it worked every time. This could just mean that something was missed in the old file for copying over, or my creating layers again or other changes were instrumental in this. BUT: With the old file still open in CS5, the pdf creation would NOT work. Background tasks stayed at 0 (once only I saw it reach 2%) and I was unable to close the file. The moment I closed that old file (which was saved and merely open in Indesign), the pdf was correctly produced. If I closed that file before creating the pdf, it proceeded immediately. I also noted the creation of locked files (.idlk) for any file that had failed to produce its pdf in earlier tests, and that I cannot manually delete even with Indesign and Acrobat shut down (says they are in use in System). ... View more

I tried out the round-trip, reimporting from a .inx, but there was no difference in the end - the pdf creation still hangs in process, though Indesign does not (but won't allow anything to save or further export). I can't truthfully claim to be 'clean' in never reusing an old file and updating it, but this particular file was recently created from scratch in CS4 but partly worked on before importing into CS5 for completion. It still isn't completed so I'm thankful that I fund this error at this stage, instead of right on deadline. Slapped wrist for not reverting to a template every single time, but it's a separate issue to this one (in that if I can foreground export with no difficulties, then it's something within Indesign that isn't working as it should for background export, as far as I'm concerned). Thanks for your added info. Chris ... View more

Thanks Peter In this case, quite a lot of work has been done on this file since opening it in CS5 (it's a magazine destined for print), so reopening the original CS4 file is no longer an option. I understand your message though - wish I'd have known of this problem before getting to this point. I don't ever buy into 'new' software upgrades when they first appear because of hassles such as this, and naively thought that such a major issue would not still be so prevalent. Would an export to IDML, open and save in CS4 and export from there as IDML to reimport into CS5 have any benefit? All I can state as certain is that a foreground pdf creation works fine. Chris ... View more

I'm merely adding my lone voice here. New installation of CS5 InDesign (and rest of suite) on new computer (Win7 64 bit). Latest updates in place for Windows and Indesign (7.03). Open and work on CS4 file that is somewhat critical for work, and everything behaves as it should - until pdf export. Makes no difference if I try Adobe-supplied settings or my own tweaks, working from presets: the export hangs at 0 (in the background tasks panel) for a single page output (or any output). I can continue to use Indesign, but not save any changes etc because the file is in use. Every time, no exceptions. Exported as IDML and imported again; no change. I can report that the script linked a few messages back for forcing a foreground export worked first time - perfect (though a pain to have to save a pdf by this route instead of simply getting on with life and work, and I have lost faith in CS5 over this and will probably revert to CS4 for other jobs, itself a pain given that I'll be working on an old computer). This pdf export really does need a fix - can not Adobe add the ability to turn off all background tasks and thus revert to CS4 behaviour? Perhaps that's simplistic but I'd like to be given choice ... Summary: pdf export broken; forcing foreground creation solves it while adding another layer of fiddling (for me). ... View more