Windows 10 V1607: Update KB4467684 kills Outlook search in Terminal Server

[German]End of November 2018 Microsoft released the update KB4467684 for Windows 10 V1607. Since then, there are more and more reports that this update killed the search in Outlook via Terminal Server.

Update KB4467684 for Windows 10 V1607

Update KB4467684 has been released for Windows 10 V1607 on November 27, 2018. Since this version dropped out of mainstream support on April 10, 2018, only Windows 10 Enterprise and Education systems received the update. The same applies to the LTSC version of Windows 10 V1607. I've mentioned that within my blog post Patchday Windows 10-Updates (November 27, 2018).

With this update, Microsoft has rolled out numerous fixes for Windows 10 V1607, but has not closed any security gaps. The KB article mentions several known problems with the .NET framework, a hiccup when using end-user-defined characters (EUDC) in Windows functions, or a broken search in Windows Media Player.

Issues with Outlook search via Terminal Server

I received two comments from German readers after I posted the article Patchday Windows 10-Updates (November 27, 2018). Both comments indicate a broken Outlook search via Terminal Server after installing update KB4467684. User @Seb asks:

Is anyone having trouble finding Outlook after installing KB4467684 on a 2016 TS server? After confirming the search entry, nothing happens at all.

In a second comment, user Seb confirmed that the error has disappeared after uninstalling update KB4467684. This issue is not listed in this Microsoft document on known Outlook issues. The issue has been confirmed in a follow-up comment by user @MaBa:

We have exactly the same problem in several TS farms. As soon as the patch is uninstalled, the search works fine again. For installations with Outlook 64-bit we could not detect the problem.

In both cases, the error refers to Terminal Server and Outlook. User @Seb then refers to this entry in the Spaceworks community, where the bug for Outlook 2010 is discussed in conjunction with Terminal Server 2016.

Wondering if anyone can help. Immediately after a month's worth of Windows Updates (all of Novembers) Outlook's search is stuck on searching and no results ever come up.

My company uses Windows Terminal Server 2016 with Office 2010. Never had this problem until after the update.

Also, I can't find System restore as I figured this would work. Does that exist in the terminal server?

It does let me delete the updates but there are so many I dont know which one.

This happens for every user, regardless if using cached exchange mode, or data online.

I already tried rebuilding the index and the Microsoft Recovery Tool. The searching did work when run in safe mode.

Any help would be greatly appreciated!

There, too, several users confirm this problem in connection with a terminal server. Repairing Outlook or similar approaches do not help – one solution is to uninstall Update KB4467684.

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search]
"PreventIndexingOutlook"=dword:00000001

A second solution suggested to fix the problem is to disable indexing in Outlook. This should be possible with the above reg file, which is to be imported with administrative privileges.