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

84 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-06-22T22:59:41+00:00

    Hi Vladimir,

    From what I've seen it looks like it's happening with every one using Office 2016 and up, on Windows 10.  I'm running Win 10 Version 2004 with latest build 19041.329 on 2 Desktops that I built.  Both have i7 Gen.8 processors.  I'm running Office 2010 Pro with latest version on one of them, and it running Great, no problems.  My other PC I upgraded to Office 2016 Pro (Retail Version) because MS is going to stop supporting Office 2010 sometime this year.  I think kx707 said they're running Office 2013 on a PC with no problems, but everyone reporting the problem seems to be using Office 2016, 2019 and 365, with Window 10.  Also seems problem started with latest update of Office.

    Turning Metered Service off fixed problem temporally, like you said, but my problem came back after a restart due to installing an updated driver.  Still waiting on MS for a permanent fix.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-06-22T19:01:47+00:00

    It seems like its universal for users with latest office update ..  i found this  issue even in amd environment >>  MSO16 Version 2005 Build 12827.20336  in my AMD based win10 v2004 desktop.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-06-22T06:11:10+00:00

    It may be that the problem only affects a small portion of users. 

    I mean, we didn’t even compare our configurations, and this could well be a Windows version-specific or even a driver problem.

    My configuration is:

    Thinkpad X1 Carbon Gen 6 (i5/8/256), using the built-in Fibocom L850-GL WWAN module

    Windows 10 Pro 64bit, version 1909

    Office 365 64bit

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-06-22T05:53:36+00:00

    I followed your link and read everything everyone had to say regarding this problem.  It seems, as I found out myself, that turning metered service off is just a temporary fix as well.  Several other members of other threads also found the problem eventually returned, and even though they didn't say that they had rebooted or restarted their system, I assume that that was the case because most are using laptops, and I don't think many people keep their laptops on 24/7.  At least the agents on the other threads said Microsoft was looking into the problem, it really is odd that no one from Microsoft has mentioned anything on this thread.  Thanks again for keeping us updated, it really is appreciated.

    Was this answer helpful?

    0 comments No comments