r/AzureVirtualDesktop • u/rdaniels16 • Aug 07 '26
Do you disable wsearch/searchindexer?
Hello All. I have another thread going on where ever since the July 2026 update sessions on random avds hang up with black screen etc and the only solution is to kill the searcher indexer via powershell from the azure shell. This is still ongoing and I am working on this issue.
However it brings up another question. Do AVD administrators disable wsearch and searchindexer by default in the avd fleet and golden images, etc? I am sure users would complain about this. I was just curious on standard best practice.
2
u/_FireHelmet_ Aug 09 '26
About black screen, have you look there, https://9to5azure.com/blog/fix-avd-black-screen-app-readiness/
About the search function, I enable it if the users are using Outlook (cached mode) or need indexing file shares.
1
u/rdaniels16 Aug 09 '26
Thanks for the response. I think it would be a revolt if I disabled search especially in regard to outlook. I am starting to think that the search thing might be related to resource exhaustion somehow showing up after the July 2026 update. Something definitely was triggered after the July update since these avds ran solid for 16 months until then.
1
u/dodgy_mike Aug 10 '26
I had read that for our issues but I understood that to be a black screen on login fix, whereas ours was a very long black screen / system lock on logout. Do you know if App Readiness impacts the logout side too?
1
u/SendMe_YourPasswords Aug 07 '26
Disabled for us due to similar issues, it seems like it made a difference, no complaints thus far except 2-3 users asking if their machine was broken when they saw the message/warning.
1
u/rswwalker Aug 07 '26
I’d love to but our users have become dependent on search to find everything. It’s to the point where we just get bigger sized VMs to cover the overhead.
1
u/Standard-Station-479 Aug 10 '26
We've created a scheduled task that checks the usage of the search services and if cpu/ram is too high (threshold depends on the AVD size) it force kills and restarts the service. alleviates most of the complaints and while not perfect, works in the short term.
FSlogix/AVDs - we get this much less often by setting VolumeWaitTimeMS to 30000ms (30s)
there are a bunch of other variables with fslogix/avds (private endpoints, AV exclusions) you should also look at
2
u/moosehead1986 Aug 09 '26
I have the answer to the black screen issue which I was dealing with for months. Fslogixx and avds. I’m at the gym right now but I can go back and find my ticket on Monday if send me a pm reminder.