Microsoft Office Click-to-Run (SxS) High CPU

Anonymous
2020-06-08T19:16:00+00:00

I am using Office Home & Student 2019 with Windows 10 Home. The June update was recently completed to Version 2005 Build 12827.20268.

After installing this update I noticed that Microsoft Office Click-to-Run (SxS) showed continuous 24% CPU utilization in the Task Manager. Power usage was shown as very high. This did not occur prior to the update. I have metered connection set in the network settings and discovered that the problem goes away if I turn off metered connection and restart the computer.

Does this sound like a bug in the latest update? I have Office 2013 on another computer and there is no problem on that system with metered connection set. I'd be interested if others have seen this problem or have any suggestions.

Microsoft 365 and Office | Excel | For home | Windows

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
2020-06-25T00:39:40+00:00

Hi KenBell6 & Everybody else,

Just got latest update for my version of Office (Office 2016 ProPlus Retail - 32bit).  Found it on Current Preview Channel.  Downloaded it and rebooted my PC and CPU Usage is back to what it used to be.

Don't know if it's a permanent fix, hope it is, but it seems to be working fine so far, after 3 reboots (just to play it safe).  I have several Office apps open, and as you can see above it looks pretty good.  Good luck everyone, let me know if it worked for you.

Was this answer helpful?

5 people found this answer helpful.
0 comments

84 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-06-12T05:02:05+00:00

    Same here: I’m not sure when exactly this happened, I’m not even sure my Office did install every update there was. I mean, it’s quite possible it went, say, from 2002 to 2005 directly. 

    I had used the Office deployment tool to downgrade to version 2003, but as I’ve said earlier, that didn’t help. 

    After I’d removed Office completely and installed 2002 with the standalone installer, there were no problems until I installed a language pack (for spellchecking, I type in several languages), after which the version bumped to 2005 again. This is how I learned that language packs pull and install current updates for the Office. 

    So I removed it again and installed version 2002, and I am going to keep that 3.4GB file for the time being, as Microsoft will certainly update the standalone installer version at some point.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-06-12T04:47:23+00:00

    Since I've got things back to normal, so far, I want to let it ride for a few days and see if cpu usage stays where it is.  If it does, I want to start updating one Version of Office at a time, I think there are 5 or 6 from where I'm at right now Version 2003(Build 12624.20466).  It seems like once the cpu problem occurs, it might effect windows 10 too, because the roll backs didn't help me at all, but I stopped at 2003?  I used the Office deployment tool I found on another thread. I'd like to find out which Version and Build caused the problem for sure.  Did your problem occur with update Version 2005(Build 12826.20336)?  I had 2 updates within a week and that's the last one I had when I noticed the problem.  It may have occurred on an earlier update, but I'm not sure.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-06-12T04:25:04+00:00

    Reverting to 2003 didn’t help me either, uninstalling Office and installing version 2002 with the stand-alone installer helped.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-06-12T02:02:33+00:00

    Didn't mean to waste anybody's time.  I just said it worked of me.  I'm still running 2 to 3% CPU usage.  It may still be the version of Office, but going back to Version 2003 didn't stop the high CPU usage.  It only worked for me when I did a repair of Win. 10.  I'm still using Version 2003 of Office, and won't update again until I see something from Microsoft about a fix.  I apologize for wasting anybody's time if they tried my suggestions and it didn't work.

    Was this answer helpful?

    0 comments