Microsoft office Click-to-run process running with high CPU and memory

Anonymous
2015-01-04T09:11:11+00:00

HI There,

I have a HP pavilion laptop running windows 8.1 and office 2013.

Things have been fine from Feb to until Nov this year, after which point I noticed the mouse cursor showing the busy revolving circle all the time, performance was reduced and the computer sounded like it was constantly working.

I traced the problem to the Microsoft office Click-to-run process running with high CPU (5+%) and memory (50+mb). If I restarted the click-to-run service the use of computer resources dropped to minimal and the problems described in the first paragraph disappeared.

Unfortunately as time has gone on an error occurs when trying to stop the click-to-run process so the above restart fix does not work and the longer the laptop is on the worse the performance gets.

I have reinstalled office twice, I hace clicked the office repair option and searched the web for a solution all to no avail.

Please can somebody help find a solution as it is driving me mad and making my new laptop unusable. BTW my partner has a similar laptop setup with no issues.

Kind Regards

Bob.

Microsoft 365 and Office | Install, redeem, activate | For home | Other

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
2015-01-20T15:29:20+00:00

Hi There,

I solve my problem.

Symptoms:

  • Process Office 15 click-to-run running constantly 20% CPU
  • Process MSOSYNC (document cache) 0% CPU and still restarting (on bacground)

The main problem is Document cache, because process MSOSYNC is not loaded and any orange tray icon (with arrow) as Office document cache in task bar is not visible.

How to solve this problem:

  1. disable service click-to-run (in services - set disabled)
  2. restart computer (click-to-run will be not loaded)
  3. open C:\Users\Username\AppData\Local\Microsoft\Office\Spw and delete all files
  4. open C:\Users\Username\AppData\Local\Microsoft\Office\15.0\OfficeFileCache and delete all files
  5. enable service click-to-run (set automatic)
  6. restart computer

The problem is solved - for me.

Was this answer helpful?

900+ people found this answer helpful.
0 comments No comments

45 additional answers

Sort by: Newest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2015-06-06T13:41:34+00:00

    Hi, I have been noticing a similar issue with my computer as well; which I seemed to have fixed for the time being. However my set up is a little different than yours is: 

    I am running windows 8.1 with Microsoft office 2010; however I use OneNote 2013. I noticed that recently when I booted OneNote 2013 my CPU usage would spike to 50-60% and remain there until I ended the "Microsoft office Click-to-run process". It seems I have fixed the issue for now by going into Control panel --> uninstall program --> find Microsoft OneNote 2013 --> Right click --> select Change --> select Quick Repair -->and press Repair . Once the repair was complete opening OneNote2013 did not cause the high CPU usage. Perhaps running a repair on the entire Office 2013 suites may help those who have all the programs installed. I will update if the issue returns, hopefully this helps

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2015-06-03T07:31:44+00:00

    This works indeed perfect. Thank you very much for your help.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2015-06-01T16:40:54+00:00

    This worked great !!  Thanks again

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments