Print Dialogue Not Opening

[Jam5CB8]

If I open a pdf document directly in Adobe Reader, I can print from there.  However, there are a few programs on my machine that (presumably) embed adobe reader in their software as the default reader.  When I click the print logo (or CTRL+P) nothing happens.  I am then forced to save the document and open with Adobe Reader.

P.S. I don't know what to call the embedded adobe viewer software.

 

[try67]

You need to contact the developers of those applications. Maybe they did it on purpose, maybe it's a bug...

[Jam5CB8]

The programs allow print on some other machines.  It is working with some and then isn't working with others.  All the machines are Win10 machines.

[AttilaG]

Hi,

I have the same problem but I think i narrowed the problem down to Windows version 2004?

Can you check and confirm if desktops running on latest windows 2004 have this issue and if computers with older verions still show the print dialogue?

I can confirm that printdialogue still works with W10 v1903, v1909, v1803

and on 5 computers with W10 v2004 the printdialogue doesn't work.

Please help confirm this so the problem can be, with any luck, manualy solved.

kind regards.

[Mindert0101]

I have the same problem

Windows version 2004 doesn't show the print dialog in embedded software, while the same software works on version 1909

[Mindert0101]

I am a developer for the software with adobe embedded.

As far as I have noticed, only the W10 v2004 has this problem

[AttilaG]

So we definitely know that it's Windows 10 version 2004.

Do we have to wait for another update from Windows or Adobe reader or could there be a manual fix for this?

Does anyone have an idea?

Kind regards.

[AttilaG]

Hello,

Sadly the new update Windows 20H2 did not fix this issue.

[Mindert0101]

That's too bad.

I have made a workaround.

I put a button above the form, where the PDF is displayed.

With the shellexecute  command I call a executable "PDFtoPrinter.exe" and print the PDF.

This executable is free.

[Egrechin]

Hi All,

Do we have any solution/workaround for this issue?

I don't see any statement from Adobe that there is a bug in a specific Windows 10 build

Thank you

Evgeny

[Mindert0101]

I neither have seen a statement from Adobe.

I don't know why.

May be Adobe doesn't read this Community 

[Robbie5E36]

We too have experienced this problem with our system.

Would have love to known this prior to setting up that new machine on this.

For now they have to save and open to print, which is just time consuming.

I do not have rights/access to change the embedding as it is a Gov't controlled system.

Is there any potential for an AHK or other action to allow for that dialog to appear?

or is it "this is the new norm" until it starts miraculosly working again?

[Mindert0101]

As I mentioned before.

I made a change in my program.

I put a button (print) above my panel where my pdf is shown.

Push the button a shellexecute  command is executed.

This executable is named "PDFtoPrinter.exe" and prints the PDF.

You can download this app 'PDFtoPrinter.exe' for free. (http://www.columbia.edu)

[Egrechin]

@Mindert0101 ,

Thank you for sharing this workaround.

It might work, however i'd like to hear from Adobe and Microsoft about the root cause and their plans to resolve this.
We have opened a parallel ticket in Microsoft support, as most likely they respond much faster the Adobe support.

[Mindert0101]

For me it works.

But it would be nice when Adobe and/or Microsoft will solve their killing changes.

I wonder how many peoply suffer from it.

Anyway It's nice to hear you opened a parallel ticket in the Microsoft support.

Let's hope it will soon be fixed!

[Jens154A]

From what I know this is a bug in Abobe Reader DC that only happens on Win10 Version 2004 and later.

This bug was introduced when Win10 Version 2004 came out around May 2020.

Adobe knows about it - it is listed as a known bug (Bekannte Probleme | Adobe Acrobat DC, Reader DC).

I monitor this forum from time to time to see if there is some official statement from Adobe about this bug.

But in all these months nothing happened.

Since this bug exists now for about 7 months I do not believe Adobe will fix it soon.

Jens

[C Wortz]

I once was a Gates fan, but now I am beginning to wonder if he is trying to make the world mediocre?  The processes at MS for development have gone astray as he has decided to attempt to solve the worlds health issues...  The MS update broke the adobe code, this is going to affect many offices that rely on reader.  It makes their jobs more frustrating having to save the pdf and print it.  I guess, we can follow in the Gates way and uninstall acrobat reader and rely on the MS products..... Thats scary.

[WesleyCreed]

Hey Guys, I have a resolution for this.

1. Launch Adobe Reader DC application from the start menu.

2. Select Edit from the menu

3. Select Preferences.

4. Select Security (Enhanced).

5. Uncheck the boxes for "Enable Protected Mode at Startup" and "Enable Enhanced Security".  If you get a prompt, just click Yes.

6. Click OK to save the changes.

7. Restart Adobe and the application that uses Adobe.

[AttilaG]

Hi Wesley,

Thanks for sharing your resolution.Uunfortunatly this did not work for me.

Are you sure this was the case for you?

thx

[Test Screen Name]

I see a lot of posts, but nobody says they have ever reported this to Adobe. Has anyone reported it? (Though it may be a normal Protected Mode limitation).

[AttilaG]

Hi everyone,

I'm here to tell you all that the print dialogue is back now.

Adobe 21.001.20135

W10 20H2

kind regards

[Robbie5E36]

Had my user verify version and confirmed with 21.001.20135 the embedding works as expected and can print from the popup dialogue.

[Robbie5E36]

Meant to include they are on 1803 currently; so it doesn't seem to be a WIN version issue, and is based on Reader version.

[Egrechin]

This is indeed a great news.

I've been struggling and running between Microsoft and Adobe, and didn't get anywhere any answer.

Good to see this fixed.

Thank you!

[AttilaG]

Some of my users also reported that my Adobe Plug-in could not be loaded or did not exist.

Reinstallation of Adobe reader DC solves the Plug-In problem.