Self-changing of MS Word file names to temporary ~WRD ones on my Mac mini running macOS Sequoia.

I have a Mac mini with OS Sequoia 15.1 with MS Word 16.91 in which I am randomly, arbitrarily, and incompetently experiencing self-changing of file names to temporary ~WRD ones. You can view some screen shots here showing the names and folders to which they are saved until closed at which time they disappear thanks to MS thus permanently sabotaging the file for the unwary. It's possible that I caused this in changing some setting in combatting another nuisance, i.e., files opening with large swaths of unneeded space. Here is an unresolved "locked" (thanks M$) thread from which I got my title: https://answers.microsoft.com/en-us/msoffice/forum/all/word-mac-office-2021-creates-random-wrd-temp-files/b1c1224c-2930-48c8-8065-5ae0526533dd



[Re-Titled By Moderator]

Mac mini, macOS 15.1

Posted on Nov 18, 2024 6:13 PM

Reply
Question marked as Top-ranking reply

Posted on Dec 6, 2024 9:48 AM

I have not had the time to follow through all responses. But I created a temporary solution. If your symptoms match mine (see this post below and my last post), read this or go directly to the bottom to see the solution.


First, I have a screen cast in case the issue is still not clear:


Screen cast: https://www.loom.com/share/53f0e27f3fda4daa9446a370c16c80cb?sid=331d0033-478f-46b7-b35a-37f950c82589


More background on my case:

  • Didn't make any changes to Word settings since the last install years ago.
  • Only relevant changes recently were macOS updates and MS App updates
  • For Sequoia (I have 15.1.1), there are many improved security permissions and other apps have been requesting Access Permissions in recent weeks. However, Word has not asked/promoted for additional permissions in my case.


