This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
UPDATE possible solution: Try OneDrive's bundled reset script https://support.microsoft.com/en-us/office/reset-onedrive-34701e00-bf7b-42db-b960-84905399050c
Wasn't sure where to post this since there's no OneDrive topic.
I’m using OneDrive insider preview 21.225.1031.0005 on macOS 12.0.1, M1 MacBook Pro. Even when I am not interacting with any files in the OneDrive folder, OneDrive regularly has several seconds of 200+% CPU usage. Immediately after, fileproviderd has long periods of 90% CPU use. This is lousy for battery life. I found at least one mention on Twitter of the same thing. The OneDrive CPU activity is likely not new, but I presume fileproviderd is new with the new OS.
I have 15,000 files synced with 12,000 set to “always keep on this device”. (My account has one very large folder that is excluded from syncing.) I watched a couple times and saw that OneDrive app activity triggered about 2 minutes of fileproviderd activity. Since the OneDrive app often has activity even when I’m not doing anything, this means fileproviderd runs *a lot*.
When this happens, Console shows hundreds of lines like these (in big groups of similar lines; these samples did not come next to each other):
default 09:31:09.436927-0800 fileproviderd ✍️ FP snapshot mutation: update<s:16420 p:16357 n:"a{59}m.jpg" doc sz:9456 m:rwx%<0> ct:1569351878.0 mt:1569351879.0 v:sver:{blob142} cver:{blob139} nsattr:<cap:rwdpf-e- ul:uploaded deco:<com.microsoft.OneDrive.FileProviderBadges.Pinned.Shared> userInfo:<21 keys>>> diffs:structure why:item changed
info 09:31:09.443150-0800 fileproviderd ✍️ reconciliation update: <fs:✅ docID(6521) content:watch sver:fileID(46661205)/b{38}m.jpg cver:46662408@2:sz:165242> <-> <fp:✅ 16288 content:watch sver:{blob142} cver:{blob139}> doc sched:utility#1637083869.443043 rank:1637083696518411264
info 09:31:09.615397-0800 fileproviderd ┏333ca �� trigger: <private>
info 09:31:10.044795-0800 fileproviderd item changed <FPItem 0x1209be840:16603 f:"b{82}m.jpg" p:16582 sz:131 KB cap:rwet bt:1569351583 mt:1569351584 mode:rwx-- uti:public.jpeg ul:uploaded dl:fault>, rules: []
They all seem to refer to nonsense file name strings like a{59}m.jpg and b{82}m.jpg. Those names do not exist in my OneDrive.
I would most like to know if this is a Microsoft problem or whether I should open an Apple bug report.
Processes in Microsoft 365 Insider for installing preview builds, activating subscriptions, and keeping apps up to date with the latest Insider features.
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.
Nobody has found a fix. That's why this forum is here... :(
This is still a very annoying issue and its hard to see that Microsoft doesn't come up with an OneDrive Update, which solves it.
My temporary solution is to start OneDrive once and a while, let it sync, and then close it again.
I recognized, that after closing OneDrive the fileproviderd process still consumes CPU for a certain amount of time (15 minutes) but eventually it disappears from the top cpu consumers again.
The same here, it doesn't go away with restart. As soon as onedrive is loaded, it eats a lot of cpu. Since I moved from intel to m1 max, first time I noticed on my MacBook Pro to run its fans loudly, thanks to onedrive. I grew habit of opening activity monitor and killing it as first thing after restarting, I don't know why I didn't uninstall it still though, I'll just do that actually. Seriously considering moving away from office and onedrive to google now.
Till now no fix from Microsoft? such a **** software.
I killed onedrive app and also fileproviderd process too, however fileproviderd process again keep coming back and eats up 100% CPU. My fan is on.
in the same boat as you guys. not crashing, but Mac fan running 100% temps running 100 degrees, file provider id using 100% cpu, for no reason lol