Rice-Jones reports months of warmth, fan noise, and declining battery endurance before finding Windows Search Indexer busy at idle. His index contained more than 700,000 items; after removing the network location, he says, it still held more than 350,000. Those are observations from one laptop, not controlled measurements establishing how much heat or battery drain indexing caused.
The underlying mechanism, however, is documented by Microsoft: Windows Search locally indexes network files held in the Offline Files client-side cache. The important distinction is that Windows was indexing cached copies—not simply deciding to catalog every NAS it could see.
How NAS files become a laptop workload
Microsoft describes Offline Files as a way to retain local copies of files from network shares. You can continue working when the connection disappears, and changes synchronize with the server when connectivity returns. That is useful for travel and unreliable connections—but it also means network storage can become a local storage responsibility.
In Rice-Jones’s account, selecting Always available offline on a network folder created the connection between his NAS collection and the laptop’s search index.
There are two distinct activities here:
- Offline Files caching and synchronization move and maintain copies between the network share and the computer.
- Windows Search indexing catalogs the locally cached content so it can be searched.
That distinction matters when diagnosing Wi-Fi traffic. Indexing cached content does not, by itself, demonstrate that Windows is repeatedly downloading the whole NAS. File transfer and indexing can contribute to the same overall workload, but they are not interchangeable explanations.
Nor should Enhanced search mode take all the blame. Microsoft describes Enhanced as expanding indexing across the PC, while Classic covers Documents, Pictures, Music, and the desktop by default. That documentation does not establish Enhanced as a mechanism for independently crawling an uncached NAS share. Here, the confirmed bridge is Offline Files.
A large index is a clue, not a conviction
Microsoft’s Windows Search performance guidance offers these reference points:
| Indexed items | Microsoft’s guidance |
|---|---|
| Fewer than 30,000 | Typical user |
| Up to 300,000 | Possible power-user workload |
| More than 400,000 | Performance issues may begin |
| Up to 1 million | Documented indexing capacity |
These are troubleshooting guidelines, not a temperature chart. A six-figure count does not prove a NAS is involved.
Microsoft also notes that Outlook adds locally synchronized email to the index. Consequently, comparing an index against only the documents you remember saving can be misleading: the searchable collection may be much broader.
The sensible question is not “Is this number big?” It is “Does this number match what I actually need this laptop to search?”
Check the scope before disabling Search
Start with inspection rather than a service-disabling command:
- On Windows 11, open Settings > Privacy & security > Searching Windows and check Indexed.
- On Windows 10, use Settings > Search > Searching Windows and check Indexed Items.
- Open Indexing Options, select Modify, and review the selected locations.
Microsoft’s newer support documentation labels the Windows 11 settings page Search rather than Searching Windows. Under Find my files, Customize search locations opens the location controls for Classic mode.
If you recognize a network folder that you previously made available offline, decide whether disconnected access is genuinely necessary. Do not remove that capability merely because the item count looks intimidating.
For work-managed devices, involve IT before changing policy. Microsoft warns that domain policy can override local configuration.
Keep offline access without indexing its contents
There is a narrower option than turning off Windows Search or abandoning Offline Files.
The Search policy Prevent indexing files in offline files cache blocks indexing of network-share files made available offline. Its documented policy description explicitly separates offline availability from search indexing.
On a device with the applicable Group Policy editor and administrative permission:
- Open Computer Configuration > Administrative Templates > Windows Components > Search.
- Open Prevent indexing files in offline files cache.
- Set it to Enabled and apply the change.
This is the counterintuitive part: enabling the prevention policy stops cache indexing. It is not a command to delete cached documents. The intended trade-off is continued offline access without those files participating in the local index.
After changing indexing scope, Microsoft documents Advanced indexing options > Advanced > Rebuild on Windows 11. Allow up to 24 hours for rebuilding; Indexing complete is the expected completion status. A rebuild regenerates the index—it does not remove Offline Files.
The lesson is about workload placement
Rice-Jones says removing the location and rebuilding resolved his problem without sacrificing Windows Search altogether. That is a useful troubleshooting direction, but not a promise that every warm laptop has the same cause.
The stronger takeaway is narrower: offline access and local search are separate requirements, and Windows provides controls to separate them. Microsoft documents both the default indexing behavior and a policy to prevent it.
Before evicting Search from the laptop, check what you have asked it to catalog. Sometimes the machine is not doing mysterious work—it is diligently completing a much bigger assignment than you intended.