Hi all,

after recently experiencing trouble (i.e. encountering the message in the title) with the search function in all contact folders, incl. shared contacts of other users, I did some digging and found out that recent patch KB2956128 seemed to mess with people's configurations. I proceeded to get rid of it and the search function was restored.

Forward to today, a new batch of updates has been installed and the search function is broken again - but not for everyone. Interestingly enough, KB2956128 is back on one machine with all the newer updates and the search still works, but it's stopped working on another machine which only has the newer/last night's updates on it.

Any ideas how I can proceed? People are working right now so I only have very limited access. Plus I'm merely what I'd consider rather tech-literate, and not actually the administrator.

UPDATE: I removed an update that was installed twice (KB2956206) on the other machine and that seems to have fixed the search function again. I fear that by tomorrow it'll be broken again though and I can't just keep deleting updates.

Thanks for your time

Hi,

Glad to hear you have found the cause and resolved it. Currently we have realized the issues caused by KB2956128, once there is any update, we will let our users know as soon as possible.

By the way, I haven't known there is a KB2956206, would you please confirm this again?

Regards,

Melon Chen
TechNet Community Su

We were experiencing the same issue with KB2956128.  I pulled it from WSUS and searching of shared folders was corrected.  This month another patch is causing the same issue KB2956203 (that may be what the post creator meant to type).  I can confirm this is occurring with other companies.  After uninstalling KB2956203, the issue corrected itself.

After uninstalling KB2956203, Windows update (from WSUS) said there was another update, KB2956128.  This was a removal of that update per WSUS.  I'm wondering if the guts of KB2956128 were part of KB2956203?

We were experiencing the same issue with KB2956128.  I pulled it from WSUS and searching of shared folders was corrected.  This month another patch is causing the same issue KB2956203 (that may be what the post creator meant to type).  I can confirm this is occurring with other companies.  After uninstalling KB2956203, the issue corrected itself.

After uninstalling KB2956203, Windows update (from WSUS) said there was another update, KB2956128.  This was a removal of that update per WSUS.  I'm wondering if the guts of KB2956128 were part of KB2956203?

I can confirm the above.  KB2956203 creates the same shared folder search problem as KB2956128.  Removing the update does indeed restore search functionality.

Apologies, I was indeed referring to KB2956203 as was pointed out by the other posters. I found another machine that had it installed and removing it from there also solved the search problem, so both that and KB2956128 seem to be problematic.

Hi,

Thank you for your reporting. We have noticed this, and would like to collect more information for further investigation.

Can you guys share your detailed system info? Also, if you have any log files about the issue, kindly share with us by sending them to this email account: ibsofc@microsoft.com (please use the link of this thread as the subject).

We appreciate your assistance with this.

Regards,

Melon Chen
TechNet Community Su

The KB article for KB2956203 (March 10, 2015 update for Outlook 2010) currently lists that it was superseded by March 26, 2015 update for Outlook 2010 (KB2965290).  That said, KB2965290 is apparently not available or referenced in SCCM or WSUS (even to import via Microsoft Catalog) yet.  You might try downloading it and manually installing it to see if it corrects your issue.  If it does, hopefully Microsoft will include it in the April patch Tuesday (if not sooner).

The KB article for KB2956203 (March 10, 2015 update for Outlook 2010) currently lists that it was superseded by March 26, 2015 update for Outlook 2010 (KB2965290).  That said, KB2965290 is apparently not available or referenced in SCCM or WSUS (even to import via Microsoft Catalog) yet.  You might try downloading it and manually installing it to see if it corrects your issue.  If it does, hopefully Microsoft will include it in the April patch Tuesday (if not sooner).

Nevermind.  KB2965290 does not address the issue.