Hello, we`re using the Adobe Reader DC AddOn for Internetexplorer. After Windows 10 Update 2004 (May release) we can`t use the print funtion anymore.
Need help to fix the problem. Our software also use the AddOn for displaying PDF documents.
Having the same issue on several PCs that updated to Win Feature Update 2004 over the weekend - users can no longer print via Adobe Active X in IE 11
We print a lot of plans to plotter using Adobe reader DC. After update to win ver 2004 it broke the ability to print. I have tried all the suggested fix, even tried disabling Symantec AV client and nothing works. Hower I have one site
with 7 PC's and all have 2004 update and they can still print. The others just get "unable to print document" error message.
Having the same issue across multiple computer in our organization. Definately caused by the new Microsoft update.
Please help with a fix.
This reply from the above comments has fixed it for us!
I had this same issue, but I was able to just now get it working again after I disabled the "Enable Protected Mode at startup" feature under Edit > Preferences > Security (Enhanced)
This did not resolve the issue for us. Just gives message, The document can not be printed.
I uninstalled Adobe Acobat DC in an attempt to reinstall and fix the issue and the machine will no longer boot.
Disabling "Enable Protected Mode at startup" via the Acrobat Edit > Preferences > Security (Enhanced) menu resolved my issue as well. Thank you, Jenniferb79366475.
As a side note, this issue only affected my PC's that were running Acrobat Reader DC. PC's running Acrobat Pro DC had no issues.
Our company has lost printing ability from Acobat DC to plotters after 2004 Update. Just gives an unable to print error. Worked fine until ver 2004 update.
Adobe Reader DC simply will not run in my laptop since Win10 ver2004 update took place.
Reverting Windows to the previous versions, everything works fine, but under Win10 2004 Reader will not even start, despite reinstalling the program in my computer.
About the specific issue in this post, I had a similar one with my Wireless HP printer after Win10 upgrade, and after a long time debugging it, the issue was the connection port had to bee redefined, maybe something alike may sort this issue out, good luck!
We are experiencing the exact same issue with Acrobat Reader embedded in our Infor Syteline ERP Print Preview form. AR works fine when you open PDF direct. If you look in Win10 Event Logs you'll notice a lot of new errors and warnings, some of which are COM failures which may be related to this issue. Control tested the problem, Win10 1909 and older no issue, Win10 2004 - Acrobat Print Button is dead. Note that all the other Acrobat buttons to Zoom, Save, Show Tools work OK. Even the Tools Print button and ctrl+P don't work. You click on the Print button and no printer dialog appears. I believe MS tightened down some security which prevents Acrobat print access when not the root process. MS does it to us again - just when I was gaining confidence in Win10 and mass deploying it. ADOBE WAKE UP - WE'RE NOT IMAGINING THE PROBLEM. Thanks, George
I am having an issue with printing as well, but I cannot print through acrobat dc, foxit, etc. This just started also.
Do we have a solution for this or the update from Microsoft has not been released yet?
Thanks for reporting the issue here.
The issue is from Microsoft's end and was due to their latest release 2004 released.
They have acknowledged the same and will be working on the same.
Please do let us know, if anything is required from our end.
It appears the issue achnowledged by Microsoft is unrelated to the Adobe print dialog not working in the IE Addon. This started with the 2004 update but so far doesn't appear to be acknowledged. The only workaround seems to be disabling the reader sandbox protected mode.
Microsoft acknowledge an issue regarding the printer spooler and fixed the bug in KB4567523. However, the issue we are talking about here is not related to the spooler issue.
I did some tests with the latest Optional Update 20.009.20074, but the issue is still not fixed.
Do you have an estimated release date for a patch regarding this issue ?
I have the same issue after updating to 2004, printing pdf from IE plug-in does not work anymore nothing happens at al when i klick the print icon and if i save the file and open it in DC the printing works so its for sure a compatiblity issue with 2004 that Adobe has to fix.
I have found that if you saved the file locally the launch it then Adobe Reader will print, just not through IE and I don't think any other browswer either
we've noticed this as well.
This is an issue rrelated specifically to the Adobe plugin in IE 11. A few notes on this.
-This only seems to affect the msi installation not the .exe installation
-Disabling the plugin in IE has been our workaround
-There is no error message it just doesnt print
- The kb's mentioned in this post do not resolve this issue.
-We have not tried this in any other browser as all of our business applications require internet explorer.
Disabling the Adobe plug-in in IE fixed the issue for us. Thanks for the tip!
Do you know if ther is group Policy for this as we have hundreds of computers to fix with this issue?
Our company is going to try making a GPO to disable the Adobe add-in based off these intructions https://social.technet.microsoft.com/wiki/contents/articles/11406.how-to-disable-internet-explorer-i...
is there any solution available?
I am also waiting on a solution to this problem.
I rarely post issues like this, but these days, this kind of thing is becoming FAR too commonplace. And it's because the Big Players who make this stuff have their tech employees spend LESS AND LESS TIME ACTUALLY SOLVING ISSUES OR TROUBLESHOOTING the frequent almost daily updates that plague our systems these days. Oh, I might add I'm an experienced IT tech and manager with over 30 years experience, currently an IT Infrastructure Specialist, so I've seen the Tech Industry become less and less responsive to making things work and more and more concerned only with spending as little time on something as possible and shoving another buck up the corporations behind.
That said, I have a client with this SAME IDENTICAL PROBLEM. After a WINDOWS UPDATE. Which is, what, about the 100th time this has happened since Windows 10 was forced down all our throats, right? You techs really working the field know, right? Unfortunately, all the hapless souls who work for MS or Adobe, largely from overseas, haven't a clue and are trained to do one thing: Get rid of complaining customers quickly, who CARES if it works?!?!
THIS subject is an example, hence why I'm here complaining. Typical corporate response: "Hmmm, WE don't have the problem. It just CAN'T be so! So to STALL AROUND, we need to ask 25 more questions: Exactly what time of day was it? What is the .dll used for the add-on? (Don't know? Ah, that's the problem! LOL) Can you give us your data to test (they KNOW you can't and won't do that, so another STALL!" Same ol' runaround.
To be fair, this likely is NOT an Adobe problem! Windows 10 Feature Update 2004 has broken more machines than it's successfully updated, I think! Close to it, anyway! So it's OBVIOUSLY WINDOWS 10 UPDATE BROKE THIS and point 2 is ADOBE SHOULD BE AWARE OF IT ALREADY. Quit beating around the bush.
CGM simply wants to know, they have the BEST QUESTION: "are you sure that you cannot reproduce this "error" with Windows 10 Update 2004 from 28th of May? Seems that many others have the same issue using the print function."
BINGO! Yep, LOTS of others. So bone up, admit there's a problem, and get working on it! QUIT a) asking more useless pointless questions that mean nothing but is a delay tactic, and b) actually spend some TIME working on the actual issue. Perhaps a GREAT idea for corporations like Adobe and Microsoft would be to ACTUALLY SPEND AS MUCH TIME ON TROUBLESHOOTING THIS AS YOU DO TRACKING TIME AND PRODUCTIVITY NUMBERS! Wow, you may actually ACCOMPLISH something then!
P.S. I assume from this thread that as of end of it July 15th that you HAVE NO SOLUTION YET. Thanks to the BEST suggestion here, simply Disable the plugin in IE and it prints directly without the dang thing. Thanks, mrioux for the best suggestion here. Should work for Adobe - oh, wait, if you did, you wouldn't have time to have fixed this - you'd be attending too many "positive thinking" and "reaching your goals" seminars.