Yet another Windows 10 fail as new update breaks the internet - here’s how to fix it

[Karlston]

Yet another Windows 10 fail as new update breaks the internet - here’s how to fix it

Sound issues have also been reported

(Image credit: Shutterstock)

 

Windows 10’s string of broken updates has now gone well beyond a joke - as it seems that the latest update to be released by Microsoft has been causing network and sound issues for some users.

 

Microsoft has recently released Windows 10 KB4532695, an update for Windows 10 that was supposed to fix problems with Windows 10’s search function, and after only a few days it emerged that rather than fixing problems, it had caused some serious issues, including boot failures.

 

It’s now become apparent that the Windows 10 KB4532695 update has also introduced other serious problems, with Windows Latest reporting that users are complaining that as soon as they’ve installed the update, the sound stops working on their PC.

 

According to Windows Latest, one user on Microsoft’s community forum complained that “I installed the update Saturday afternoon and immediately the sound stopped working,” with Windows 10 now not recognising their speakers.

 

Not only is that incredibly annoying, but, rather worryingly, it seems the problem didn’t go away once the user uninstalled the update - and it even persisted after they performed a full reinstall of Windows 10.

Connectivity woes

Another incredibly frustrating problem with the latest Windows 10 Update has also emerged, with users complaining that their network connectivity has been impacted - meaning they cannot connect to the internet.

 

The issue seems to be impacting bother wired Ethernet connections, as well as Wi-Fi connections, and is affecting network adapters from a range of manufacturers.

 

While some people aren’t able to connect to the internet at all, others are reporting that they can still connect to the web, but their internet speeds are severely limited.

 

Using Windows 10’s built-in network troubleshooter doesn’t fix the issue - the only option is to uninstall the updated.

How to fix Windows 10’s network issues

If you’ve encountered network problems after installing the latest WIndows 10 update, then this is how to fix those network issues.

 

Open up the Settings app (click the Start menu and then the cog icon), then click ‘Update & Security’. 

 

From the window that appears, click ‘View update history’, then ‘Uninstall updates’ and select ‘KB4532695’.

 

Hopefully this will sort the issue for you until Microsoft releases yet another update to fix the problems its last update introduced. Microsoft seriously needs to make sure that the next update solves these problems without adding new ones – otherwise it might find its reputation suffers even more. 

 

 

Source: Yet another Windows 10 fail as new update breaks the internet - here’s how to fix it (TechRadar)

[steven36]

Bada Bing, bada bork: Windows 10 is not happy, and Microsoft's search engine has something to do with it

 

The week's triumvirate of TITSUP* is complete

 

 

Updated Microsoft doesn't do things by halves. Not content with Teams taking the day off and Outlook labeling everything as spam, now Windows 10 Search has joined the cock-up club.

 

The problem manifests itself by flinging up a large black box where search results should be on the Windows 10 desktop. Multiple flavours of Windows 10 are affected, and PCs at Vulture Central have also suddenly caught the search sickness.

 

We're guessing queries are piped to Bing, which isn't responding for some reason, causing all results to not show up on desktops. In which case, we have to wonder, why is it necessary for Windows 10 to send local queries to Microsoft's backend, and why is it programmed in such a way that network failures blow away all results, including local ones?

 

 

As is par for the course, social media is awash with anguish as people hopefully type characters into the search box and are rewarded with... nothing. A thread on Reddit contains a partial solution to the problem, courtesy of the HowToGeek team, which involves disabling Bing in the search screen. The fix involves fiddling with the registry, and as such we'd advise caution. It's a shame that the setting to disable Bing isn't surfaced somewhere a little more convenient. Hmm.

 

The Start Menu itself appears unaffected. However, if, like us, you use the search box to get to apps – because life is too short to wade through a maze of menus – this outage is doubly maddening. Even typing the name of a known app, such as notepad.exe, and hitting return does nothing. Sad.

 

A Register reader with the problem grumbled to your sympathetic vultures that he "had dozens of reports" before muttering: "Something with their wonderful Bing integration has broken even local searching!"

 

Do we detect a note of sarcasm there? "Another fun day of Microsoft pushing their Bing product and ruining everyone's day."

 

Don't mince your words. However, a bit of server-side sickness managing to stop the local desktop search working is a bit worrying. Searching through File Explorer was still

functioning in our testing, but isn't quite the same. The Register contacted Microsoft and was told that the born-again cloud flinger was aware of the issue and an explanation would be forthcoming. We'll update this article when it arrives.

Updated to add

The Windows giant claims it has now fixed the problem, which affected Windows 10 Search and a bunch of Microsoft 365 services for customers, by rerouting network traffic. This ensured queries were finally answered:

We rerouted user connections and validated that impact associated with MO203172 has been remediated. Additional details can be found within the admin center.

— Microsoft 365 Status (@MSFT365Status) February 5, 2020

