This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 81%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERE%3C/text%3E%3C/svg%3E)
Going to reference a Technet I found while trying to research this issue https://social.technet.microsoft.com/Forums/en-US/062d6be1-4d6c-49c3-9822-abaff2833478/windows-10-sync-center-conflict-office-files-creates-a-filenamexxxxxxxtmp?forum=winserverfiles#8f1cf272-0f55-4991-9db7-3ff548d87126 I have Multiple updated Windows 10 Enterprise computers running offline files sitting on the network generating these files. 1000s of them. The server is not stressed. Disk queue sits around 1 -1.5 This issue only started on November 18 basing it on file tracing to see the TMP files. Most times the file is there along with a TMP file. Anyone ever find a solution to this?
If we go to the end user and Resolve. Windows 10 sees the TMP file as a conflict for the real file. The resolving the conflict leaves BOTH files on the server and both on the end user computer. But the TMP file does NOT have the most up to date info. (using a text file)
The user directory is a DFS share.
This is going to create a storage space issue.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Try check the event viewer and see if there is any clue there?
You may open Feedback Hub app and report this issue and make sure add steps to reproduce this problem and share your configurations and necessary log files for the Windows team to investigate this issue.