Windows 11 Indexing is paused
What the hell is up with Windows 11 and the indexing being paused?
I was told by customer help to rebuild, which I did. And it took forever to index a few thousand files (because "indexing is paused") and was still not finished when...
Yesterday, windows took it upon itself to start rebuilding without discussing it with me first, and now I am back at square one - its taking like a bazillion years because "indexing is paused".
All search results return as not found !!!!!!!!!!
Does anybody know how to fix this ****?
Windows for home | Windows 11 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
97 answers
Sort by: Newest
-
Anonymous
2022-05-11T17:47:36+00:00 -
Anonymous
2022-05-11T17:27:49+00:00 -
Anonymous
2022-05-11T15:19:35+00:00 Is this guy for real? Do you not think that most of the internet knows how to press the windows button + R and type services.msc?
Restarting the service does nothing. I tell a lie, it becomes unpaused for all of one minute, and takes an age to index anything, so by the end of the minute, your 10 files better off indexed.
Troubleshooter does not detect issue
Administrator priv does nothing
Windows terminal and commands do nothing
Rebuilding is a waste of time
I read an article stating indexing is limited to 400,000 files? This in itself is annoying as we have about 400,000 images of Jennifer Lawrence from the mobile hack a few years back. Anyway, reducing the number of files through sync does nothing either.
Windows needs some sort of update that will rectify this as it is painstaking for a windows professional user.
-
Anonymous
2022-05-11T14:34:22+00:00 I got KB5013943 and KB5013628 today. Neither looks like they would fix this - but so far every time I have checked my indexing status is "complete".
-
Anonymous
2022-05-08T16:15:50+00:00 Finally found an instance where the paused message appeared and I hadn't run Outlook since rebooting. So turns out that's not a clue. Oh well.