Incredibly, it seems Windows 10 Search and other services were knocked offline by infrastructure falling over, preventing all search results, even local ones, from showing up on desktops. Yes, it's that stupid. Microsoft suggested the problem was limited to Europe, though we've heard from folks in America who were affected, too.

 

In a note to customers, Microsoft blamed a "third-party networking fiber provider," that "experienced a network disruption resulting in impact," adding: "We're reviewing our network redundancy options to find ways to prevent this problem from happening again."

 

You will need to reboot your PC once, twice, or thrice to pick up the connectivity changes, if you were affected by today's outage.

 

* Total Inability To Search User Profiles

 

Source

[voman]

Yesterday night my Windows 10 search was affected but it was quite late so I shut down my computer and went to bed. Today everything's fine again. As I'm in Brazil to failure was not restricted to Europe.

[steven36]

4 hours ago, Kalju said:

Do not fall victim to malicious propaganda.

 Easy to say after the fact  that Microsoft deployed a fix for  it. Why are you trolling  members here that had a problems with windows  search  like many did yesterday because it depends on the internet to  use it fully ?   

 

Even  Mary Jo Foley had this issue how ignorant can one be i wonder?

https://www.zdnet.com/article/windows-10-users-encountering-problems-with-built-in-search/

 

When  Microsoft  admitted to it  that means only one  here  that is spreading propaganda. is you witch is nothing new because you spread false info all the time that Windows 10 dont have bugs i seen you in a other post here just this week were you you doing it! I ignored that post  because Microsoft didn't acknowledge that bug like  they did this one because it was internet related they didn't have too because the update was optional  you can just uninstall the update if you had problems   .

 

 

 

But going back to what you said the other day about Windows  BSOD  ,fact is it dont matter  if it driver related if it was working before they apply a update  and driver dont work after the update and causes you to BSOD  or other problems  Microsoft  is the one at fault  because  the update was not tested     . they should of  gave you a driver update too so it would not cause problems. they shouldn't have to have reinstall  windows  just fix it like some did. But if it optional and it breaks Windows 10 and your crazy enough to keep seeking updates that end user error.  I even had it happen on windows 8.1 before after i done a update and after i clean installed windows it was gone  that what i love about Linux we dont have BSOD  on it . That one  thing really sucks about Windows  and updates is the fact some  old hardware the drivers not updated since TH2   . I have  a gateway PC  like that here a Gateway that came with Windows 8 only thing you can do to get driver updates is use Linux or  buy new hardware or just use it with Windows with Old drivers  and hope for  the best . besides using old drivers  is bad  security  there known exploits in them.

 

Microsoft never thought about all these problems  when they  gave away windows 10 free upgrade and drivers have been a big problem with Windows 10 since June 2015  and here it is  4 and half years latter and people are still having issues . If everyone bought new hardware with windows 10 they would not be as many issues with drivers and if they was you can get a driver update and fix it.  I even had BSOD  before even on XP  .Sometimes its a  driver that causes  and sometimes it some software   that  causes it .  If you cant figure out what is causing it the only thing that will really fix it is reformat . Microsoft need to get better native  drivers  like Linux  has  that would fix  most issues  with drivers  .The problem  is  the old closed source drivers  are not really compatible with Windows 10  and people are using  windows 10  for hardware that came with Windows Vista  , Windows 7 and  windows 8/8.1 so it will always be  driver problems because of it . Sometimes they even blacklist upgrades because of drivers what happens if you dont have a driver update i guess Microsoft would have to provide it or you be stuck on a old version of Windows 10  tell you bought new hardware.

 

They trying to support way to much hardware  with no good native driver support  0x0000009F (DRIVER POWER STATE FAILURE) its like on my Gateway  if i dont  use the  old 3rd party driver the one that comes with windows dont have hardware acceleration.    The native stuff that comes with windows so far is crap  and updates and upgrades break the old 3rd party drivers sometimes. Cleaning the registry like you sugesst  it not going to help if you use some snake oil registry cleaner that delete stuff it shouldn't  . And  if you  go in the registry and try to do it yourself  and dont what your doing  and most people dont you may do more harm than good have to reinstall  anyway. Here it is 2020 and people still installing snake oil to fix windows , people never learn . If  your image is messed up it not going  to help  only thing will help is a  clean image  and if it too slow only thing that going to make it faster is buy better hardware or use a OS that not  so bloated that have been tested to run faster than windows 10 on low end hardware.

 

The more they update Windows 10 the less compatible its going to become with old hardware. Same thing happen with Mac OS  upgrades in the  past  it became too much for old hardware  and same thing  happen when they made Windows Vista  . So if your on old hardware on windows 10 your just on borrowed  time. Already for Windows 10 to run  good  you need at lest 8 gb of ram while on Linux you can use 4 gb and it run good some people only use only 2 gb. And they still sell PCs with 4GB of ram with windows 10 lol.

 

Best thing users  could do for windows search is 1. disable Cortana  2. install Open-Shell-Menu and use its search instead , 3.Also Everything is a good for search tool on Windows , those is what i use on Windows 8.1 . M$ cloud . windows 10 is turning into Chrome OS when you need internet to search local .

 

