Temporary Fix!!!

I discovered this same problem today on an XP machine and at this time can't explain what caused it but it is working at the moment.  I hope this is helpful for someone. It was a headache for me and I lost valuable time trying to figure it out.

1.  I checked all paths and variables.  Everything looked good.

2.  I uninstalled 10.1.2 and reinstalled.  Still no Good

3.  I uninstalled 10.1.2 and reinstalled 10.1.1.  Still no Good

4.  I checked all the registry paths.  They "appear" to be correct.

5.  I renamed acrord32.exe to bob.exe and double clicked it.  Adobe opened successfully.

6.  I renamed it to reader32.exe and double clicked it again.  Adobe opened successfully.

7.  I then double clicked a PDF file and browsed to the new reader32.exe Adobe Reader Executable.

8.  I clicked the box always use this programs as default.  <-- no exact.  going off memory.

9.  Double checked that PDF's open in Explorer, IE, Outlook, Etc.  I am able to open all PDF files again.

NOTE:  I dont know what caused this or why renaming the .exe fixes it, but it has allowed me to continue working for the day.  I also dont know what kind of problems this will create when updating to a new version of adobe reader later down the road. 

Chris Rahm

RahmTech Computing, Inc.

www.rahmtech.com

Rename it to acrord32.exe and I start receiving the same error msg bruno does in the image above.  It really is strange.  We have seen spyware programs prevent removal software from running based off its name and we would have to rename the software in order for it to run long enough to remove infections, but I have never seen or understand why that would be the case for Adobe Reader.  What would be the purpose. 

Hi again.

The temporary solution that I found to work correctly with Adobe was rename the acrord32.exe file to another name like acrord32222.exe for example like ChrisRahm did.

If I changed the name to the original one acrord32.exe the same error appeared.

A few weeks ago I ran the autoruns.exe windows program that you can find in internet. It found an incorrect link to acrord32.exe in windows registry ("File not found..."). I deleted it and renamed the acrord32222.exe file to the original one acrord32.exe. Now Adobe Acrobat works in my XP.

Can you try it in yours?

Regards from Portugal.

It appears that renaming it worked for opening PDF documents but not printing.    I was able to remotely log back in this morning and run autoruns.exe and locate the "File Not Found" Issue bruno mentioned above and deleted it.  I then redirected PDF file assocations to the default acrord32.exe from my renamed reader.exe, restarted the computer and now adobe reader is reading and printing as expected. 

Thanks everyone for your input on this situation.

Chris Rahm

I just remember that the incorrect registry key was placed in the "image path" of autoruns.exe. The message was "File not found: c:\program files\Adobe Reader 10.0\Reader\AcroRd32.exe