Skip to main content
Question

Box Drive causes permanent fileproviderd enumerator flood after restart

  • April 14, 2026
  • 0 replies
  • 1 view


## Environment

- **macOS**: Apple Silicon (M-series)
- **Workflow**: MATLAB accessing (FieldTrip) functions stored in Box Drive (cloud-only / streaming mode)

---

## Problem

After restart, Box Drive causes `fileproviderd` to use high amount of CPU (100%) that makes **all Finder file operations hang indefinitely** — including copy/paste, and any application (e.g. MATLAB) that reads files stored in Box Drive.

---

## My guess

`streem` (Box's internal sync engine) launching with `--folder-prefetch-depth 1`, might cause it to enumerate all folders at startup, which might flood `fileproviderd` with dozens of enumerator requests per second.

## Terminal Diagnostics

(base) ***@mac ~ % log stream --predicate 'process == "fileproviderd" AND eventMessage CONTAINS "box"' --level default

Filtering the log data using "process == "fileproviderd" AND composedMessage CONTAINS "box""

Timestamp Thread Type Activity PID TTL

2026-04-13 22:15: [removed by moderator] 0x4b850 Default 0x0 1380 0 fileproviderd: (Foundation) [com.apple.foundation.filecoordination:claims] Write options: 80000000 -- URL: <private> -- purposeID: com.box.desktop.boxfileprovider -- claimID: A30479E8-5B83-4DD6-A8E4-88E28D50E48A

2026-04-13 22:15: [removed by moderator] 0x4b856 Default 0x0 1380 0 fileproviderd: (Foundation) [com.apple.foundation.filecoordination:claims] Write options: 80000000 -- URL: <private> -- purposeID: com.box.desktop.boxfileprovider -- claimID: E1B861C1-4051-4F3A-8185-1596A4997250

2026-04-13 22:15: [removed by moderator] 0x4b856 Default 0x0


```
sudo fs_usage -f filesys fileproviderd | grep Box

22:17:46 openat [-2]//Users/***/Library/CloudStorage/Box-Box 0.000041 fileprovider

22:17:46 openat [-2]//Users/***/Library/CloudStorage/Box-Box 0.000013 fileprovider

22:17:46 openat [-2]//Users/***/Library/CloudStorage/Box-Box 0.000014 fileprovider

22:17:46 openat [-2]//Users/***/Library/CloudStorage/Box-Box 0.000012 fileprovider

22:17:46 openat [-2]//Users/****/Library/CloudStorage/Box-Box 0.000012 fileprovider

22:17:46 openat [-2]//Users/***/Library/CloudStorage/Box-Box 0.000013 fileprovider

22:17:46 openat [-2]//Users/***/Library/CloudStora


```

How could I avoid the situation when box drive is taking a few days after restarting the computer before I can actually access the files?