Quote

For the past several years, Microsoft been working to unify and personalize its search experience across Office 365, Windows and Bing.

 

https://www.zdnet.com/article/microsoft-to-update-sharepoint-with-deeper-personalized-search/

 

That Outage is a sign of things to come when  Windows 10 becomes windows 365 ! They say they going to fix it but they been having outages on Skype for years so good luck that it stays fixed.

 

[Screen]

So that's why my network has been acting weird with random disconnections. Well will get fixed sooner i guess. 

[steven36]

News Analysis Win10 Search blackout due to 'fiber provider' glitch? Pull the other one, Microsoft.

 

By Woody Leonhard, for Woody on Windows @ Computerworld

 

 

 

Microsoft blamed the widespread Win10 Search blackout we experienced yesterday on a 'third-party networking fiber provider that experienced a network interruption.' Hogwash. Somebody at Microsoft is beta-testing buggy software on our production machines.

 

If you believe that yesterday’s worldwide crash of Windows 10 Search was caused by a bad third-party fiber provider, I have a bridge to sell you.

 

Microsoft’s transparency in the Search black box fiasco has earned it a “five nose Pinnochio” veracity rating from Patch Lady Susan Bradley. That’s as bad as it gets.

Microsoft wants you to believe that:

 

... a temporary server-side issue caus[ed] Windows search to show a blank box. This issue has been resolved for most users and in some cases, you might need to restart your device. We are working diligently to fully resolve the issue and will provide an update once resolved. 

Clearly, that’s only part of the story. Here’s what we know for sure.

 

Windows 10 Search works even if you aren’t connected to the internet. Go ahead. Unplug your computer. See?

 

Bing was only tangentially involved. Many people found that they could get their Search boxes back by modifying the registry to disable Bing Search — the “feature” in Windows 10 that routes all of your Search bar searches through Microsoft’s data-gathering servers. But a large number found that zapping Bing Search didn’t bring back the Search box.

 

 

There were no official patches associated with the outage. None went out yesterday morning.

 

There were no Microsoft Store updates associated with the outage. Lots of searching by lots of people has turned up exactly zero evidence of changes to any Store apps leading to the chaos.

 

 

So if there were no bad patches, and Win10 Search doesn’t require an internet connection, what’s going on? 

 

Consider:

 

Microsoft has been monkeying around with Search builds. What started as a snipe hunt for changing default Search text (thx, @howardagoldberg) turned into the discovery of an explosion of rapidly changing Search build numbers — 2020.02.01.6237928, 2020.02.02.6237943, many more. My main machine’s up to 2020.02.04.6238073 early Thursday morning.

The Search app has changed from an old Win32 program that’s worked pretty well since Win7 days into a new JavaScript/React UWP POS (thx, @warrenrumak). I’ve been expecting that shift since we started having problems with File Explorer Search in Win10 version 1909 months ago. I didn’t expect to see a retroactive change in Win10 version 1903, but now it appears as if UWP-itis has infected both versions.

 

 

The intent, of course, is to give us a flashy new Search “experience” that shows today’s weather, news, today in history, and new movies (thx, @b) whenever you type in the Search box. What a great idea. Not.

 

That’s what we know for sure. Permit me to toss out a conjecture.

 

Microsoft appears to be updating Search — the Search that runs on your machine — by changing things on its servers. There’s no user notification about changes, no permission requested or granted to change the Search software. No Patch Tuesday. No KB article. No cumulative updates. Not even a Windows Store entry to block. No documentation. Nothing you can do about it.

 

As best I can tell, this has led to a merry round of beta (alpha?) testing, where Microsoft's test machines are our production machines.

 

Somehow, a bad version of Search made it into production on our machines that shows a black screen and disables the Search box entirely. When the folks at Microsoft finally figured that out, it took them about three hours to push out a new version. Remember, Search should work whether you’re connected to the internet or not. Yes, the bugs were on Microsoft’s servers — third-party fiber provider notwithstanding. But they were also on our machines.

 

Short version: Somebody at Microsoft is beta-testing buggy JavaScript code on our machines. Without warning. And there’s nothing we can do about it.

 

There’s a further conjecture: Is it possible that responsibility for the Search software was pulled out of the Windows Experience team and placed in the Windows Core team?

 

Remember, those two groups report to entirely different masters — Joe Belfiore for Experience, Scott Guthrie for Core. Belfiore is headed out for another months-long cruise with his family, with Panos Panay picking up the baton. I have no idea what @ScottGu is doing right now. He’s been uncharacteristically silent for many months. Perhaps he fell off his bicycle.

 

It’s time somebody at Microsoft stepped up to the microphone and told Bradley’s Pinocchio what’s really happening.

More on AskWoody.com.

 

 

 

Source

[Michael*]

Is this issue fixed in 19559.1000.200131-1437?

[dhjohns]

What I find strange is that some people have issues upon issues while I have none.  Could it be PEBKAC?