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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I originally posted this in Office365 as that was the forum I was sent to from my Administrator panel. However, they have said to post here instead. So here goes.
Since a few days ago (around the time I installed Lync Basic instead of Lync 2010), the Microsoft Office Upload Center constantly needs repair. I have deleted the caches in User/App Data/Local/Microsoft/Office/14.0/OfficeFileCache and also /15/OfficeFileCache
It is the one in /15.0 that is the issue (now up to OfficeFileCache - 10.old).
When I try the repair option, it says something is accessing the cache and please close all Office apps. Even if there is no Office app running. I stopped Lync automaticallly starting, rebooted and still the same. I have to close in the systray SkyDrivePro and SkyDrive and then the Repair can continue. Then the error is cleared.
I can leave it for 10 minutes and the Upload Centre icon sits in the systray quite happliy. Until I open Windows Explorer and click on the SkyDrivePro icon, I can see my SkyDrivePro files in Explorer as normal with the green ticks, the SkyDrivePro icon in systray says it's up to date (nothing being processed) and then the Office Upload Center error comes back.
"The Microsoft Office Document Cache encountered a problem and needs to be repaired."
I have Office 2010 on the desktop and Office365 as my company's main work environment.
I'm baffled. How can I stop this happening? Thanks.
also
I have Office 2010 on my desktop and Office365 as the work environment as stated above. The only Office 2013 components are SkyDrivePro (which used to work fine without these cache issues) and Lync (just installed via Office365 as instructed by the Office365 site to upgrade the Lync2010 I used to have which worked fine).
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
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.
You guys might want to look at this reply in another forum:
I am on a home peer to peer network with office 2013 so it may not be a solution if you are on a corporate domain but the solution suggested solved all my problems, including the corrupted cache that you are discussing.
The folder you're looking for is hidden. In file explorer you need to go to view and check Hidden items, then you'll find it.
Running Windows 10 and Office 365 for Business and I have this problem but cannot find the actual cache file anywhere. I have done everything else Microsoft recommends, including uninstalling and reinstalling everything. This solution makes total sense, but I cannot find the \AppData files (or obviously anything following in the path recommended here: C:\Users\user\AppData\Local\Microsoft\Office\16.0\OfficeFileCache ) in my user profile, or in any other user profile on my machine. Does anyone have any suggestions?
On a surface pro running windows 10 and office 2016 (64 bit) I found that by actually going into the C:\Users\user\AppData\Local\Microsoft\Office\16.0\OfficeFileCache folder and deleting all the files fixed the problem. Also a good idea to delete any other \OfficeFileCache*(number)* folders that have been created as they are a waste of space. Make sure you've saved all documents that you keep on onedrive before performing this.
Deleting all this data will give the OfficeCache the opportunity to rebuild itself. Restart the computer, open office uploader or any other office app and the annoying message will have gone away if everything else is right. Good luck!