none
OneDrive for Business uses high CPU since Office 365 1712 8827.2148

    Question

  • Hello everyone

    The OneDrive Support told me that this is not their problem and I should ask here for advice.

    We are using SharePoint 2013 on Premise and therefore have OneDrive for Business (Groove) to sync our userdata with SharePoint.
    Now, since the Office 365 Update 1712 (Build 8827.2148) our OneDrive for Business permanently uses one CPU core at 100%.
    No permanent network traffic, no errors. Sync is working perfectly fine, just high CPU usage.

    Problem affects every computer (approximately 100) that got the update. Repairing and reinstallation of Office and OneDrive did not help.
    Also I was told to delete the local OneDrive cache which also had no impact.

    Does anyone else have this problem or may even knows a solution?!

    Thanks a lot!

    Andy

    Update 07.02.2018: The recent Office 365 Update 1801 (Build 9001.2138) did not resolve this issue. It perists.


    Monday, January 29, 2018 2:42 PM

All replies

  • Hi,

    I have encountered exactly the same problem since updating My Office today. Would very much appreciate any help in resolving this.

    Kalle

    Monday, January 29, 2018 5:49 PM
  • Hi,

    I have the same problem after installing the latest Office update.

    I tried all the 'normal' fixes but it is still the same. When I restart my computer i looks fine, but if I go to the filepath where my files are located, using Windows Explorer, the CPU goes up to around 32% and stays there.

    /Peter

    Tuesday, January 30, 2018 2:28 PM
  • Hi,

    Same problem since newest version :(

    - I have cleaned cache, as suggested on another MS forum.

    - Re-synced all shares from SharePoint.

    And still 12% CPU (this is 100%CPU of one of my cores):

    @MS: Any plan to fix it? 

    /Marcin

    p.s. We can disable heating in our office as all PCs fans are working almost all time now :P xD

    Wednesday, January 31, 2018 9:52 AM
  • Same problem here, in my organization I have 400 pcs. All updated pcs to office 1712 have this issue.
    Wednesday, January 31, 2018 2:55 PM
  • Same thing with Version 1801 (Build 9001.2122 Click-to-Run) and SharePoint Server 2013

    John

    Wednesday, January 31, 2018 3:56 PM
  • We are having the same issue here as well, same problem and same environment. Luckily we are in transition to 365 and only have a couple dozen laptop with this issue. Microsoft needs to address this.
    Wednesday, January 31, 2018 6:50 PM
  • Hi,

    According to your description, it seems that it is cased by this update.

    You can use the dump file to narrow down this issue.

    By the way, this issue is difficult to solve through the forums to help you.

    I suggest you open a ticket from Microsoft, this will help you to solve the issue as soon as possible.

    Thanks for understanding.

    Best Regards,

    Carl Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, February 01, 2018 6:07 AM
  • We have exactly the same issue here! Sharepoint 2013 Server (on Premise) und Office 365 (One Drive for Business).

    When can we expect a fix? 

    Thursday, February 01, 2018 7:30 AM
  • Hi,

    I'd love to make a ticket for this issue, yet my company does not have the budget for that sadly.

    It is also weird that there are so many people now with this problem and Microsoft still does not seem to want to act on their own.

    Thursday, February 01, 2018 9:12 AM
  • I suffer from high CPU usage as well.  WHat I noticed is that if I pause the syncing.  Stop the client and restart it, the client remains low in CPU utilization.  But as soon as I resume syncing, the CPU usage gets pegged.

    This is especially frustrating as I am using a Surface Pro that is having issues with CPU throttling and Fans (it shuts off / standby if I don't kill the process soon enough).

    Thursday, February 01, 2018 2:10 PM
  • I have the same exact issue on a Lenovo laptop and a Surface Pro 4, both are running Office 2016 Click-to-Run version 1712 (build 8827.2148 Click-to-Run).  Groove.exe consumes around 40% CPU on a dual-core i7 Surface Pro 4 and about 20% CPU on a quad-core i7 Lenovo laptop, causing the fans to run much more than normal due to the overall higher CPU usage.

    My OneDrive for Business (Groove) client is connected to my OneDrive for Business personal storage in an on-premise SharePoint 2013 server.

    I have disconnected the library, deleted the local cache, rebooted and then re-connected the client to my OneDrive for Business library in our on-premise SharePoint 2013 server and the high CPU usage issue still persists.




    • Edited by mike.driest Friday, February 02, 2018 6:35 PM Updated CPU usage
    Thursday, February 01, 2018 3:42 PM
  • Same issues with 1712 (Build 8827.2179) x64 - I just updated, One Drive for Business is using approx 30% CPU for no reason - MS where is the fix?

    Thursday, February 01, 2018 10:18 PM
  • Same issue, around 30% CPU, (1 core 100%). Really really annoying. I'm continuously shutting down the sync client as a workaround but it's not practical.
    Friday, February 02, 2018 9:08 AM
  • Hi Carl,

    Our IT made Ticket.
    What troubles me is that as you may see this is global problem, maybe you can escalate this issue higher or provide us with link where we can track problem?

    /Marcin

    Friday, February 02, 2018 10:38 AM
  • Thank you very much Marcin! You're a lifesaver!

    Let's hope that the issue will be found quickly and already resolved in the next update cycle. (But that might be a bit too late already sadly.)

    Friday, February 02, 2018 10:46 AM
  • Just adding my voice to everyone else's. Since the latest update, OneDrive for Business hovers around 31% CPU usage. My current approach is to shut it down most of the time turning it on once or twice a day to bring my synchronization up to date.

    I hope Microsoft gets the message and fixes this one quickly!

    Saturday, February 03, 2018 6:00 AM
  • Hi,

    I have the same problem after installing the latest Office update!!!

    Saturday, February 03, 2018 3:31 PM
  • I have this same issue. But what I don't get is that even when I close the application with Task Manager, it starts running automatically again after a few minutes. I have to keep terminating it manually. I also can't see an option to prevent OneDrive for Business from running at startup.
    Sunday, February 04, 2018 8:50 AM
  • Same here - Onedrive for business, version 16.0.8431.2153

    I've renamed groove.exe to something else in here and it stops it's respawning.

    C:\Program Files (x86)\Microsoft Office\root\Office16\


    Eliot

    Sunday, February 04, 2018 11:08 AM
  • Hi,

    Got reply from Support, but it seems that Microsoft Support is focusing on onedrive.exe not on groove.exe.

    Nevertheless this is what they wrote:

    ISSUE
    High CPU usage is observed, after OneDrive for business update.  

    SCOPE
    The case is going to be considered as resolved, one the high CPU utilization is not present. In addition, the case is considered solved and can be archived, if we establish that the problem is 3rd party software/hardware problem, bug or behavior by design.  

    FINDINGS
    Please follow the suggested action plan below:

    1. Open Task Manager, right-click the Microsoft OneDrive process and select End Task. Restart OneDrive and see if this helps.

    2. Rest the one drive application and see if that works. https://answers.microsoft.com/en-us/onedrive/forum/odstart-oduninstall/full-reset-of-onedrive-on-windows-10/12a357f8-7773-4856-bf0c-0ecd308f4184?auth=1

    3. If the above does not help, exit OneDrive and navigate to the following location in File Explorer: %AppData%\Local\Microsoft\OneDrive\setup\logs Locate the following two hidden files and delete them. a. UserTelemetryCache.otc b. UserTelemetryCache.otc.session Now restart OneDrive and see if it helps.

    4. If nothing helps, you may have to uninstall OneDrive completely and reinstall it again.

    UPDATE:
    Fix provided from Support does not fix the problem.


    Tuesday, February 06, 2018 8:13 AM
  • Adding myself to the list. Exactly the same problem here.

    MICROSOFT: How about a fix??

    Tuesday, February 06, 2018 10:43 AM
  • Add me and my organization to this list as well. I have been researching this for a few weeks now and tried the below steps with no luck.  Comes right back. CPU between 20% and 50% and the only way i really noticed was because it gets my Surface Book fans going which hardly ever run. 

    1. Open Task Manager, right-click the Microsoft OneDrive process and select End Task. Restart OneDrive and see if this helps.

    2. Rest the one drive application and see if that works. https://answers.microsoft.com/en-us/onedrive/forum/odstart-oduninstall/full-reset-of-onedrive-on-windows-10/12a357f8-7773-4856-bf0c-0ecd308f4184?auth=1

    3. If the above does not help, exit OneDrive and navigate to the following location in File Explorer: %AppData%\Local\Microsoft\OneDrive\setup\logs Locate the following two hidden files and delete them. a. UserTelemetryCache.otc b. UserTelemetryCache.otc.session Now restart OneDrive and see if it helps.

    4. If nothing helps, you may have to uninstall OneDrive completely and reinstall it again.

    Tuesday, February 06, 2018 2:56 PM
  • That "Action Plan" is exactly what I meant in my innitial post with "Also I was told to delete the local OneDrive cache which also had no impact."

    So basically, back to step one.

    Microsoft, please listen. There is an error here that various multiple companies are expiriencing and we need your help.

    Tuesday, February 06, 2018 3:43 PM
  • Added it to the top too but just in case someone checks the last messages first:

    The recent Office 365 Update 1801 (Build 9001.2138) did not resolve this issue. It perists.

    Wednesday, February 07, 2018 9:06 AM
  • I have the same issue with Office 365 1801 (Build 9001.2138) and no fix till now.

    Wednesday, February 07, 2018 12:37 PM
  • Also on v 1801 and seeing this same issue. It has begun to effect more users throughout our ORG as well. 
    Wednesday, February 07, 2018 5:17 PM
  • On my two Win 10 Pro x64 devices I am running 2016 x86 Version 1801 (Build 9001.2138 Click-to-Run) with Groove.exe still constantly using the CPU.
    Wednesday, February 07, 2018 6:54 PM
  • I concur. Built 9001.2138 doesn't work.

    Like everybody, I had to stop OneDrive for Business entirely and have to rely on browser access for now, which is certainly not ideal.

    I look forward to a fix.

    Wednesday, February 07, 2018 7:46 PM
  • I have the same issue with Office 365 1801 (Build 9001.2138) and no fix till now.

    Same issue here using 1801 Build 9001.2138 too. Tried to get detailed information what causes this issue using process monitor but found nothing helpful. Waiting for fix.
    Thursday, February 08, 2018 6:42 AM
  • Exact the same problem with the same versions as mentioned above. None of the mentionend things helped.
    • Edited by Helge Hoehn Thursday, February 08, 2018 10:18 PM
    Thursday, February 08, 2018 10:18 PM
  • Same here again with consist around 31% usage. It's so annoying and slow down my whole comp.

    

    


    MCSD .NET, SCJP, SCJWD

    Thursday, February 08, 2018 11:35 PM
  • Hate to say 'me too'.....but me too. Been this way for a month or so now. 

    Does it on my Dell Latitude 7480 on Windows 10 1709 RTM (25% CPU on a Core i5) and on my Surface 4 Pro on Windows 10 17093 (25% CPU on a Core i5). 

    Syncing to an on-premises Sharepoint 2013 library. 

    Fan noise is driving me nuts. 


    Friday, February 09, 2018 12:52 AM
  • Exact same issue here, observed on two separate machines. Version 1801 (Build 9001.2144) is still broken, and yes it has been going on for about a month.

    Deleting UserTelemetryCache.otc and UserTelemetryCache.otc.session did NOT work.

    Depending on the machine it is pegged at 20-30% CPU doing nothing.

    I hope Microsoft are listing because constantly exiting the OneDrive app every time I open Office is driving me nuts too.


    • Edited by eforgacs Friday, February 09, 2018 6:48 AM
    Friday, February 09, 2018 6:46 AM
  • #MeToo
    Friday, February 09, 2018 7:37 AM
  • HAHAHAHA, Microsoft address a problem.  I hope you're not holding your breath.  They're as pig headed as our government.

    Helpful nice guy

    Friday, February 09, 2018 8:48 AM
  • The answer he gave you is normal IT answer.  Create a ticket and we'll take care of it.  Yeah right.  More like "Wait until someone finds something they can exploit, they'll create a virus that takes advantage of it then Microsoft will do something about it."  Oh wait, that doesn't always work.  File extensions are still hidden by default but yet viruses take advantage of the hidden extensions every day.

    Sorry if I sound sarcastic but I've been in IT for over 20 years and it never changes.  Companies think they're never wrong.


    Helpful nice guy

    Friday, February 09, 2018 8:52 AM
  • Exactly the same issue here.  Brand new high spec laptop, was working great then I applied the updates!

    Version 1801.

    :(

    Friday, February 09, 2018 10:00 AM
  • Seems as if i did solve my problem here:

    Stopped synching, and with that i did cut the connection of that pc with online.

    Stopped OneDrive for Business (right mouseclick - exit).

    Restartet Windows, deleted the old local synch-folder, then i went online with browser to the onedrive and did hit "Synch"-Symbol from there. This started Onedrive for Business again, asked for password, i then changed the local folder to something else (as i always do), and started synching.

    All fine now.

    The difference is that i did not supply the adress to be synched within the onedrive-tool, but i passed that piece of information by hitting "Synch" in the online-view.

    Give it a try, i can't tell you why that helped.

    • Proposed as answer by trlbb Sunday, February 11, 2018 10:57 AM
    • Unproposed as answer by Miingno aka. Andy Thursday, February 15, 2018 9:10 AM
    Saturday, February 10, 2018 2:55 PM
  • Brilliant, thank you so much!

    I followed your instructions to the letter except for the reboot part, which I skipped. What this seems to do is force migration from GROOVE.EXE to OneDrive.exe which now handles both OneDrive personal and OneDrive for Business.

    Note: based on my scientific observation of a representative sample of 2 PCs ;-), the groove.exe problem seems to only occur in Windows FCU, because I never experienced it on my Work PC which is running a less recent release of Win10.

    • Edited by trlbb Sunday, February 11, 2018 3:07 PM
    Sunday, February 11, 2018 11:03 AM
  • I think you are right with the migration thing... as i recognized after that trick, that at every reboot a popup occured asking me to specify a library to synch with... although in the taskbar i could see Onedrive already activ, and status "All synched". Then, after some while, i detected that i had two cloudsymbols running, the activ one, and the second one starting with windows and asking for a hyperlink to a library. I disabled that one with deselecting "Start with Windows Boot", and then it was gone. So... somehow to instances of onedrive arround here ;-)
    Sunday, February 11, 2018 11:20 AM
  • I've been frustrated with the same problem, but problem solved with the help of the comments in this forum.

    Step 3 of @Outlanderbz's solution worked for me, with the extra step that @NoPlayback suggested.

    1. I exited Onedrive for Business (right mousclick - exit),
    2. then deleted the two files in %AppData%\Local\Microsoft\OneDrive\setup\logs (a. UserTelemetryCache.otc b. UserTelemetryCache.otc.session)
    3. then restarted my computer
    4. then i went online with browser to the onedrive and hit "Sync"-Symbol from there.
    5. waited for password prompt to come up (it took about 2 minutes before it popped up), entered password, and all seems fine now.
    Sunday, February 11, 2018 3:44 PM
  • Although this cannto work for on premise stuff I tried and failed. There is no migration to OneDrive for on premise Sharepoint. As a hint: If I stop GROOVE.exe and make sure that there is no explorer window "sitting" on the One Drive For Business folder, then GROOVE.exe is not restarted and everything seems to be fine. As soon as I start a Windows Explorer and change to the folder GROOVE.exe appears and consumes a whole CPU/thread.

    Monday, February 12, 2018 1:47 PM
  • I've tried this and unfortunately it doesn't work for me.

    I've even downloaded the most up to date OneDrive.exe but that gives me a connection error.


    Wednesday, February 14, 2018 5:05 PM
  • Thanks NoPlayback for your suggestions here. Glad it worked for you but nothing for me. Still sitting on the CPU.
    Thursday, February 15, 2018 9:11 AM
  • It appears Microsoft is phasing out Groove.exe.

    https://support.office.com/en-us/article/changes-to-the-previous-onedrive-sync-client-groove-exe-in-office-2016-click-to-run-3eff17b9-c709-462f-946c-17719af68aca


    • Edited by Jessy_D Thursday, February 15, 2018 2:31 PM
    Thursday, February 15, 2018 2:31 PM
  • It appears Microsoft is phasing out Groove.exe.

    https://support.office.com/en-us/article/changes-to-the-previous-onedrive-sync-client-groove-exe-in-office-2016-click-to-run-3eff17b9-c709-462f-946c-17719af68aca


    Interesting that no one at Microsoft yet mentioned this here.. That's kinda a key point for this issue.

    However it means a LOT of work for companies like ours where hundreds of people are currently using Groove to sync data... Thanks MS

    Friday, February 16, 2018 7:16 AM
  • It appears Microsoft is phasing out Groove.exe.

    https://support.office.com/en-us/article/changes-to-the-previous-onedrive-sync-client-groove-exe-in-office-2016-click-to-run-3eff17b9-c709-462f-946c-17719af68aca


    Interesting that no one at Microsoft yet mentioned this here.. That's kinda a key point for this issue.

    However it means a LOT of work for companies like ours where hundreds of people are currently using Groove to sync data... Thanks MS

    So I made a test and excluded Groove.exe as suggested in the article above. Sadly now I am unable to sync with our on-premise installation as it just tells me, no suitable OneDrive for Business client is installed. And when I try to download the newest OneDrive client it simply tells me, that I already have a newer version installed.

    Should've read the fine print on the page above confirming that:

    "However, the previous OneDrive for Business sync client (Groove.exe) is still fully supported and is used for on-premises instances of OneDrive for Business or SharePoint Server"

    And with that I want Microsoft to finally fix that bug please!

    Friday, February 16, 2018 8:03 AM