{"id":9026,"date":"2019-05-05T03:15:22","date_gmt":"2019-05-04T21:45:22","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=9026"},"modified":"2023-07-31T20:49:35","modified_gmt":"2023-07-31T15:19:35","slug":"enumerating-user-sessions-generate-filter-pools","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/enumerating-user-sessions-generate-filter-pools\/","title":{"rendered":"Enumerating user sessions to generate filter pools failed Error in Windows 10"},"content":{"rendered":"

After you install a Windows 10 feature update, the event viewer may contain Microsoft-Windows-Search Event ID 3104 Gatherer entries showing the error Enumerating user sessions to generate filter pools failed. Details: (HRESULT : 0x80040210) (0x80040210)<\/strong>. Here is what the event looks like:<\/p>\n

Log Name:      Application\nSource:        Microsoft-Windows-Search\nDate:          \nEvent ID:      3104\nTask Category: Gatherer\nLevel:         Error\nKeywords:      Classic\nUser:          N\/A\nComputer:      W10-PC\nDescription:\nEnumerating user sessions to generate filter pools failed.\n\nDetails:\n (HRESULT : 0x80040210) (0x80040210)\n\nEvent Xml:\n- <Eventxmlns=\"http:\/\/schemas.microsoft.com\/win\/2004\/08\/events\/event\">\n- <System>\n  <Provider Name=\"Microsoft-Windows-Search\"Guid=\"{CA4E628D-8567-4896-AB6B-835B221F373F}\"EventSourceName=\"Windows Search Service\" \/>\n  <EventID Qualifiers=\"49152\">3104<\/EventID>\n  <Version>0<\/Version>\n  <Level>2<\/Level>\n  <Task>3<\/Task>\n  <Opcode>0<\/Opcode>\n  <Keywords>0x80000000000000<\/Keywords>\n  <TimeCreated SystemTime= \/>\n  <EventRecordID>20540<\/EventRecordID>\n  <Correlation \/>\n  <Execution ProcessID=\"0\"ThreadID=\"0\" \/>\n  <Channel>Application<\/Channel>\n  <Computer>W10-PC<\/Computer>\n  <Security \/>\n  <\/System>\n- <EventData>\n  <Data>Details: (HRESULT : 0x80040210) (0x80040210)<\/Data>\n  <\/EventData>\n  <\/Event>\n<\/pre>\n
This error may be followed by Event ID 1015<\/code>, containing an error something like this:<\/p>\n
Windows Search Service has been suppressed 10259 time(s) since 1:16:14 PM. This event is used to suppress Windows Search Service events that have occurred frequently within a short period of time. See Event ID 3104 for further details on this event.<\/div>\n
[Fix] Enumerating user sessions to generate filter pools failed Error in Windows 10<\/h2>\n
Microsoft documentation<\/a> suggests rebuilding the Windows search index to fix Event ID 3014 error Enumerating user sessions to generate filter pools failed<\/strong>. There are other solutions as well which we’ll see one by one below, starting off with a potential fix.<\/p>\n
Reset & Rebuild Search Index Completely<\/h3>\n
Simply opening Indexing Options applet in the Control panel and clicking on the Rebuild<\/strong> button may not help. You’ll need to set the SetupCompletedSuccessfully<\/strong> registry value to 0<\/code> in the registry key HKLM\\Software\\Microsoft\\Windows Search<\/code>. This removes additional folders from the Included Locations. You’ll need to add them back to Indexed Locations. Then, perform a rebuild of the Windows Search index.<\/p>\n
\"Enumerating<\/p>\n
\"tipsThis procedure is explained in detail in our article Reset and Rebuild Search Index Completely in Windows<\/a>. Follow the steps under How to Manually Reset Windows Search and Rebuild the Index<\/strong> and then run the Search troubleshooter<\/a> as explained in Method 1 in that article.<\/p>\n
\"Enumerating<\/p>\n
Many users have indicated that resetting and rebuilding search helped them eliminate obsolete & non-indexable folder locations, including the defaultuser0 profile folder. This in turn has fixed the Enumerating user sessions to generate filter pools failed<\/strong> Search error in the Event Viewer.<\/p>\n
\n
Make sure Windows Search service is running<\/h3>\n
    \n
  1. Start the Services MMC by running services.msc from the Run dialog<\/li>\n
  2. Double-click Windows Search<\/strong> from the list<\/li>\n
  3. Make sure that the startup type is Automatic (Delayed Start)<\/strong> and the service is Running<\/li>\n<\/ol>\n
    \n
    Modify DCOM Permissions to allow SYSTEM account<\/h3>\n
    Here is another major fix that we haven’t had a chance to test it out on our systems:<\/p>\n
    A Windows 10 user named “pchesels” said:<\/p>\n
    The fix for me on this was to add the SYSTEM account to the DCOM Security. Go to Component Services, computers, my computer, right click, and Properties, go to COM security, in access permissions AND Launch Activation Permissions Edit the limits<\/strong> and Edit the Defaults<\/strong> and ensure the SYSTEM<\/strong> account is added and given all rights locally and remote.<\/em><\/p>\n
    All my errors like this went away afterward.<\/p>\n
    Editor’s note:<\/strong> Note that by default the SYSTEM<\/strong> user isn’t listed in the Edit the Limits<\/strong> permission entries in Component Services. Adding SYSTEM to the list may fix the error, but it could have other security implications.<\/p>\n
    \n
    Acronis True Image software<\/h3>\n
    If you’re using Acronis True Image software, the two services<\/a> may be causing the Event ID 3014 Search error.<\/p>\n