For many years I’m using Adobe Acrobat Reader to read PDF documents. Recently I started getting an annoying popup prompt for my Adobe ID while opening PDFs. I don’t have one and don’t plan to get one – it is just useless to me at this point.
[ Disclaimer: This worked for me with Adobe Acrobat Reader 11. Now I’m using Reader DC, but I’ve never got Adobe ID login prompt here and I don’t know why. ]
Here is the way to get rid of this prompt:
- Open Registry Editor (and be extra careful there!)
- Go to “HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\11.0\Workflows” (if you don’t have “Workflows” key, just create one)
- Create new “DWORD (32-bit)” Value with name “bEnableAcrobatHS” and value “0”
That’s all – short and simple!
Thank you so much for this excellent solution!!!
Thank you so much! have a nice day!!!
Will this work for Acrobat DC?
Maybe. Feel free to check and update here.
Didnt work for DC
Thanks for the solution … Works perfectly for Adobe Acrobat DC … No more annoying pop-up for Sign-Ins.
just find the correct folder in “HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\DC\Workflows in “regedit.exe”
Works like a Charm …
Thanks once again for the solution
how to solve this problem with Adobe Acrobat Pro DC. Please help
No idea, never used DC. But people in the comments claim they have the solution.
I just tried this with Acrobat DC Standard. It did not work, I still get the prompt to sign in in order to activate/run the program.
Did you try the registry key for Acrobar Reader that I posted or the key for Acrobat DC from the comments above?
Getting nowhere with this. There is no “Acrobat DC” key under Adobe – there is 11.0, and 2015, I added the DWORD value in both locations but still get the same prompt.
Maybe try to create “HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\DC\Workflows” and add DWORD value there? (As I said, just guessing…)
thx,it really works!
Thank you so much that help a lot
Has anyone tried adding this in a way that will affect all Terminal Server users?
Great solution!
thank you so much for solving this annoying issue for me!
much appriciated
Yes that fixed it. Just have to follow the correct path. Worked. After 2 years. haha.. Thanks