
There are times when the Windows Search doesn’t work and you wouldn’t have a clue as to why it happened since it does not give any error codes. In such cases, you have to check the error logs in the Event Viewer to find out more about the problem. From there, look for an error with the Event ID 3104 in the Windows error logs and if you see an error message that says, “Enumerating user sessions to generate filter pools failed”, read on as this post will guide you in fixing the problem. Apart from the error message, you might also see more information in the details section of the log that says, “(HRESULT: 0x80040210) (0x80040210)”.
This kind of error is most likely caused by something that prohibits the search function from initializing. A lot of users assumed that it could be due to Cortana but it’s actually not. While some users also reported that they encounter the issue after they restarted their computers. This error was also reported with the same event ID 3104 on the Windows Server. According to security researchers, this error could be caused by problems in the Registry entry of Windows search. It could also be due to an issue with the SYSTEM account where it hasn’t been added to the DCOM Security. It is also possible that the Windows Search function has not been initialized.
To fix this error, you can try to rebuild the Search Index manually or run the Search and Indexing troubleshooter. You can also check the startup type of the Windows Search service or try some registry tweak.
The first thing you can do to fix the problem is to manually rebuild the Search Index. You can do that by going to Control Panel > Indexing Options and from there, click on Advanced. After that, go to the Index Settings tab and then click on Rebuild > OK. Once you’re done, check if it fixed the problem.
You could also run the Search and Indexing troubleshooter in Windows 10 as it checks whether the settings are in place and automatically corrects any issues with the Windows 10 search function. To run this troubleshooter, just click on the Start button and select Settings > Updates and Security > Troubleshoot. From there, select the Search and Indexing Troubleshooter. Once the troubleshooter is done, restart your computer and see if it fixed the error.
In this option, you have to check the startup type of the Windows Search service since the service won’t start. To do so, refer to these steps:
Before you apply some registry tweak, you need to create a System Restore point first. Once you have that covered, follow these steps:
“Connapi.dll Not Found" "This application failed to start because connapi.dll was not found. Re-installing the application may fix this problem." "The file connapi.dll is missing." "Cannot start [APPLICATION]. A required component is missing: connapi.dll. Please install [APPLICATION] again." "Cannot find [PATH]connapi.dll"
Error code 0x000000D1 is a serious error that is displayed when Windows automatically shuts down to protect the system against further damage.
Usually, when this error occurs, the message displayed to the users states something like STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL.
Usually, the STOP 0x000000D1 error code is caused by issues like incompatibilities, third-party drivers, driver conflicts, outdated drivers, malicious drivers, and other related problems.
Speaking technically, the message displayed to the user actually means that the kernel-mode driver has tried to gain access to memory at an unreasonably high process IRQL.
If left unfixed, STOP 0x000000D1 error can become quite serious. Increased frequency of occurrence may not only lead to data loss but can cause system corruption as well. That’s why it is crucial to fix it and to resolve the underlying issues causing it as soon as possible.
dism.exe /image:C: /cleanup-image /revertpendingactionsAfter you execute the command, restart your computer and try to run System File Checker again and see if it has fixed the problem or not.