<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - LibO 6: Windows 10 content indexing does not work" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130320#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - LibO 6: Windows 10 content indexing does not work" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130320">bug 130320</a> from <a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> V Stuart Foote</a> <pre>(In reply to Michail Pappas from <a href="show_bug.cgi?id=130320#c11">comment #11</a>) > BTW, I don't have office installed at either work or home. Maybe. But if the still needed F3 search turns up the odffilter.dll string, or the GUIDs listed in <a href="show_bug.cgi?id=130320#c4">Comment 4</a> show up registered, some application (other than a full MS Office install) laid them down. Rather than MS Office components, better to think of these as IFilter add-ons to the Windows shell to expose file metadata & properties, search indexing, and file thumbnails for use in the Windows explorer GUI, and supporting indexed search. Have an issue should the MS provided odffilter IFilter interfere with our LibreOffice provided ooofilter IFilter module.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>