"Not all files are indexed" even though all files are actually indexed

[sibber5]

Microsoft PowerToys version

0.82.1

Installation method

GitHub, PowerToys auto-update

Running as admin

No

Area(s) with issue?

PowerToys Run

Steps to reproduce

As far as i can tell just its there from the start, there arent really any steps to repro.

Indexing is set to enhanced, and some folders are excluded (in addition to the default excluded files). Pending files to be indexed are 0.

Logs zip attached below.

PowerToysReport_2024-07-26-01-49-46.zip

✔️ Expected Behavior

To not get the warning.

❌ Actual Behavior

Getting warned that not all files are indexed even though they are.

Other Software

No response

[similar-issues-ai]

We've found some similar issues:

• Run keeps showing that "Not All files are indexed: #18346 , similarity score: 83%
• Warning Not all files are Indexed #13365 , similarity score: 83%
• "Warning: not all files are indexed" despite Enchanced index setting on Windows 11 #12152 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[sibber5]

All these duplicates seem to say is to disable the warning, but the bug is still there. Not sure whey they were closed

[sacc91]

I got the same on a new Windows 10 PC I just built. It only seems to go away after going into "Advanced Search Indexer Settings" and turning on the C: drive indexing.

Settings > Search > Searching Windows > Advanced Search Indexer Settings > Modify > Local Disk (C:)

[TheJoeFin]

@sibber5 Is this issue still relevant in v0.87? /needinfo

[sibber5]

yes the issue is still there

I still have enhanced indexing turned on like in the screenshot above and i also have all my drives indexed in "Advanced Search Indexer Settings" like sacc91 said

[GlacierFox]

Got this issue too, Windows 11. Same index settings as the OP. Can't get rid of it.

[cinnamon-msft]

/dup #20665

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!