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 No 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 No comments

42 additional answers

Sort by: Most helpful
  1. Anonymous
    2019-11-24T03:01:49+00:00

    Hi,

    I"m so glad I'm not alone. We are having this issue too. Files vanish sometimes when user Saves. Additionally, Office's supposedly hidden temp folder/files are visible. User sees them appear then vanish. 

    Occasionally, users will save files and they will seem to vanish. They turn invisible but keep their names. When a user calls to tell me his file disappeared, I have him press shift-cmd-period to show hidden files. If he reports that it's there but "gray" then I know what to do.

    The current workaround is to open a new email in outlook, then drag the "hidden" file into it as an attachment. Then drag the file back out of outlook to save the attachment. The final file has [1] appended to it if saved in the same location as the original. I have the user then delete the original and rename the new, removing the "[1]". 

    Light years from ideal with an office full of people trying to get work done and meet deadlines, but it is what it is I suppose until it's fixed.

    Clients are MacOS 10.13 or 10.14, latest minor release on all. Server is MacOS 10.12 (RAID 1+0).

    Office version is 16.31.

    Thanks,

    Jeff

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-06-24T10:01:14+00:00

    I've encountered the same issue and seem to have found a (temporary) solution

    Office version 16.38

    Client Mac OS 10.15.5

    connecting through AFP/SMB (both encountered the issue) with a OSX server 10.15.5

    Issue:

    I create a new document in Word and try to save it to my network share but the file appears only for a split second to then disappear.

    Checking the network share I found that the file became invisible.

    Solution:

    • Uninstall Office from the client Mac

    • Download Office version 16.30 through Macadmins and install on client Mac

    I have been testing with version 16.30 and the issue seems to be resolved, the newly created documents now just appear as you'd expect.

    Hopefully this issue will be fixed in one of the following updates...

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. 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 No comments
  4. Anonymous
    2019-12-23T15:35:40+00:00

    I appear to have found a solution to the hidden file issue, however in addition to the files being hidden, I am also observing that saving the file immediately after being created fails.   Here are the steps to reproduce:

    Running OS X 10.14.6

    Word 16.32 (19120802)

    1. Create a new file in word
    2. Save file on network share
    3. File will save, and disappear.
    4. Make changes to the file, try and close word.
    5. Word prompts to save, hit save.
    6. Word appears to close, but then reopens.
    7. Turns out it is impossible to save the changes to this file - the only way to exit is to tell Word to discard the changes - subsequently opening the file confirms only the initial save worked
    8. Opening the file again, saving works normally.

    Clearing the hidden flag does not fix the save issue... I noticed the com.apple.quarantine flag is set on the file, sure enough examining the logs I see that sandboxd has denied write access to create temporary files.

    The behaviour occurs using both AFP and SMB protocols.

    The sandboxd error that occurs when I initially create a file:

    Violation:       deny(1) file-read-xattr /Volumes/Public/

    The sandboxd errors that occur when trying to save that same file immediately afterwards:

    Violation:       deny(1) file-write-create /Volumes/Public/Test.docx.sb-118eafb8-ncgFo2 

    Violation:       deny(1) file-write-create /Volumes/Public/.~WRD0001 

    When I first started testing, there was an additional sandboxd violation in the ~/Library/Group Containers/UB*.Office folder... running the following command in this folder appears to have fixed the hidden file issue:

    xattr -r -d com.apple.quarantine ~/Library/Group\ Containers/UB*.Office

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments