There is a serious disk error on file ~Word Work File S{A1F41F30-FB84-B649-9F8A-F0A7D2698BBF}.tmp

Anonymous
2016-05-30T19:08:24+00:00

everytime i save a word file on my mac i get this message. 

i'm using ms office v15.22.1. 

Please advise. Thanks

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
2016-10-04T03:10:48+00:00

I had this issue for many months and it was very frustrating--It was so frequent that I switched to Pages for a while. Since I have updated Word (running V 15.28 (160927)) for 2-3 weeks, I have not had 1 serious error. I am keeping my fingers crossed. 

I'm on a late 2013 MBA 11, running El Cap 10.11.6

I thought it might be helpful to read a post from someone who has had some good luck...

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2016-09-14T17:39:21+00:00

Hi everyone,

On 9/13/16, we released update 15.26 (160910), the September feature update for Office 2016 for Mac. Please install the update by clicking Help > Check for Updates > Check for Updates. Our engineering team has been intensively working on the ‘serious disk error’ issue and feel that this latest update will resolve it.

If you continue to experience problems, please reply to this thread with the following so that we can further isolate the cause:

  1. A screenshot of the About dialog (that shows the Office build number).
  2. A screenshot of the serious disk error dialog.
  3. The output of running ls ~/Library/Containers/com.microsoft.Word/Data/Library/Application\ Support/Microsoft/Temp from Terminal.
  4. The output of the command defaults read  com.microsoft.Word from Terminal if the issue happens in Word; or defaults read com.microsoft.Outlook if the issue happens in Outlook.

If you continue to experience the same ‘serious disk error’ issue that you did before installing the update, let us know and we will reach out to you in a private message to see if you’re willing to have an engineer speak to you directly to get it resolved.

If you experience any other file-related issues (other than the ‘serious disk error’), let us know that, too.

Again, we apologize for the frustration around this issue, and hope that this solves it.

Best,

-Erik, Office Newsroom

Was this answer helpful?

0 comments No comments

251 additional answers

Sort by: Oldest
  1. Anonymous
    2016-07-21T00:45:07+00:00
    1. Office 2016 15.24 OSX El Capitan 10.11.5. Just did the Office install a few weeks ago - but think it was 15.23
    2. Nope. New laptop - barely has any software on it.
    3. Definitely 'S' but will keep an eye open for others. 'S' just happened now when I tried to ctrl-z a recent change- it also seems to happen when I try to make formatting changes. I can generally type new text, but it can happen when I try to delete text or spacing.
    4. When Office has been running for maybe 30 minutes. I can save the doc under another filename and get maybe 10 more minutes without the errors...then it starts again. Have not opened a bunch of files at the same time, so can't comment on that.
    5. No, but per other troubleshooting tips, I did rename that file to .old twice - though office has automatically created a new copy of that file within a day of my renaming it. Renaming it did seem to help until I opened a new file or restarted word or the computer.
    6. Nope
    7. Admin. I've also repaired permissions per other troubleshooting tips - that didn't help at all.
    8. Rebooting and closing windows both help temporarily...but the issues always come back after Word has been open for a period of time. I don't use Outlook, so I can't comment on that.

    ** Note - I am NOT using Active Directly like prior poster. This computer is not networked at all.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-07-21T11:15:30+00:00

    This computer is not networked at all.

    Then how did you post your message?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-07-21T11:52:16+00:00

    Okay, I just got the error again. As you can see below, it's an "S" scratch file.

    Important Notes:

    Even though the message refers to "Word Work File," I was using Outlook at the time, as seen by the icon in the error message:

    There is a serious disk error on file ~Word Work File S{6D0685DE-875A-FF44-BA00-6FF9CF3A1A60}.tmp.

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=b79ebaad-b256-467c-847e-6e0d29f9d296)

    When I clicked OK on that dialog, I got this dialog:

    Word has insufficient memory. You will not be able to undo

    this action once it is completed.  Do you want to continue?![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=3175a0d3-f6d4-4c00-ab81-196406c49748)

    Word wasn't even running when I saw this error! Again, I was using Outlook.

    Outlook had been left running overnight.  The actions I took immediately before the error were as follows:

    1. I pressed ⌘-N to open a new email message.
    2. Skipping the headers, I typed two words in the body of the message.
    3. I selected that text using ⌘-A, and then formatted it as strikethrough text.
    4. I tried to insert a new word in-between the two existing words, and that's when the first error popped up.
    5. When I clicked OK, the 2nd error popped up.  I clicked Yes.
    6. I pressed ⌘-Z to undo my last action, and Outlook crashed.

    Note: I'm perfectly comfortable using the Terminal, event viewer, etc., so if there's additional info I can provide, please let me know.

    I saved the Microsoft Error Reporting log, but I couldn't include it in this message because your editor said it was too long. I'd be glad to email it to you, if you want.

    Tip for improving this forum software: You should allow users to upload files.  Even if you limited such uploads to ASCII text files, that would be sufficient for attaching logs.

    Was this answer helpful?

    0 comments No comments