Skip to main content
Participant
July 20, 2016
Answered

IMSLib.DLL error persists... Have tried all forum suggestions

  • July 20, 2016
  • 1 reply
  • 6100 views

I continue to receive the error "Installation Problem: IMSLib not found. Acrobat services will not work."

This is a new purchase, download, and installation of Acrobat Pro DC on a Windows 7 x64 desktop PC. I receive no errors during installation. I do not have Photoshop or other CC applications installed. I have tried all the suggestions in the earlier thread related to this issue (Installation Problem: IMSLIB not found. Acrobat Services will not work.). Approaches I have tried include (full restarts of Windows between any delete/install step):

1) Uninstalled old previously installed versions of Acrobat Pro 9 and Acrobat Reader. Ran the Adobe CC cleaner in both the new (DC) and old (CS) versions.

2) Uninstalled all other Adobe software on computer (eg: Flash)

2) Deleted all Adobe directories under Common Files and user AppData

3) Reinstalled CC and Acrobat DC Pro from scratch (I have now done the uninstall/reinstall 3 times)

4) Reinstalled Adobe Application Manager

5) Ran "Repair Installation" inside Acrobat DC Pro

6) Did the regsvr32 -u and -i options to rejigger the registry. It reported an error finding the DLL file.

7) Manually copied IMSLib.DLL from the Adobe installation directories to System32 and SysWOW64 Windows directories (I tried all 3 of the different versions in the underlying directories... They have different file sizes.)

Nothing changes the symptom. Opening either Pro DC or Reader DC gives the dll error and no extended services.

Please advise. I must get this working soon or request a refund and install a competing product. PDFs are a critical part of my work.

This topic has been closed for replies.
Correct answer KenMolay

Additional info that may be important... I run Windows off an SSD C: drive. My default installation directory for all programs is on my conventional D: drive. So Acrobat is not getting installed under the C:/Program Files (x86) directory it might be expecting. As an experiment, I tried copying the Adobe directory structure and all DLL files from my D drive to the C drive. It didn't solve the problem.


Closing this off with resolution. I changed my default installation directory back to C:/Program Files (x86) and reinstalled. Everything worked properly, with no more IMSLib error.

This should be worked on by the installation development team at some point. You can't assume an installation directory with no ability to customize or change the location. Plenty of people use small OS disk partitions and need to install applications in other directories or drives.

1 reply

Sarojini_Nagar
Participating Frequently
July 20, 2016

Hi klmonline ,

We are sorry for the inconvenience.

Try booting your computer in safe mode with networking and check if you able to launch Acrobat DC without errors. .

To boot the system to safe mode with networking you would need to restart the computer and Tap F8 key from the key board continuously until you get a screen with Advanced boot option .

Use the arrow keys to select safe mode with networking .

Also try referring this article : Can't sign in to Extension Builder

                                              Error: "The file AdobePDF.dll is needed" | Adobe Creative Suite 3 on 64-bit Windows

Let us know how it goes.

Regards

Sarojini

KenMolayAuthor
Participant
July 20, 2016

No difference in symptoms. Launching Acrobat DC in Safe Mode gives the same IMSLib.dll error.

I tried downloading the dll from your referenced Extension Builder thread and placed it in my Acrobat library with no effect. The Adobe Creative Suite 3 thread seems to have no relation to this problem and references another dll entirely.

KenMolayAuthor
Participant
July 20, 2016

Additional info that may be important... I run Windows off an SSD C: drive. My default installation directory for all programs is on my conventional D: drive. So Acrobat is not getting installed under the C:/Program Files (x86) directory it might be expecting. As an experiment, I tried copying the Adobe directory structure and all DLL files from my D drive to the C drive. It didn't solve the problem.