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

    Participant
    February 20, 2009
    Maybe now that this has happened (see below) they will step it up a bit on 9.1.

    http://www.adobe.com/support/security/advisories/apsa09-01.html
    February 19, 2009
    I have to be able to read PDFs so I went to the Foxit site that Bill Kov referenced and downloaded the program. It seems to work great and it's very fast. Good luck.
    Hopefully Adobe will get on with a fix to this crazy problem.
    Participant
    February 19, 2009
    Same thing for me Tony Bosco. The LocalLow folder exist and i can only start acrobat reader 9 on my terminal server (windows 2008 enterprise) if i'm logged-in as an administrator. If I try to start it as a user, I get Visual C++ Runtime Library error.
    February 19, 2009
    Kevin,
    I have the LocalLow folder in the directory you reference. It doesn't seem to make things any better. It's funny I can use Reader 9.0 if I'm logged into my Administrator account (I don't get the Visual C++ error), but not my User account. Has anyone else noticed this?
    February 19, 2009
    Ge3oR
    02.04.2009 at 03:14PM PST, ID: 23554837
    I had the same problem on my 2008 TS server with Adobe Acrobat Pro 9. After some investigation with process monitor, I saw that Acrobat was crashing after searching for the c:\users\USERXX\appdata\Locallow folder. If I create the folder manually, everything works. This problem was only with Roaming profile and mandatory roaming profile.
    A search then on MS Support and found this :

    The LocalLow folder may not be created on a Windows Vista SP1-based computer or on a Windows Server 2008-based computer when roaming profiles are used in a domain environment
    http://support.microsoft.com/kb/955555/en-us
    January 24, 2010

    As users with roaming profiles, it is a very important issue to you. 
    However, in the scheme of things, it may not be very important to the 
    overall user base. If this is a problem for your company, have everyone 
    in your company report the bug in the Adobe Bug report form. The more 
    users they know are effected, the more likely it will be fixed. Believe 
    me if IBM, ATT or the DOD had the problem, it would be fixed ASAP. Your 
    company needs to help make it an important issue to Adobe.

    Participant
    January 25, 2010

    NICE ATTITUDE!

    Participating Frequently
    February 18, 2009
    Hey Daved - we can all say "Check is in the mail".

    Can you say "We're from Adobe and we're here to screw your computer up".?

    I finally got sick of their lack of even basic service and made the switch to FoxIt.

    B
    Participant
    February 17, 2009
    I am so glad to have found this forum. I am the Desktop Support Manager for a large urban school district on the west coast in the US and this is huge for us. Most of our users have roaming profiles dictated by group policy in Active Directory where all the Application Data is backed up to a SAN. This error message started happening a month ago and has since caused numerous problems/corruptions of profiles on the local machine not to mention the errors and non-functioning of Adobe Reader/Acrobat/CS3/Flash etc. I guess we will go with FoxIt or roll back to Reader 8. This is really crazy because I imagine many public and private environments have the same basic setup we do. BTW - Our Web Design group does have the support package and was told they will be notified if a solution becomes available. Can you say 'check's in the mail?'
    Participating Frequently
    February 14, 2009
    Smiddy -I wouldn't expect any help - I had an open Tech Support ticket on this very same issue for almost 3 weeks. Someone finally condesended to answer after 3 weeks and the message was, to paraphrase it "if you want support for this buy a support program".

    That's the day that I deleted the program and got FoxIt. It takes 2mb of space and works fine except for a minor printing issue that they fixed.

    I DO hope that Adobe is lurking someplace. I'm a professional speaker and present on customer service - Adobe's given me some great new material!
    Participant
    February 14, 2009
    Nice work Adobe. We spend tens of thousands on a VL for Creative Suite 4 and can't deploy it without users getting this error. I can only scratch my head as I wonder why the hell Adobe is coldly abondoning the larger -and I imagine, highly lucrative- corporate market. The business development manager must be on crack.
    Participating Frequently
    February 12, 2009
    Believe me, no you don't unless you just want to experiment and come up with a fix.

    Allen - Hmmmm. The only issue I had with FoxIt was with printing. It somehow locked up my spooler but that seems fixed now.

    I've become very soured with Adobe folks. Very dissatisfied with how they're handling this debacle.

    They have assumed a position of complete deniability and I can't think of a better way to drive existing and potential clients away.

    B