Outlook 365 search not working in pst windows 10#
Outlook 365 search not working in pst windows#

If the issue still continues, since we mainly focus on general issues about Outlook desktop client in normal environment and know little about FSLogix.

Outlook 365 search not working in pst windows#

So, in order to eliminate the influence of these factors, it is suggested to create and use a new windows profile in your RDS environment after updating and see if the issue has any difference. When you are in Outlook and look at indexing status it never loads.ДЄs I know, Outlook search feature is mainly based on local windows search and many factors from your windows settings or registry value might cause issues like yours. We've got the search service set to automatically restart if it fails.

I did some more search about your issue but could not found more related information. Sorry to hear that those information above could not help solve your issue. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

If an Answer is helpful, please click 'Accept Answer' and upvote it.

Outlook 365 search not working in pst windows 10#

FSLogix search functionality is not compatible with Server 2019, Windows 10 multi-session, and subsequent multi-session operating systems with enhanced native search capabilities. Please check if they could be helpful to your issue:Д¬onfigure Profile Container to roam the Windows Search databaseД«esides, you might need to first check the capabilities of your environment, just as the official document mentioned:Д¬hanges to enhance native search behavior in Windows Server 2019 and Windows 10 multi-session remove the need for FSLogix search functionality. I did some search about your issue and found a Troubleshooting Guide related to similar issues as yours in FSLogix forum. Hi going further, please make sure you have upgraded your FSLogix and Outlook to the latest version.ДЄccording to your description, seems that your issue might be more related to the specific FSLogix environment and I'm afraid that Troubleshooting methods used in windows environment might not help much.