Word 16.31 turning server files invisible

Anonymous
2019-11-20T17:12:10+00:00

Microsoft Word 16.31 for macOS seems to be turning server files invisible.

This has been observed in mulitple locations with multiple Macs (macOS 10.13.16 and 10.14.6) saving to macOS Server 10.12.

The file's UNIX chflags bit is turned to "hidden" and to make it visible we have to find the file using "ls -la" and then "sudo chflags nohidden file/path.docx?" to fix the file and make it visible again.

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
Answer accepted by question author
Anonymous
2019-11-24T15:20:28+00:00

With help from Adam Berti or Berti Group we have found that this script can fix a folder or share's invisible word documents:

find basedir/ -name '*.docx' -exec chflags nohidden {} ;

Where "basedir/" is the full path to a server share (including the trailing slash)

Adding -print will list what is happening.

find basedir/ -name '*.docx' -exec chflags nohidden {} ; -print

But it would be far more helpful if Microsoft would just fix Word 16.31 !

Was this answer helpful?

8 people found this answer helpful.
0 comments

42 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-01-21T21:44:38+00:00

    Out of curiosity -- was this limited to a problem with Server 10.12?  Or any version of macOS Server?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-01-23T15:37:32+00:00

    Yes this server is on 10.12.

    Alec

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-01-23T16:35:46+00:00

    Out of curiosity -- was this limited to a problem with Server 10.12?  Or any version of macOS Server?

    We're seeing it on 10.11 server.

    That being said, the user who was experiencing the problem notes that with the January release of Word for Mac, she no longer experiences the problem.

    Please be advised that she may also have changed her protocol from SMB to AFP as a troubleshooting step.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-01-29T22:48:00+00:00

    We're still seeing the issue (last incident was yesterday - Jan 28th 2020) even after updating to 16.33 (on Jan 14th 2020). OS X Server 10.11 with SMB and AFP enabled. Client is on macOS 10.14.6.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments