This message was deleted.

@Matthias Schlimm ⬆️

BIS-f does nothing on any Services, expect cortana. The same issue is reported some month in the bis-f slack channel too. I will copy the content to here as follows -snip- Just to update - i can unfortunately repeat this issue. I take a known-good image (just built actually so fresh), verify Search is working, run BISF and reboot, Search is broken. I then fix search, verify all is working, then re-seal with BISF, reboot, and Search is broken again. I 'fix' search by setting HKLM\Software\Microsoft\Windows Search\SetupCompletedSuccessfully = 0 which makes Windows clear out the old and create new index. This seems to reliably fix it. We do have some basic Search GPO settings relating to FSLogix search roaming, but again, never any issues until running BISF. Any thoughts welcome. I appreciate BISF may not itself be doing anything to the Search service, or the index database files\folders etc., but it seems to have some involvement somewhere. For now, after BISF sealing i will stop Windows Search service, set the regkey above and shutdown quickly! -snap-

Do you use any optimizer? VDA has one and/or Citrix Optimizer? Both disable Windows search by default. Or is it getting disabled after a while? I remember this issue once at a customer, let me think about it...

So does PVS as well

We don’t use VDA/PVS optimizer anymore. Only Citrix Optimizer with a custom template (controlled by BIS-F) that doesn’t disable search service. We don’t see this issue in our customer environments 🤔

Citrix Optimizer does not disable search by default (it's an optional entry that is disabled by default)

Sorry! You're right. We just took the option out of the template to make sure nobody accidentally activates it.

Thanks for all the help and advice. I'll give this reg key a try. I've since tried to rebuild the index and noticed entries in the event log about a corrupt in the search database. Shortly after this the service seems to be disabled so I think it might be related. Thanks everyone for your help!

@Dennis you are rIght , the PVS Target OS Optimizer is triggered from BIS-F and this uses the default configuration mostly and disable the search service. With next 1912 release the PVS target is optimizer is skipped from BIS-F m, but not yet.

Yea I'm see this, but I'm 100% what is doing it.

The BIS-F logfile might be help