NEW MAIL APP available in MS Store, 12Jan20
If not auto-updated in Settings - Apps, - Open MS Store & do search Mail
Test print now seem rectified
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Today, I printed an email from Windows 10 Mail. The Mail app version is Version 16005.13426.20316.0. I printed by clicking the "..." at top right, then selecting Print. I was printing to letter sized paper. Print preview looks normal. However, when I print, the print is compressed into 1/4 of the page, and is so tiny as to be illegible. The entire page prints in the top left quarter of the paper.
Printing a test page is normal.
Print from Word is normal.
I have tried more than one emails from Mail, and they print the tiny version to the top left quarter of the sheet. It happens whether I print on one side or double-sided.
Here is the print preview (normal).
Here is a scan of the paper sheet. The actual printout is only in the top left corner.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
NEW MAIL APP available in MS Store, 12Jan20
If not auto-updated in Settings - Apps, - Open MS Store & do search Mail
Test print now seem rectified
I had that search bar problem too, & it didn't work in File Explorer, either. I would click them & nothing would happen. It was a repair-install that made it work again for me, I think. What is a "server side" fix?
Thanks PCR. Some features are fixed server side and I think this is one of them.
I remember once Search on the taskbar was broken, which was fixed server side as well.
I don't know, Sumit. We all started out with Version 16005.13426.20316.0 & still have it. Yet, when this thread started, it had the issue & now it does not. Mail doesn't seem to have redownloaded with a fix in it, even keeping the same version. It's a mystery what they did to make it work. A big mystery.
Version 16005.13426.20316.0 appears to have fixed the issue.