Reader 9 won't open PDF from web browser

I'm glad I came here because I was having the same problem. I followed the suggestion about changing the
Edit>preferences>Internet (checking) then unchecking the same, and it seems to have worked.

If you are trying to use the Adobe Reader 9 web browser plug-in in Windows 7 Beta, in the words of Donnie Brosco: "Forget About It!"

Download and install the .exe version of Foxit Reader. Opens PDFs in the three browsers I tried: Opera 10a, Mozilla SeaMonkey 1.1.14, and IE8. You can fill out the IRS tax forms with it and open encypted PDFs that require a password. ;)

WEll I am sorry if trouble with Adobe Reader v9 is "off topic" for this thread. I thought that was what we were trying to fix? My troubles with reader 9 have certainly compounded as I have tried the various fixes suggested, but the primary "thread" remains the same - that of not being able to, open reader 9.

That would be terrific only I cannot open Adobe Reader v 9 at ALL.

Bill; If I could delete or unistall Reader 9 I believe I could re-install it or another resding program and solve my problem - which has grown to one of the Adobe Reader 9 resisting - in fact, refusing to allow - the uninstallation process.

Thanks for your help and WHERE is Adobe????????

I had the same problem (not being able to open PDFs in a web browser) even though I had just downloaded Adobe 9.0. I tried opening 9.0 Reader, going to Help, and clicking on "Repair Adobe Reader Installation," but that didn't work. I then removed 9.0 using the usual Control Panel/Remove Program method (I did not remove Adobe Standard 6.0, Adobe.com, or other Adobe programs). Presto! It worked. Good luck everybody!

Deb;

Thanks for the suggestion. I can find the Adobe files and delete them all EXCEPT Adobe Reader v 9. So, since I cannot delete it, I seem to be at a standstill here.

And, I agree, it is time for Adobe to jump in and help us.

Tom,
You may want to try searching your hard drive for any and all leftover files. With our version of XP Professional, we go under Start, Search, For Files or Folders, and search your hard drive for "Adobe". Maybe by deleting all remaining files you will be able to reinstall 9.0, if you want. Make sure to restart your computer. I've been told even if you "remove" from your control panel that some files are left behind.
Good luck.
Deb

Regarding Windows 7 Beta:
Last night, I spent several hours trying all the hacks I have read on this. Nothing works.

I tried the following without success:
1) Adding the key bBrowserIntegration as per another thread here
2) Reinstalling a set of Adobe Reader 9 registry keys (see post #15)
3) Running Adobe Reader 9 with Vista compatibility and Administrator rights
4) Running Opera 10 Alpha with Administrator rights
5) Deleting all Opera cache files
6) Trying to open a PDF both browsers, Opera 10 and IE8
7) Opening a local PDF file with the browser
8) Uninstalling Adobe Reader 9 (inc: Adobe Air, Acrobat.com) and reinstalling. (I did not have any previous pdf readers installed)
9) Changing security on nppdf32.dll to Full for all user accounts
10)Changing security on AcroRd32.exe to Full for all user accounts

Oddly, I did get a PDF to open in both Opera and IE8 a couple of times, but then no more PDF's would open in either browser.

The only thing that did work was to not open a PDF in a browser window. This meant changing Adobe Reader to not "Display PDF in browser", and changing action of MIME types in Opera to use AcroRd32.exe instead of the Acrobat Reader plug-in. When I did this, after the PDF was downloaded it would open in Adobe Reader outside the browser.

Opening PDF's in a browser works fine for me in XP and Vista. Can't get it to work in Windows 7 Beta though. I have decided to uninstall Adobe Reader 9 from Windows 7 Beta and give some other readers a try - such as Foxit Reader.

Come on Adobe, this thread is over 100 replies long with nary a peep from you. You need to address this.

Same problem is comming up with the users of my software.

I tried the registry keys, but this didn't solved the problem.

Is this bug allready taken in consideration by adobe??