Word for Mac 16.25 cannot remember window size

Anonymous
2019-05-15T13:06:49+00:00

I just updated to word for Mac 16.25. Word no longer remembers the sizing of the document, and always opens to a very small window. Never happened before the update.

Original Title: Word for Mac 16.25

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
Answer accepted by question author
Anonymous
2019-05-16T09:46:48+00:00

Hi All,

We have received several reports about the same issue recently. For others to easily identify the information here, I’m summarizing the issue as follows:

Issue description:

After updating to version 16.25 (190512), Word for Mac can no loner remember the window size closed last time. It always opens at a fixed size.

Environment:

Word for Mac version 16.25 (190512) on all three latest version of Mac OS.

Assessment:

We can reproduce the same behavior on our side. And we are reporting the issue to our related team for further investigation. Once there is any update, we will post back as soon as possible. As a workaround, you can open the Word for Mac application first and open the file from the recent list or from the File menu.

Thanks,

Ran

Was this answer helpful?

40+ people found this answer helpful.
0 comments No comments

151 additional answers

Sort by: Most helpful
  1. Anonymous
    2019-05-21T12:38:17+00:00

    Thank you, pineman, that seems to have resolved the matter for me.  Much appreciated!!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-05-21T11:05:39+00:00

    How does one access that fix?  Thank you.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2019-05-20T20:03:43+00:00

    This should have been sorted DURING the beta period.

    16.25 fast ring = broken

    16.25 slow ring = broken

    16.25 release = broken

    What the #$&@&@* is the Insider program for, if MSFT refuses to use feedback, AND this slips through, AND...

    16.26 is still broken.

    This is absolute nonsense.

    Microsoft's QA team should be embarrassed - this is a failure.

    Agreed. But at least they finally acknowledge the problem. I don't know much about software development but if the problem didn't exist in 16.24 then it seems like it shouldn't be too complicated to solve. Compare A and B, see what changed, zero in on culprit and fix.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more