Acrobat reader installs, does not run

[geoB]

A client had some failure with its installation of Acrobat reader 7.1
and tried to uninstall and reinstall. An unspecified error message
resulted. When I was called in I tried Adobe's manual uninstall
directions, including deleting several registry entries. Subsequent
reinstalls appear to succeed and add all the appropriate files, yet
the program does not launch. PDFs cannot be opened.

System is running Win2000, sp4. I would greatly appreciate any leads
on what might prevent the reader from running. None of the available
Adobe versions (7,8,9) works.

Thanks.

George

 

[Pegasus [MVP]]

A client had some failure with its installation of Acrobat reader 7.1
and tried to uninstall and reinstall. An unspecified error message
resulted. When I was called in I tried Adobe's manual uninstall
directions, including deleting several registry entries. Subsequent
reinstalls appear to succeed and add all the appropriate files, yet
the program does not launch. PDFs cannot be opened.

System is running Win2000, sp4. I would greatly appreciate any leads
on what might prevent the reader from running. None of the available
Adobe versions (7,8,9) works.

Thanks.

George

What happens when you launch Acrobat from a Command Prompt? What do you see?

Seeing that this is most likely an Acrobat and not a Windows issue, I
suggest you check the Acrobat FAQs and repost the question in an Acrobat
newsroup.

 

[HxEngr]

reinstalls appear to succeed and add all the appropriate files, yet
the program does not launch.  PDFs cannot be opened.

System is running Win2000, sp4.

I too am running W2K, SP4. Not sure if this is relevant to your
situation, but every now and then I get what appears to be the same
thing - Acrobat reader will not open. However, checking Task Manager
(ctrl-alt-del, then T) and looking under processes, shows that
AcroRd32.Exe is running in multiple instances, even though none are
visible on the screen. Closing all the preexisting instances then
allows Acrobat reader to run normally. This situation comes up most
frequently when Acrobat gets opened from within my web browser
(FireFox) and also a separate instance is running standalone, as by
opening a PDF.

Steve Hendrix

 

[GeoBrooks]

Eventual solution: installed reader from foxit.

g