My attempts for a solution:

  • This time, I tested first whether the issue occurs on the local drive or other drives (external, network or cloud drives).
  • I found that, for my case, it is isolated to external and network drives only. It works fine on local drives.
  • This points to the fact that Word needs access permissions for the external drive/network drives - even though Word has not asked for it explicitly.
  • Now, checking permissions
    • Test 1 (Failed): Using "Get Info" on Finder and Terminal "ls -al /Volumes/MyDrive" command)
      • Terminal shows the "./Volumes/MyDrive/.TemporaryItems/folders.501" folder (where temporary Word files are stored having "_unknown:_unknown" owners and low level access permissions. I am not sure if this is normal. No action taken as I do not want to change this without knowing first. I will investigate further.
      • "Get Info" - shows nothing out of the ordinary. I reset to the same (Read-Write for the user and staff).
      • Open Word, try to save: issue is not resolved.
      • Close Word App
    • Test 2 (Failed): Check macOS Settings for "Privacy and Security > File & Folders".
      • Word is listed (for me) here.
      • "External Drives" access turned ON - no other drives/folders are listed.
      • I turn OFF and then turn it back ON.
      • Open Word, try to save: issue is not resolved.
      • Close Word App
    • Test 3 (Succeeded): Check macOS Settings for "Privacy and Security > Full Disk Access".
      • Word is NOT listed (for me) under this setting (I prefer this since the fewer apps have Full Disk Access the better for security).
      • I add Word and give it Full Disk Access anyway.
      • Open Word, try to save: issue is resolved.


To summarize - Word needs proper access permissions for non-local drives and it is not prompting the user for granting those permissions. Once Full Access is manually granted, it works. It is obvious that Word should request necessary permissions so the user does not have to do this, which open the possibility for misconfiguration. It is a Microsoft and Word problem - not Mac.


This resolution is not permanent since I do not want to give Word "Full Disk Access" if it is not necessary. Word should request the right permissions - not one chosen by the end users.


The Temporary Solution -

WARNING: this solution gives the Word app a high level of file access that I am not certain is necessary and makes me uneasy and hence, this solution in my mind, is a temporary one. So, I recommend that you continue your research and reaching out to MS Support and get a permanent solution.


Does your symptom match mine?

  • Word documents on external and network drives do not save as expected.
  • When saved, the title/name of the document shown in the title bar of the open Word window (not in Finder) - changes from its original name to a temporary file name (like .~WRDXXXX) - see screen cast above.
  • Any additional changes made during the time when the temporary file name is shown in the title-bar are not saved to the original document - so all changes after this may be lost.
  • At this point, if I try to close the Word App, it shows a prompt saying the file (.~WRDXXXX) was not saved and asks to save it again and opens the folder window.
  • If I cancel, all changes made are lost. If I save to a new file or write over the original file, changes are saved to the selected file.
  • Repeats if I make more changes.


Steps to Solution:

If your symptoms are similar/same, especially the first few bullets above, try the temporary solution below.


  • Quit the Word App
  • Open macOS System Preferences
  • Click "Security & Privacy"
  • Click "Full Disk Access" from the list of preference items on the right side.
  • Click the plus (+) icon at the bottom of the System Preference window
  • Navigate to "Applications > Microsoft Word" select it and click "Open" to add it to this list
  • Make sure the checkbox is turned ON
  • Now open Word again and try saving your changes.
  • In my case, the issue is not repeated and document content is saved.


Hope this is helpful for some.


Thanks.

27 replies

Dec 5, 2024 2:18 PM in response to RobertBurnsOB

Look at the latest comment from Apple Censorship Central: "We’ve edited your post Self-changing of MS Word file names to temporary ~WRD ones on my Mac mini running macOS Sequoia. because it contained personal information." Are there competent people there? I know more than any of them about confidentiality, as I am an experienced lawyer, and cannot imagine anyone other than an AI-diseased robot coming to that conclusion.

Dec 5, 2024 4:23 PM in response to Barney-15E

No as to "Microsoft has always used that temp file naming convention". I'm sure that it doesn't do that for you. I doesn't do that for me now. It didn't do that for me before in years of heavy usage except when this problem occurred. No reasonable consumer would consent to file name changes on the desktop; somewhere behind the scenes is not in issue. I don't have the expertise to determine what caused the problem, but I posted in this thread what DC Computers said in my invoice.

Dec 5, 2024 5:28 PM in response to RobertBurnsOB

RobertBurnsOB wrote:

No as to "Microsoft has always used that temp file naming convention". I'm sure that it doesn't do that for you. I doesn't do that for me now. It didn't do that for me before in years of heavy usage except when this problem occurred. No reasonable consumer would consent to file name changes on the desktop; somewhere behind the scenes is not in issue. I don't have the expertise to determine what caused the problem, but I posted in this thread what DC Computers said in my invoice.

It doesn't have to do anything for me or you. Microsoft's software is writing those files. Whatever you did to corrupt Word and the rest of Office I don't know. It appears to be related to you trying to change the location of the temp files. That's what happens when you start messing around with things that should not be changed. If reinstalling Office fixed the problem, don't try to change the location of the temp files again.

Dec 5, 2024 6:12 PM in response to Barney-15E

I have no recollection or belief that I did anything to change where temp files were saved other than to save as back to the original file once I realized that the corruption/problem caused by Apple/M$/chance (not by me according to the shop) of hijacking my desktop file names and sabotaging my files. The only thing I did before that was to stop word files opening up super large; I suspect that that sudden problem was also a symptom of the corruption/problem. To the software engineers: Don't create problems and then blame users trying to resolve them.

Dec 6, 2024 1:57 PM in response to steve626

I am unaware of having used any such language. I have not cared where temp files are stored. What I have cared about is the nonconsensual name change of desktop files and the consensual frustration of saving changes. The causing of corruption, if such occurred, is beyond my competence but not surprising to me. This helps me to get a sense on how it occurred. Again, DC Computers knows far more than anyone here what if found and how it fixed it.

Dec 6, 2024 2:00 PM in response to mm_astoria

My problem was fixed by a professional at DC Computers. After some exploration by a tech with me present after viewing my video I was told something along the lines that some type of occurrence probably caused some type of corruption requiring somekind of install. When I picked up the machine the blame was vaguely placed on the OS. The "description" in the invoice is above and doesn't tell me much as a lay person.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Self-changing of MS Word file names to temporary ~WRD ones on my Mac mini running macOS Sequoia.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.