As first spotted by Windows Latest, Microsoft confirmed the reports, and it found that the issue goes back to KB5064081 ...
Results that may be inaccessible to you are currently showing.
Hide inaccessible resultsResults that may be inaccessible to you are currently showing.
Hide inaccessible results
Feedback