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
    2016-05-03T15:14:14+00:00

    Setting the line spacing to an exact value works too, but it's not very handy, of course. There are dozens of reports of this problem already, but still no solution. It annoys me that this was no problem in previous versions of Word - I wish I hadn't upgraded (I'm using other functions of Office 2016 that I can't miss - so to speak - so going back to an older version is not an option for me).

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-05-03T08:38:51+00:00

    FRUSTRATION!!

    Same as you, Björnslebaert, I have installed every new version of Office 2016 (RTM and Insider Preview) since making this post in November 2016 and no luck.

    My current Windows 10 x64 SL is 10586.218.

    Office 2016 x64 is 16.0.6769.2040

    FURTHERMORE:

    • This layout mess occurs even when using Arial.

    • I also experience that when you use the bare-naked default settings, printing is to pdf is ok, but as soon as you adjust any margins, line spacing, font size, space before paragraph etc., then the layout gets messed up.

    TEMPORARY SOLUTION:

    For  the moment the only real temporary solution (as someone mentioned earlier) remains:

    1. Open a new document.
    2. Immediately "save as" a ".doc" instead of ".docx"
    3. Go to "Word Options > Advanced" and then tick the box "Use printer metrics to lay out document"

    This is silly and you probably are restricted with using the .doc format instead of .docx

    Nearly 50 replies and 4 months later, we are still lost at sea.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-03-30T17:44:10+00:00

    That doesn't work for me, alas. I've read numerous posts about problems with third-party fonts under Windows 10 and Office 365, and am starting to wonder if the problem isn't rather Windows 10-related?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-03-29T05:42:12+00:00

    So, we're four months later now, and I've downloaded numerous updates for the Office 365 package, but ... still no solution???

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-02-01T17:46:20+00:00

    Is there some way we can know that Microsoft is aware of this problem?

    I've downloaded lots of updates for Office 365 in the past few months, but still no solution ...

    Was this answer helpful?

    0 comments No comments