Update #2 on Build 26.143: Clarifying the Materialization Trigger (System vs. Data)
Following up on my previous post regarding Build 26.143 and bulk hydration on an encrypted external APFS volume:
I want to make a quick technical correction/clarification regarding how macOS File Provider handles file materialization (.CloudStorage/System vs. .CloudStorage/Data).
The Previous Assumption vs. What Subsequent Testing Revealed
In my last update, I noted that after bulk downloading my ~690 GB library using "Always keep on this device," the files sat in .CloudStorage/System with dual Finder badges, but appeared to automatically shift into .CloudStorage/Data after ~12 hours of idle time.
Upon conducting further testing on a completely clean, isolated test system, I discovered that macOS does not run this materialization pass spontaneously just from idle time. #### What Actually Caused the "Magic" Transition
The overnight materialization pass on my primary system was actually triggered because a background file-scanning process (in my case, a scheduled MSP 360 backup sweep) traversed the file system and interrogated the file metadata.
Here is what is actually happening under the hood:
Hydration (100% Downloaded): When you execute a bulk download on Build 26.143, OneDrive fetches 100% of the raw bytes and deposits them locally on your physical APFS drive inside Apple's domain container (.CloudStorage/System). Your data is completely downloaded and safe offline—no internet is required to access it.
The Untouched Idle State: If no application, script, or backup tool actively opens or scans those files, macOS File Provider leaves the payload in .System as dataless stubs (SF_DATALESS). Because of this, Finder displays dual status badges ("Always available on this device" alongside the cloud outline badge) and reports an incomplete "Size on Disk" in Get Info.
The Materialization Pass: The moment an app opens a file, a backup engine indexes the directory tree, or a script touches the file handles, Apple's fileproviderd daemon instantly strips the SF_DATALESS flags, shifts the blocks into .CloudStorage/Data/OneDrive-Personal, and clears the cloud badges in Finder.
Bottom Line
If you run a massive bulk download and see dual badges or DaisyDisk showing data sitting under .System, don't panic—your files are all locally present on disk. Finder's visual badges and Get Info storage calculations simply lag behind until an active file access or backup scan triggers the macOS File Provider materialization pass.
Most importantly, across multiple full-library downloads, version integrity remains 100% pristine with zero file truncation!