Watermark Error 400

none of these solutions have worked for me. The problem has only just happened last week, after some windows updates. Now it is slowly creeping through the firm as these updates happen. This is vital to us as we use it for electronic letterheads. our only work around at the moment is to save as PDF and then print then print the PDF!!!

when will there be a solution to this bug?

1. No one here can tell you when something will be fixed, or even that it will be fixed. This is a user-to-user support forum. -- You can give feedback TO MICROSOFT designers and decision makers on Microsoft Word or other Microsoft Products (using their feedback mechanisms, not here)
2. Did you try disabling connected experiences or working off-line?
3. Did you try inserting a faded/semi-transparent image in your header in lieu of inserting a watermark?

none of these solutions have worked for me. The problem has only just happened last week, after some windows updates. Now it is slowly creeping through the firm as these updates happen. This is vital to us as we use it for electronic letterheads. our only work around at the moment is to save as PDF and then print then print the PDF!!!

when will there be a solution to this bug?

Hi john

Your suggestion is workable. I can have my watermark in my work.

Thank you

Claude

Adding the picture to the header just pushes all of the text on the page down. I don't want an image in the header, I need a watermark background for the page.

This will happen if you put the picture in line with the text in the header, so that the picture behaves like a (large) character and increases the header downwards. That is not desirable.

The trick is to anchor the object to the header and position it, wrapped, in the document body or actually behind the text in the body of the document. You would also want to change the Transparency setting to mimic a "washed out" watermark. (This is actually how the Watermark facility in Word works.)

As noted elsewhere in the thread, changing the connected experiences will present another workaround for the underlying issue.

Thank you! This worked.