Deactivation of Windows Search (mail.winsearch.enable) is not possible
Categories
(Thunderbird :: OS Integration, defect)
Tracking
(Not tracked)
People
(Reporter: dfghjkjhg, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [workaround: comment 14])
Comment 4•14 years ago
|
||
Comment 8•10 years ago
|
||
Comment 10•10 years ago
|
||
Comment 11•9 years ago
|
||
Comment 13•8 years ago
|
||
Comment 14•6 years ago
|
||
Hi,
I had the same issue in version 60.7.0 32 bits. I checked the "allow Windows to search" option and was unable to uncheck it (even through the mail.winsearch.enable which instantanely switches back to true).
I decided to turn of the "windows search" service (thanks to services.msc) but it turns on automatically. So I set this service to be disabled (not to automatically start). Then I can uncheck the Thunderbird option (it is grayed). I don't remember if I had to restart Thunderbird in the process. Once done, if you turn on the service again, the problem remains : on Thunderbird opening, it asks if it is the default application for emails etc. and if you allow windows to search. Even if you uncheck it, it activates this option !
ATB
Comment 15•3 years ago
|
||
RenArD, Robert,
Does this also happen with Windows 7? Or 10?
Comment 16•3 years ago
|
||
Windows 7 - I don't remember seeing it there. I no longer use Windows 7.
Windows 10 - I haven't seen it under Windows 10.
Updated•2 years ago
|
Comment 17•6 months ago
|
||
I know this is a very old issue, but i noticed that after turning off windows search in the settings, the following preference was still set in the config editor:
mail.winsearch.enable
= true
Updated•2 months ago
|
Comment 18•1 month ago
|
||
Since Wayne seems interested in this bug, let me make a comment here related to closed bug 1926337.
I think that originally this bug 553048 had a different cause, but the cause in Thunderbird 68 and later is as pointed out by Meichthys.
The "Allow Windows Search to search Messages" option in the Settings UI and "mail.winsearch.enable" in the Config Editor are not linked.
This is also the cause of bug 1664169.
Comment 19•1 month ago
|
||
Description
•