Windows indexing rebuilding nonstop

Hi there,

Thanks for your help.

I forgot to mention but the Office version I have installed is 32-bit. If you have any guidelines in this case, I appreciate it.

Thank you

Alexandre Silva

Since you are using the 32-bit version of Office, please completely disregard the previous registry steps involving the Wow6432Node directory. That specific registry key is actually required for your 32-bit applications to communicate properly with the 64-bit Windows system. The indexing loop in a 32-bit Office environment is frequently tied to the strict memory limitations of the 32-bit search protocol handler. When this background process attempts to read massive or even slightly corrupted Outlook data files, it exhausts its memory limit, crashes entirely, and forces the Windows indexer to drop its progress and start over from scratch.

To resolve this, you need to repair the structural integrity of your Outlook data files directly before the indexer attempts to scan them again. Open File Explorer and navigate to your Office installation folder, which is typically located within the Program Files (x86) directory under Microsoft Office and then the root folder for your specific version. Locate and run the built-in Inbox Repair Tool executable named SCANPST.EXE. Browse to your specific .pst or .ost files, which are usually hidden inside your local AppData directory under Microsoft and Outlook. Run this repair process on your large mail files multiple times until the tool reports that no further errors exist.

Once your data files are structurally sound, right-click the Start button, open your installed apps list, and perform a Quick Repair on your Microsoft Office installation. This action automatically verifies and rewrites the correct 32-bit search filter registry keys without requiring any risky manual registry edits. After the Office repair finishes, ensure your Dropbox syncing is paused just as before, restart your computer, and leave the system completely idle overnight so the Windows Search service can process the repaired Outlook files without hitting memory conflicts.

Hope this helps :)

VP

Hi Alexandre Silva,

The continuous indexing restarts you are experiencing are typically caused by the Windows Search service encountering a corrupted database or a file temporarily locked by an active background program. When the indexer hits these conflicts, usually triggered by large Outlook data files or actively syncing cloud folders like Dropbox, it drops its current progress and attempts to start over. Adding a new indexing location intentionally triggers a restart, but the underlying corruption prevents the process from ever completing. To resolve this permanently, you will need to bypass the standard control panel rebuild options and manually clear the core database.

Begin by opening the Windows Services application and completely stopping the Windows Search service, which forces it to release any locked database files. Open File Explorer, navigate to your main system drive, and access the hidden ProgramData folder. From there, follow the path through Microsoft, Search, Data, Applications, and finally the Windows folder. Inside this directory, locate and delete the Windows.edb file or clear the entire folder contents to force your system to generate a completely clean database upon the next restart. If you are running a 64-bit version of Office, a known registry conflict with the 32-bit search protocol handler can also cause these crashes. Open the Registry Editor and navigate to the Wow6432Node directory inside both the HKEY_CLASSES_ROOT and HKEY_LOCAL_MACHINE hives. If you find the CLSID folder named {F8E61EDD-EA25-484e-AC8A-7447F2AAE2A9}, you can delete it from those 32-bit nodes to ensure Windows correctly utilizes the 64-bit search protocol handler.

Before you restart your computer to initiate the new index, ensure you pause your Dropbox synchronization. Cloud syncing applications frequently lock files while checking for server changes, which can immediately crash your freshly running indexer. After restarting, leave Dropbox paused and keep your PC powered on and completely idle overnight. The search indexer runs at maximum speed only when the computer is inactive, so providing it with an uninterrupted overnight window will allow it to successfully build a stable catalog of your Outlook and local files.

Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

VP

Continuous rebuilding of the Windows/Outlook search index typically indicates a problem with the index store or with how Outlook data is being indexed. Use these steps to stabilize it:

1. Let indexing complete when possible

• The indexer only runs at full speed when the PC is idle. If large Outlook data files (.pst/.ost) or many Dropbox files are included, indexing can take a long time and appear to “restart.”
• Open Indexing Options and confirm the status shows “Indexing complete” at least once after leaving the PC idle for an extended period.

2. Rebuild the Windows Search index If indexing never completes or keeps looping, rebuild the index:
3. Close Outlook.
4. Open Control Panel.
5. Choose Indexing Options (or search for Indexing and select Indexing Options).
6. Click Advanced.
7. On the Index Settings tab, under Troubleshooting, select Rebuild and confirm.
8. After the rebuild starts, leave the machine on and as idle as possible until the status shows indexing is complete.

This clears a corrupted index catalog and forces a clean build, which often stops the constant restart behavior.

3. Rebuild the Outlook Instant Search catalog If the issue is mainly with Outlook items:
4. Close Outlook.
5. Open Control Panel → Indexing Options.
6. Confirm Outlook is listed under Indexed Locations.
7. Select Advanced → Index Settings → Rebuild.
8. Reopen Outlook and allow time for Outlook items to be fully re-indexed.
9. Avoid changing indexed locations during rebuild Adding or removing locations while the index is rebuilding can cause it to restart. Wait until Indexing Options shows that indexing is complete before changing locations (for example, adding more Dropbox folders).
10. If using 64-bit Office and Outlook search is still unstable If Outlook search returns no or inconsistent results after the rebuild and Office is 64-bit, follow the registry-based fix for 64-bit Office search issues:
11. Close Outlook.
12. Open regedit and verify these keys exist:
    • HKEY_CLASSES_ROOT\CLSID\{F8E61EDD-EA25-484e-AC8A-7447F2AAE2A9}
    • HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{F8E61EDD-EA25-484e-AC8A-7447F2AAE2A9}
13. Delete these keys if present:
    • HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{F8E61EDD-EA25-484e-AC8A-7447F2AAE2A9}
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{F8E61EDD-EA25-484e-AC8A-7447F2AAE2A9}
14. Restart Windows.
15. Open Outlook and wait for indexing to complete (this may take hours).

Editing the registry is risky; back up the registry first as described in How to back up and restore the registry in Windows.

6. Rebuild Windows Search index if OneDrive/Dropbox content is involved If Dropbox (or other synced folders) is included and search status seems stuck or incorrect, rebuild the Windows Search index again from Indexing Options → Advanced → Rebuild, and let it run while the PC is idle.

If, after a full rebuild and a long idle period, indexing still repeatedly restarts or never finishes, this typically indicates a deeper Windows Search or profile issue and may require further OS-level repair or profile recreation.

References:

• You cannot find files when you search a Windows Vista-based computer even though the files exist on the computer
• Outlook issues, including reminders that fail to appear, messages stuck in the Outbox, and Desktop Search indexing problems
• Fix search issues by rebuilding your Instant Search catalog
• No search results for POP, IMAP, or Exchange accounts
• The OneDrive sync status icon incorrectly shows "syncing" in File Explorer