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
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

45 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-05-30T17:38:40+00:00

    I agree that OneNote is a factor but I have discovered that if I pause synching on OneDrive then the problem goes away till I resume synching again.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-30T10:21:01+00:00

    I have also tried the suggested solutions, but none of them seem to solve anything. The problem reappears after reboot / re-install. As a temporary solution, I stop the click-to-run task, but the service will restart it again soon after. I would really appreciate if Microsoft could provide a fix for Office asap.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-05-29T20:39:19+00:00

    Having the same problem.  Followed the instructions and the same problem occurs repeatedly whenever (1) I open up OneNote or (2) made a change in OneNote.  My OneNote syncs to files via OneDrive which I suspect is the problem.  After I end the Microsoft Office Click-to-Run service the annoying circle by my cursor goes away ... but reappears the moment I open OneNote.  There has to be a solution to this annoying problem!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-05-21T20:52:54+00:00

    This issue just recently started on my machine.  I have followed the steps listed below along with the clean boot.  As soon as I open Microsoft OneNote 2013, my CPU usage jumps immediately to 30% and stays there for a while.  It will eventually go back to normal, but as soon as i click on OneNote, 30% CPU usage.  Please help.  Joe.

    My machine is a privately built desktop.

    Was this answer helpful?

    0 comments