<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - LibO 6: Windows 10 content indexing does not work" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130320#c30">Comment # 30</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - 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:nachodelosrios@gmail.com" title="Lobotomik <nachodelosrios@gmail.com>"> Lobotomik</a> <pre>I've been suffering the same for a long time. * Windows 10 Home 1909 64-bit, running at home. * LibreOffice 6.4.4.2 as of today, but it happened just the same with previous versions. * In Advanced indexing options, LibreOffice file extensions are associated with "OpenDocument Format Filter" for properties and contents. * I have a folder with some 50 .odt files I have created myself. These are the symptoms: * Contents of .pdf, .docx and many other file types are found in Windows 10 searches. * Contents of .odt files are not found in Windows 10 searches. * Rebuilding the index does not cure the issue. * If I save the file as .docx or .doc, matches in the new .docx or .doc file appear (but of course not in the .odt file). * If I rename the .odt file as .sxw, matches appear instantly in searches (with no change in format involved!). * Large icons in Windows File Explorer show a faithful image of the file contents. Search *has* worked in the past, but only occasionally, and not for long. I cannot tell when did it work, for how long, and which were the special conditions, if any, but I've seen it work a couple times without doing anything special (that I remember). I'm reasonably tech-savvy, but no Windows expert. With kind guidance I can look through regedit, browse logs if you tell me where they are, or run stuff on a console and report results. I'd be so happy if this was solved. It looks like a very small bug. I repeat I *have* seen it work in a system, and then again not work without any further changes I could tell.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>