Skip to main content
Participant
July 11, 2008
Question

Reader 9.0 AcroRd32.exe caused Microsoft Visual C++ Runtime Library error

  • July 11, 2008
  • 131 replies
  • 194996 views
A client has updated Adobe Reader 8.1 to 9.0 on several machines and now cannot use Adobe Reader.

The program start, the Adobe Reader window appears but no document and then an error message is displayed that says;

"Microsoft Visual C++ Runtime Library
Program: C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe
This application has requested the runtime to terminate in an unusual
way.
Please contact the applications support team for mor information."

Adobe Reader has been removed, the computer restarted and then re-installed from a full installation package and the problem persists.

Does anyone have any ideas how to fix this?
    This topic has been closed for replies.

    131 replies

    Participating Frequently
    January 28, 2009
    Thanks so much! I'll look it up.

    I appreciate the support - maybe you could drop a note to Adobe. . . :-/

    Bill
    ~graffiti
    Legend
    January 28, 2009
    A lot of folks around here seem to recommend this one: http://www.foxitsoftware.com/
    Participating Frequently
    January 28, 2009
    Can you make any recommendations at all? I'll go on C-net later and do a review.

    Just venting here but I've uninstalled and reinstalled the program 3 different times without a solution. I guess it IS time to move on.

    This is just so unlike Adobe - putting out a product with known issues. . .
    ~graffiti
    Legend
    January 28, 2009
    >I'm currently 8 projects back because I can't read pdf files that clients have sent me.

    Not sure why. There are numerous free PDF readers out there. Try a different one.
    Participating Frequently
    January 28, 2009
    Hello Andrew and all -
    I've had an open ticket on this in tech support for a while and in reading some of these threads - I'm still confused.

    I'm on a 32 bit Vista platform.

    It appears that the best answer that I see is to uninstall this trouble maker and find a copy of the last version.

    I'm currently 8 projects back because I can't read pdf files that clients have sent me.

    I'll check back here from time to time but if anyone has a better suggestion,I'm up for it.

    Bill
    Participant
    January 28, 2009
    Its pathetic, even a request for V8 was closed by support. when I reopened it my case "disappeared"!
    Participant
    January 25, 2009
    I can't quite believe this is still outstanding.

    Regardless of how bad this looks on Adobe as an example of their apparent disregard for existing customers, they are actually selling a product that claims to be compatible with Windows environments. It is not. A subset does not equal the full thing and Adobes beta testers have really fallen short of the mark on this one.

    Like other customers I have ended up being forced in to implementing alternative products. The response times have been abysmal and it is inconceivable how badly Adobe has handled this. Senior representatives should have stepped in to calm things down, but it looks like the damage has been done now.

    It's not atypical for Adobe to be slow with development (getting with 64 bit years later than everyone else springs to mind) but this is a known bug and should be given priority over new feature sets.
    Participating Frequently
    January 8, 2009
    I posted it too!
    I also called them again... "we are aware of the issue,they sent me a link to this thread as a work around, and then... Thank you for calling."
    Participant
    January 8, 2009
    Thanks Ethan for that link - posted our issue there - hope it helps get Adobe moving more quickly.
    Participant
    January 8, 2009
    FWIW, I get similar symptoms with a very simple configuration.

    Users homed to C: work fine.
    Users homed to D: don't work.

    Vista Ultimate 64 Bit SP1.

    I don't claim this is the same issue, but the symptoms look the same to a user (me).

    I also see this w/ the Picture Manager accessory of Office 2007.

    Moving to Foxit seems to fix the Reader (but not the Picture Manager) problem. I'm unlikely to go back until this is well and truely fixed.