Print to PDF not working in Windows 10.

Question

A few days ago, I updated to v1809. I have since installed updates as well.

The issue is that any attempt to use the Microsoft Office 365 feature of "Microsoft Print to PDF" from Edge, or to save an image from the Snippet Tool causes the following error:

This is applies to only new attempts to create the file (when Print to PDF used), and the message is slightly different for attempts to save from Snipping tool (e.g. \Pictures\ and not \Documents.) Both have the identical message "File not found."

This is occurs regardless of in-use profile (Admin, my MS Account (Users group), my local Standard Profile (Users group), etc.) Does not appear to be related to profile settings or type.

I have followed a number of recommended approaches to fix the issue (reset Edge, set to default for printer, etc.) w/o success.

Search on the net proved fruitless.

My Office 365 subscription reports "Up to date" for all updates.

Any guidance or help is greatly appreciated!

Jim

Answer 1

Hi Jim,

Thank you for writing to Microsoft Community Forums.

I suggest you to try the following methods and check:

I suggest you to refer to suggestions from Kristine Arpreplied on January 13, 2018 and check: Microsoft Print to PDF is not working.

Additionally follow the below steps.

Method 1: Check the User folder.

Edge sometimes saves the PDF documents to the default directory automatically. If you don’t see the save dialog while using Microsoft Edge, make sure to check C:Users%username% folder for saved PDF files.

There are instances Edge stores saved PDF file in UserDocuments folder automatically, so make sure that you check it as well.

Method 2: Update the printer driver

---

If replacing the printer driver didn’t solve the problem, you might as well try to update the current one. In case you don’t know how to do that, just follow these instructions:

1. Go to Search, type devicemngr, and open Device Manager.
2. Expan Print queues.
3. Right-click Microhsoft Print to PDF, and go to Update driver.
4. Follow further on-screen instructions.
5. Restart your computer.

Please refer to Print to PDF tutorial.

Hope it helps.

Thanks,

Suman.B

Microsoft Community - Moderator

Answer 2

The answer might be as simple as it is stupid. Did you for instance activated the "controlled folder access" in Windows Defender?

To your defense I was at the brink of reinstalling Windows 10 when I saw that also "Foxit Reader PDF Printer" behaved erratic.

Answer 3

Please refer to Print to PDF tutorial.

Hope it helps.

Thanks,

Suman.B

Microsoft Community - Moderator

Suman.B:

Actually it helped a great deal!

What is a bit off, is that the solution (for me at least) was none of what was included in your response. Strangely enough though, it got me following a separate approach.

In this case, I have the Virus & Threat Protection/Ransomware Protection turned on.

What is unusual though, is that any attempt to "Print to PDF" failed to provide an alert that an "application" was attempting to alter protected folder(s). My "protected folder" is in fact, the Documents folder w/in any active profile.

Without a clear indication of the application that is hitting the brick wall, there was no way to define it as a safe execution.

So, the end-result: When I turned off the Ransomware Protection - it worked w/out an issue. To print from Edge to a .PDF to any designated folder from within the Print dialog.

So, yes. I really do appreciate your response and yes, that has identified the root cause - at least for performing the print operation to my Documents folder.

It still doesn't lay out the process to permit co-existance between Microsoft Print to PDF and Ransomware Protection. That is my next step.

Thank you again!

Your time and guidance is greatly appreciated, and you are a credit to this forum!

Jim

Jim

Answer 4

A few days ago, I updated to v1809. I have since installed updates as well.

Any guidance or help is greatly appreciated!

Jim

Revert to v1803 or whatever you had before v1809.

Unfortunately, that doesn't solve the issue.

It is unclear why such a suggestion would be given.

Jim

Answer 5

A few days ago, I updated to v1809. I have since installed updates as well.

Any guidance or help is greatly appreciated!

Jim

Revert to v1803 or whatever you had before v1809.