Replies

Hello everyone

As per my earlier Tweet with Woody, we saw this earlier today in the office with 1903 users.  I’ve implemented a GPO to add

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search
DWORD BingSearchEnabled = 0

Prior to applying the GPO on my own 1903 PC, search worked normally. I performed a gpupdate /force believing the new GPO to be applied and got the blank search fly-out.  Killed SearchUI.exe, which was found to be in a suspended state and still the same. But the registry showed the GPO was not applied through a mistake of our making.

Odd then that the gpupdate instigated the fault even though the 365 back-end is the root cause.

Applying the registry entry above correctly and kicking SearchUI.exe resolved it for us.

Cheers

 

-Neil-

2 users thanked author for this post.

rc primak, woody

Starting working again for us sometime between 0700 to 1900 (UTC) on 10th September. All synchronisations since then have been successful.

Hi

First post and un-lurking.

Reviewing the June updates today via AskWoody, I see on the referred ghacks post a need for a May servicing stack update (SSU).  Which made me think, yup, probably not yet deployed within my WSUS server.  I take the cautious route for only releasing security, rather than functional, updates so SSUs are classified within the “Updates” class.

I think Susan must have been thinking about this recently because via a search, this pretty much came within the first few results:

https://partnersupport.microsoft.com/en-us/par_clientsol/forum/par_win/question-about-servicing-stack-updates/48fbc36e-625f-45a6-9c21-840a0a6cb061

Seemingly didn’t get very far?  If only WSUS had a regex filter…

I’ll just add a +me too because missing these SSUs is annoying and means you have to keep reading resources like here (thanks Team Woody) like a hawk.

1 user thanked author for this post.

Elly