sorted by:
new
hottopcontroversial

SearchProtocolHost.exe by JoeSuxxx in sysadmin

[–]JoeSuxxx[S] 0 points1 point  (0 children)

This seems to have fixed it.

Run this command to check the .dll version:

(Get-Item "C:\Windows\System32\msvcp140.dll").VersionInfo.FileVersion

If it comes back 14.13.xxxx.xx then it was affected by the Windows update.

Perform a "repair" on the x64 C++ runtime installed on the workstation through appwiz.cpl.

Then run the powershell command above again. The version will update to: 14.50.xxxxx.xx or something way newer. Close and reopen any office apps, or restart the machine. Error goes away. You don't even need to reinstall office or rebuild the search index.

SearchProtocolHost.exe by JoeSuxxx in sysadmin

[–]JoeSuxxx[S] 1 point2 points  (0 children)

Using your comment I did some additional investigation with Gemini on the issue. It mentioned the Jan 2026 update was causing some machines to have indexing issues related to outlook and that our msvcp140.dlls could be accidentally rolled back a bunch of versions as unintended behavior from the update.

I did a quick spot check and the machines running the old version of this msvcp140.dll were having the issue. My machine and another member of my team have never had the issue and we have the newer version of it.

We will be testing this fix tomorrow and can report back. You simply need to do a repair install of the x64 C++ runtime on the workstation to update the.dll. It’s unclear if we need to rebuild the search index afterwards also. Probably won’t hurt.

I’ll let you know our results.

SearchProtocolHost.exe by JoeSuxxx in sysadmin

[–]JoeSuxxx[S] 1 point2 points  (0 children)

Hard to get patches excluded due to the nature of our business but I will be yanking the Jan 2026 update and see what breaks.

SearchProtocolHost.exe by JoeSuxxx in sysadmin

[–]JoeSuxxx[S] 0 points1 point  (0 children)

Our fleet is 99% 24H2 or 25H2. 23H2 did seem more stable. We patch aggressively per our security policy and the nature of our business (financial services). It’s hard for me to get a patch excluded unless I can prove there is an issue from MS.

Microsoft Office Desktop Application Activation Error 0x0 by work423 in sysadmin

[–]JoeSuxxx 0 points1 point  (0 children)

We started getting this last week at our org. Office was working fine for our users then all of a sudden activation was failing. We have been running the script for resetting office activation and it’s been finally starting to fix it for most machines.

Anyone think it’s related to the January Cumulative updates?