Copy link to clipboard
Copied
I have a user who is trying to batch print pdf files from the Windows Explorer context menu. They select all the files in a folder right click and print.
The files then open if Acrobat Reader and are sent to print.
However they are finding not all files print. For example if there's 8 files in a folder you might get 5 that print and 3 that don't.
There's no errors coming up and no pattern to what prints and what doesn't. You can go back into a file that hasn't printed and it will print fine on the second attempt.
Anyone come across this before?
Copy link to clipboard
Copied
Having the same issue with multiple users trying to batch print .pdf files. All details are exactly the same as Dave is reporting.
All users are on Win10 or Win11. I had 1 user report the issue to me yesterday, Today I have ~15 users with this issue.
I have done the following so far:
I checked that all users were up to date in Windows update.
Uninstalled Adobe Acrobat Reader DC.
Ran adobe cleaner.
Installed the latest version of Adobe Acrobat Reader DC from a fresh download.
I have tried with protected mode at startup on/off.
Copy link to clipboard
Copied
Hi
i've managed to resolve this doing this: in adobe reader go to menu and do the "disable new adobe reade", mine isn't in english but must be something like that, restart adobe and windows explorer context print works again.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Hi Dave389159511jus,
Thank you for reaching out.
As mentioned, the issue occurs when printing multiple PDFs from the Windows Explorer context menu. This is weird behavior. Would you mind sharing the following information?
- Make and model of the printer in use
- Acrobat Reader and OS version on the machine
- Did the issue start recently? If yes, have you made any recent changes?
Meanwhile, please try the troubleshooting steps suggested here: https://adobe.ly/4cd57ov. Check if that makes any changes.
Let us know if you need any help.
Thanks,
Meenakshi
Copy link to clipboard
Copied
Thanks Nelson, that has solved it.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now