Msosync.exe uses 60% of CPU in background all the time

You may follow the suggestion by 'Jennifer Zhan' from the thread link below to disable the 'MSOSYNC.EXE' and check if it helps:

http://social.technet.microsoft.com/Forums/en-GB/officeitpro/thread/f018dada-b35e-43e3-bb08-5204e2f3d113

Aravinda,

Thank you for the reply.  Before posting I did search the forum and read the thread you provided.  However, it does not begin to answer my question, unfortunately -- nor did Jennifer address the original question by the other poster.

Jennifer's suggestion does not disable msosync.exe.  It merely hides the icon in the notification tray!

So, the question both the other poster and I have remains unanswered.  Why is this process consuming so much CPU time, coninuously, when we do not have any files to be synced?  It is a waste of resources, electricity, and a sign of very poor software design, as far as I can determine.

Hopefully you or another Microsoft expert can provide some insight into this problem, and perhaps a solution as well.

Thank you.

Robert

Follow the steps below and remove 'msosync.exe' from the Windows startup:

Click Start > All Programs > Accessories > Run > Type 'msconfig'.

In the configuration window  > Go to startup tab > Uncheck the box for 'msosync.exe' and verify the result.

That is what I have done recently -- disable msosync.exe in the startup process.  This does get rid of the symptoms of high resource usage.

It would of course be preferable to have a solution for the cause of the problem.

Msosync is run via a task in Task Manager. To disable it:

Start >> Administrative Tools >> Task Manager >> Highlight "Task Scheduler Library".

You will see a task called "Microsoft Office 15 Sync Maintenance for..."

Right click on it and choose "Disable".

Even if you disable the task, the process for MSOSync will still be running. So, to stop it you either have to reboot, or kill the process using Task Manager.

Hope this stops your high CPU usage.

Msosync is run via a task in Task Manager. To disable it:

Start >> Administrative Tools >> Task Manager >> Highlight "Task Scheduler Library".

You will see a task called "Microsoft Office 15 Sync Maintenance for..."

Right click on it and choose "Disable".

Even if you disable the task, the process for MSOSync will still be running. So, to stop it you either have to reboot, or kill the process using Task Manager.

Hope this stops your high CPU usage.

I meet the same problem.  CPU usage was once stay at 100%.  4 steps help me to get ride of it.

setp1. Upate the office 2013. by "check for update"

step2, Disable the "Microsoft Office 15 Sync Maintenance for..." Task.

step3. remove the component "skydrive 2013 pro" from office 2013 installation.

step4. kill the process "MOSSYNC" in the task manger.

After these,  CPU usage jump back to 8%. hope this approach may works for anybody!

If other responses below didn't work foor you and if you are uncomfortable with manually editing the Registry the get the Sysinternals Autoruns application here:

--> http://technet.microsoft.com/en-us/sysinternals

Install it anywhere you want, run it and accept the license terms, and then use the Find sialog to search for 'mso' (without the quotes). The relevant entry will be that naming the executable msosync.exe. Just uncheck the box to the left.

Just a caution: this utility edits the registry and you might damage your system by changing the wrong entry. Stopping msosync, however, should not cause issues.

I renamed the file and the process stopped, renamed it back and still not running.

I am assuming though that each time I restart my PC that I will need to repeat the steps?

thanks much for the tip!

Microsoft: Lightweight task keeps Microsoft Office Document Cache in good shape. Disabling this task may lead to unexpected issues when working with documents from online sources as well as higher disk usage.

... Lightweight???

... maybe that has also to do with OneDrive desktop app... When I create a Word document on live.com and OneDrive syncs it to my destkop the msosync.exe problems starts ...