1 person found this helpful
I was getting the same error after installing the Adobe Reader 10.1 update yesterday.
I could open all PDF's from within Adobe Reader X, but if I double-clicked on them from Windows Explorer, I'd get the error "you must first launch Adobe Acrobat and accept the end user licence agreement"
Strangely, it didn't affect all PDF's - some worked, some didn't! It didn't seem to be related to where the PDF's were stored either (local or on the network)
I don't have Adobe Acrobat installed, and it worked fine with Adobe Reader X (10.0)
I uninstalled Adobe Reader and reinstalled 10.0, and it worked fine. But when I run the 10.1 update again, it broke again!
So I uninstalled Adobe Reader X again, and reinstalled 10.1 from here:
And now it works fine - the update obviously broke something, whereas installing the 10.1 version from scratch works fine :-)
Hope this helps.
Thanks for the response. The file that I had used for installation was the complete file (.exe) grabbed off of the Adobe FTP site.
I did use the .exe as opposed to the .msi file to perform the installation.
As I've had a day of uninstalling and reinstalling Adobe Reader, I uninstalled 10.1 & reinstalled it using the .exe you provided, but it still works fine for me now.
I reckon if I uninstalled 10.1 and installed 10.0, then run the 10.1 update, this would break it again, but frankly, I'm sick of the sight of Adobe! I'm just glad I can double-click on my PDF's and open them again :-)
I hope you get it sorted...
Do you have Adobe Acrobat installed on your system as well? Cause from the message it looks like the PDF is trying to open itself in Adobe Acrobat and not Adobe Reader?
If you have Adobe Acrobat installed on your system as well, try launching it once, and accept the End User License Agreement.
On the two PC's that have exhibited the issues there are no other Adobe products including Acrobat that are installed.
Thanks for the response.
This is weird.
Can you please post the value of the following regsitry entry:
Is yours a 64 bit system? If so, the registry entry will be somewhat different:
I am having this same issue since the upgrade. What I find works though is if i open a pdf from the desktop or folder it works fine. If i try to open it from an attachment in my outlook 2010 i get the license agreement. I do not have this registry entry in my machine and i have added it which made no difference. If i copy the same pdf attachment to a file then it seems to work. Whatever invokes the license check from an attachment seems to be broken.
Just removed Adobe 10.1.0 and reinstalled useing the .exe from the ftp site. This seems to work. If you upgrade from 10.0 to 10.1 seems to be the only time it breaks.
I'm having the same issue after upgrading to 10.1.0 however it only occurs when trying to
open password protected PDFs. The workaround of first opening Adobe Reader and then browsing to open it works but my users cannot open them directly via a doubleclick. Uninstalling and then installing 10.1.0 fresh does not resolve this issue for us.
Did you uninstall and re-install useing the full exe downloaded from the ftp site or use the adobe website to install using download manager. I still have the problem if i get the version from the website update. All my other issues went away useing the full exe from there ftp site.
Yes I tried that, no luck. :-(
My users don't have issues opening regular PDFs, it's just the password protected ones. Have you tried a password protected one?
Just tried it with a password protected one and it opened fine
. Maybe it's a password protected pdf with combination edit/preferences/general/ "enable protected mode at startup" . We have that turned off because it breaks our third party apps we use in combination.
Ok, I've discovered what the cause of my issue is. When Reader 10 first came out
I made a registry change in order to prevent the super annoying and end-user confusing
pop up box that would happen, the one that asks about opening a PDF in protected mode or something (I dont recall exactly). Anyways I just revesed this change and now the PDFs open fine. Now I just have to do some testing to determine if this is going to make those popups come back or not...since I had previously changed two different reg settings.
...is the one that I just changed back to "1" and resolves the issue
...is the other one I had set to "0" that doesnt seem to affect the "User License Agreement" issue
I also was pushing the
THat didn't seem to have any effect.
I think the other key you had might be the one causing your password protected issue. It is the only difference between mine and your setups from these posts.
So it comes down
1: useing the adobe website to upgrade to 10.1.0 breaks the reader integration in different ways.
2: installing full version from ftp site fixes the issue except for password protected pdf if you have the
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\10.0\FeatureLockDown set to 0
changing back to 1 repairs this issue.
Hmmmm maybe 10.2
1. Updated originally via SCUP with the published 10.1.0 files. This broke my customizations (accept EULA, disable protected mode, remove Auto Update).
2. Then downloaded MSI from Adobe FTP site, and crated new custom installation using Customization Wizard, and pushed that out.
3. Now users are receiving the message from some, not all, PDF files when opening them up by double-clicking the file. All files are over the network, and some opened but most did not.
4. removed the bProtectedMode (no one has mentioned that THIS is the key you need to enable (1) or remove) within the "FeatureLockdown" folder, and this enables/disables the protected mode on startup (Edit>Preferences>General).
While this fixes this issue, it still brings back Protected Mode which on one test, blocked a PDF from view one time, but didn't the other (buggy much???). Also, we originally disabled this because users were being blocked from opening PDF's over our network for some reason.
So it appears 10.1.0 either broke the Enable Startup Mode feature, or the registry edit "bProtectedMode" is broken for disabling the feature.
Help me Adobe... you're my only hope...