BUG!! Word 2016 fails to print margins correctly / messes up layout (Possible OpenType .otf Font bug)

Anonymous
2015-11-26T19:37:16+00:00

Hallo everyone,

I am having severe problems with Word 2016, as it does not print the document layout correctly as it somehow messes up the margin when printing.

NOTE: This happens when printing to Adobe Acrobat DC and my physical printer!

My document layout:

• no markup,

• custom margins (set to 1,27cm top / bottom and left / right - my printer can easily handle these...)

• no header or footer

• paper size set to A4 in all settings

IMAGE 1

The following is picture shows page 1 of my document in "Print Layout"-view. This is how I want the document to look when printed.

IMAGE 2

Here is a picture of the Print-preview menu. You can see that the Print preview still shows the document exactly as I want it. No problems. No funny settings selected. No "Print Markup" selected.

IMAGE 3

Now this is what happens when I print the actual document:

The bottom margin changes and suddenly the whole layout is messed up!

Please advise whether this a bug, or some setting I seem to wrongfully configure.

This is really annoying as I sometimes spend hours to get the layout and spacing in a document right, but then when it comes to printing the document, everything is messed up.

Thank you.

Microsoft 365 and Office | Word | For home | Windows

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.

0 comments No comments

138 answers

Sort by: Most helpful
  1. Anonymous
    2015-12-30T13:35:05+00:00

    Thanks for your input, but unfortunately, this doesn't work for me :(

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-12-25T13:30:39+00:00

    Ah, now I understand: the problem we're having here is not that printing doesn't work, but when we print (either to pdf or to a physical printer), the margins of our document are changed when using third-party fonts :)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-12-25T13:08:23+00:00

    BJ, First you have to test and see if you can "print-to-PDF" if you run word as an Administrator. So choose your printer as "Microsoft-print-to-PDF". If you can print to a PDF file, (i.e. basically save to a pdf file) but you still can't print to a real printer, then the problem is your printer or its driver. You may need to update the driver or get a new printer. When I first started out on this, I can't even print to PDF, it said "Printer not ready" no matter which printer I chose, so I knew right away the problem wasn't my printer. So try to print to a file instead of a real printer and see if it works. Make sure you "run as administrator". You should get a UAC prompt (for which you have to answer Yes) when you open Word as admin. If you don't get the UAC prompt, you are not doing the "run as admin" correctly. If you get the UAC prompt when opening word as admin AND you still can't print to a PDF file by choosing your printer as "Microsoft-print-to-PDF', then I am at the end of the line. Good luck.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-12-25T07:35:56+00:00

    Thanks for your input! Unfortunately, running Word as an admin didn't solve the problem for me. I'm curious to hear if it did for someone else, though!

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-12-24T18:06:35+00:00

    Same problem. Spent hours with Microsoft tech support who charged me $99 and they couldn't figure it out. Well, guess what, they are just not as competent as I would like them to be as I finally figured it out myself. The problem is that for some reason, you have to run Office app (or any app you have printing issue) as an Administrator in Windows 10. And here is how you make it happen:

    How to fix printing issue in a Window 10 application:

    (1)  Go to the application tab from “Start”

    (2) Right click on it

    (3) Go to “More”

    (4) Select “Open file location”, this will take you to file explorer directory where your app is

    (5) Right click on the highlighted application name, select “Properties”

    (6) Click “Advance” button

    (7) Select “Run as administrator”

    (8) Save all changes   

    (9) Recreate all shortcut, re-pin to task bar etc

    Don't forget to do (9)! Now your app will print. But there is a pesky but harmless side effect in that you will get a UAC prompt everytime you open the app. Just click "Yes" on the prompt. If you don't mind that then you're done. If you want to get rid of the UAC prompt (for a single app), you have to use the Task Scheduler. Here are the steps I found on the web.

    (1) In Task Scheduler, right-click "Task Scheduler Library" and select "New Folder" Name it whatever you would like.

    (2) Select the new folder and click "Create Task" (not "Create Basic Task")

    (3) Name the task something descriptive. Enable "Run with highest privileges," and select your OS under "Configure for."

    (4) Under the Actions tab, select "Start a program" in the Action dropdown if it isn't already. Click Browse and find your app's .exe file (usually under Program Files on your C: drive).

    (5) (Laptops) Under Conditions tab, deselect "Start the task only if the computer is on AC power."

    (6) On your desktop, right click and select New > Shortcut.

    (7) Paste 'C:\Windows\System32\schtasks.exe /RUN /TN "Name of folder\Name of task" into the text box.

    What a pain in theAss!!! This is a just stupid stupid bug that wasted hours and hours of my time. Microsoft should be ashamed of themselves to have bugs like this in the year 2015. Don't they even do QA on their products? Or did they only do it in Adminstrative mode? I'm not even a tech guy, I work for a hedge fund. The fact that as a tech layman, I have to figure all these out all by myself wth no help from those Microsoft tech support (after they have the nerves to charge me $99) says plenty about the company.  So glad we don't have MSFT in our equity portfolio!      

    (

    Was this answer helpful?

    0 comments No comments