Yet another bug in Win10 1903: Upgrade may knock out certain WiFi cards

[Karlston]

Yet another bug in Win10 1903: Upgrade may knock out certain WiFi cards

Microsoft just announced that it’s putting a hold on upgrading machines to Win10 version 1903 for “some devices with Intel Centrino 6205/6235 and Broadcom 802.11ac Wi-Fi cards.”

 

Here’s the full announcement:

Safeguard on certain devices with some Intel and Broadcom Wi-Fi adapters

 

Microsoft and NEC have found incompatibility issues with Intel Centrino 6205/6235 and Broadcom 802.11ac Wi-Fi cards when running Windows 10, version 1903 on specific models of NEC devices. If these devices are updated to Windows 10, version 1903, they will no longer be able to use any Wi-Fi connections. The Wi-Fi driver may have a yellow exclamation point in device manager. The task tray icon for networking may show the icon for no internet and Network & Internet settings may not show any Wi-Fi networks.

 

To safeguard your update experience, we have applied a compatibility hold on the affected devices from being offered Windows 10, version 1903.

 

Affected platforms:

• Client: Windows 10, version 1903

 

Workaround: If you are using an affected device and you have already installed Windows 10, version 1903, you can mitigate the issue disabling then re-enabling the Wi-Fi adapter in Device Manager. You should now be able to use Wi-Fi until your next reboot.

 

Next steps: Microsoft and NEC are working on a resolution and will provide an update in an upcoming release.

 

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

I’m trying to remember when the “Update now” button appears. I know about “Download and install now,” but “Update now” doesn’t sound familiar.

 

 

 

Source: Yet another bug in Win10 1903: Upgrade may knock out certain WiFi cards (AskWoody - Woody Leonhard)

[Coleo]

I faced the problem after upgrading to 1903. Only solution reinstall the wifi driver from manufacturer. All is good now.

[zanderthunder]

https://old.reddit.com/r/Windows10/comments/d2apfk/cumulative_updates_september_10th_2019/ezxsex0/

 

According to this thread on Reddit, it seems that the latest cumulative update also screws up network drivers on some systems with MSI and Gigabyte motherboards.

 

Situation 1: 

Quote

 

KB4515384 broke my Intel NIC. It kept reporting 'disconnected'. I downloaded the Intel 24.0.0.11 drivers, and did a fresh install, but no luck...still disabled. I uninstalled the kb, and I'm back in business. I'm running Intel driver 12.18.8.22 successfully pre-update, if that helps anyone. Now, I sit and wait and hope MS fixes!

MSI Gaming Pro Carbon X370 onboard Intel I211 Gigabit NIC.

 

 

Situation 2:

Quote

Same thing happened to me. MSI Gaming X470 M7 AC with Killer E2500 ethernet. It also broke the Intel wifi.

 

Situation 3:

Quote

 

Same for me! I have the MSI B450 Gaming Pro Carbon AC. Also with an Intel I211 Gigabit NIC (and WIFI, which this update also breaks). The only fix is to uninstall this Windows update. Really frustrating, especially because I only understood the cause of the issue after doing a clean install of Windows.

EDIT: I have the latest drivers and firmware for Intel networking, chipset, and BIOS (and everything else).

Question: can anyone with an Intel i211 network adapter say if they do NOT have this problem?

 

 

Situation 4:

Quote

Ditto for me. Gigabyte GA-AX370-Gaming 7 with two NICs, Intel and Killer. Neither worked post update, same symptoms as others have had. Tried reinstalling drivers, no difference. Rolled back KB4515384 and all was well again.

 

The only option for them is to uninstall and block the update for now, as most reported that installing and reinstalling drivers also can't help much.

 

Seems Microsoft getting more bad lucks when it comes to updates tho. After the high CPU issue, orange tint issue and audio issue reported, Microsoft has to step up without any compromise and have these updates thoroughly tested. Don't wanna repeat the same mistake that Microsoft had done when 1809 (October 2018 Update) was released last year. Enough is enough.

[steven36]

Microsoft offers workarounds to even more bugs in the latest Windows 10 build

 

Lack of testing times

 

"Fixed it?" "No."

 

MICROSOFT SEEMS to be caught in another corporate boot loop of its own making as the list of problems facing users of the latest Windows 10 update continues to balloon.

 

Customers (and let's not forget, we are customers) have already had to deal with a CPU hogging issue caused by the separation of Cortana from the search functionality of the desktop.

 

A second patch was released to replace that faulty patch and for many people, it's completely borked their search functionality altogether. In some cases, it borked the start menu completely.

 

But this weekend has seen the list grow still further. Gamers are complaining that their in-game audio is all over the place because apparently, Windows isn't processing multi-channel audio correctly. The current workaround is to turn off multi-channel audio or surround sound, assuming your sound card allows it.

 

For some, Wifi is borked too - if you're running an NEC device with Intel Centrino 6205, Centrino 6235 or Broadcom 802.11ac wifi card. Microsoft suggests switching the network adapter off and on again every time you restart Windows. That's not annoying at all.

 

Plus, if you're using the Chinese IME editor, which means most of China, then you may find, again, that your CPU is going crazy as a result. Microsoft says you can fix this by turning the Touch Keyboard/Handwriting Panel to ‘manual' in services.

 

This has all happened in Build 1903, which was released earlier this year and was supposed to be tested to within an inch of its life before release to avoid the calamities affecting the previous Build 1809. Unfortunately, as Microsoft continues to add patches, it seems to be incapable of fixing one thing without breaking another.

 

Unfortunately, even though Redmond took extra time testing the original 1903 build, it is quite happy to throw update patches to the wall and see what sticks. Not cool Microsoft.

 

Source

 

[steven36]

Windows 10 Cortana 'fix' breaks the internet – and people aren't happy

 

 

Some PCs have reportedly had their networking functionality killed by the patch

 

Windows 10 has run into more trouble at the hands of the KB4515384 update, which is, by all accounts, breaking far more than it fixes, with the latest victim reportedly being networking functionality.

 

As we’ve already seen, this particular patch was designed to fix a problem with the May 2019 Update whereby Cortana and search were spiking CPU usage, a nasty gremlin, but while KB4515384 solved this, at the same time it broke search in both the Start menu and Taskbar.

 

Not only that, the update also caused sound issues (Microsoft notes that “audio in certain games is quieter or different than expected after installing this update”), and now it would appear, networking problems.

 

The latest gremlin has been highlighted by Windows Latest which cites reports on Reddit and Microsoft’s own Answers.com forum, as well as feedback submitted to Microsoft via the Windows 10 feedback hub.

 

One user submitted feedback to the effect that: “Cumulative update (KB4515384) causes the NIC [network interface card] to fail to enable with a code 10 error. Reinstalling network drivers from Intel or Windows Update sources does not resolve the issue.” However, uninstalling patch KB4515384 causes the problem to go away, the user observes.

 

Another user on Reddit notes: “KB4515384 broke my Intel NIC. It kept reporting ‘disconnected’. I downloaded the Intel 24.0.0.11 drivers, and did a fresh install, but no luck ... still disabled. I uninstalled the kb, and I’m back in business. I’m running Intel driver 12.18.8.22 successfully pre-update, if that helps anyone. Now, I sit and wait and hope MS fixes!”

 

Other users then chime in saying the same thing has happened to them, and as mentioned, there’s also a ‘network adapter failure’ thread on Answers.com.

 

This problem appears to be affecting Intel network hardware (both Ethernet or wired connections, and Wi-Fi), and has hit at least two different brands of motherboard, with MSI and Gigabyte boards being mentioned in the above posts.

 

Obviously these are pretty frustrating issues, and users can try disabling and then re-enabling the network adapter in Device Manager, followed by rebooting their machine, to see if that might shift the problem. But it seems the only guaranteed solution here is to simply ditch the offending patch KB4515384, which isn’t a great workaround, seeing as that leaves you with other problems of course.

 

The original Cortana driving up processor usage issue was itself introduced by a previous cumulative update (KB4512941) for Windows 10 May 2019 Update.

Patience wearing thin

This is all beginning to sound like a real mess, isn’t it? And to rub further salt in the wound, Windows Latest also highlights potential issues with Action Center failing to open after the installation of KB4515384.

 

It would certainly seem to be a patch that causes far more trouble than it resolves for some, and unsurprisingly on some of these threads online, folks are clearly losing patience with Microsoft.

 

One Reddit poster complains: “Correct me if I’m (significantly) wrong, but it seems like every single time they’ve pushed out a major update since Windows 10 was released, they’ve broken something stupidly simple & often generally essential for basic usage ... and even now, four years later, I still can’t install Windows 10 if I don’t unplug every non-essential peripheral in the system beforehand – even if the drivers for them are pre-installed in Windows itself!”

 

Elsewhere in that large Reddit thread, more flak is fired at Microsoft, including the following shot: “Don’t blame Windows, blame company culture where features get people promotions but not bug fixing and optimizations. Same thing happens at Google frequently.”

 

Hopefully we’ll get some acknowledgement from Microsoft about these fresh problems (and maybe an incoming cure) before long.

 

Source

[zanderthunder]

Seems like Microsoft fails to pay extra attention on bug fixing and optimizations section tho. Something needs to be done seriously to ensure botched update does not happen again in the future.

[steven36]

4 hours ago, Edward Raja said:

Seems like Microsoft fails to pay extra attention on bug fixing and optimizations section tho. Something needs to be done seriously to ensure botched update does not happen again in the future.

All the bugs started  up this time when they patched  DejaBlue Aug update  then they patched two remote code execution bugs in the Remote Desktop Protocol in Sept .  and spun off more bugs . Unless M$ hires  a new QA team what you say is never going to happen,  after they  laid them off in 2014 botched updates started appearing in Windows 7 and 8.1 as well . Windows 10 has been one big bug  fest since 1st released in June 2015  it's a never ending cycle of Problem Shooting .  The difference in 1903 and most other versions was most of the bugs  was in it when released from insiders  that were not found yet and   Microsoft patched them after released GA . 

 

Most of the bugs in 1903 is coming from post  GA release  security updates . It's not a insiders release  and  they  laid off there QA team in 2014 so the consumers are doing the beta testing of every update .What people dont get The QA titles have changed  now they call them "Customers" If you don't won't to beta test for business you need to buy a  Mac or use GNU Linux LTS witch is free . As long as  any version of  windows have updates they not testing them  . The only update testing that is going on is before it got released to consumers  (Insider releases .)   Once a version goes to Consumers  Home users that are not insiders are testing updates . Insiders are on a different version of Windows 10 with another list of bugs.

 

Why did Microsoft lay off 'Programmatic testers'?

https://www.linkedin.com/pulse/20140806183208-12100070-why-did-microsoft-lay-off-programmatic-testers

 

Microsoft Has A Software Quality Problem

https://www.thurrott.com/windows/windows-10/187407/microsoft-has-a-software-quality-problem

 

Blue Screen Stop 0x050 error reported for systems installing KB2976897, KB2982791, and KB2970228  Aug 14, 2014

https://www.infoworld.com/article/2608859/blue-screen-stop-0x050-error-reported-for-systems-installing-kb2976897--kb2982791-.html

 

Windows updates are at it again, reportedly hanging and slowing down systems April 13, 2019,

Windows 7 machines seem to be the most vulnerable

https://www.techspot.com/news/79639-windows-updates-again-reportedly-hanging-slowing-down-systems.html

 

 

[Karlston]

Wait, there's maybe more...

Yet another bug with this months Win10 1903 cumulative update: PIN knockout

I don’t know how widespread this is, but @gpmartens1 reports:

Applied the KB 4515384 Cumulative Update to 4 machines using Win 10 1903.  On 3 of the 4 machines, it made Pin Login Unavailable.  I uninstalled the update on 1 machine, and it did not fix the problem.  I’ve tried numerous suggested fixes/changes in Group Policy, etc., and nothing has fixed the problem.  No other problems have been noted yet.

 

There are other details to getting to this point, but found a solution, after trying 10-15 other suggestions.  Delete the contents of the folder C:\Windows\ServiceProfile\LocalServices\AppData\Local\Microsoft\Ngc , then reboot, and your prompted for the Pin login again.  Don’t know why it’s requiring a 6 digit PIN, because I’ve never set that rule.  The files in the Ngc folder will be rebuilt when you reboot.

Worth noting: Microsoft says it fixed a similar-sounding bug in the late-late second August cumulative update for 1903. Per KB 4512941:

Addresses an issue that may prevent the personal identification number (PIN) prompt from appearing when authenticating in Internet Explorer.

I wonder if this is a new manifestation of an old bug — or a completely new one altogether?

 

Have any of you had this problem?

 

 

 

Source: Yet another bug with this months Win10 1903 cumulative update: PIN knockout (AskWoody - Woody Leonhard)

[zanderthunder]

9 hours ago, steven36 said:

All the bugs started  up this time when they patched  DejaBlue Aug update  then they patched two remote code execution bugs in the Remote Desktop Protocol in Sept .  and spun off more bugs . Unless M$ hires  a new QA team what you say is never going to happen,  after they  laid them off in 2014 botched updates started appearing in Windows 7 and 8.1 as well . Windows 10 has been one big bug  fest since 1st released in June 2015  it's a never ending cycle of Problem Shooting .  The difference in 1903 and most other versions was most of the bugs  was in it when released from insiders  that were not found yet and   Microsoft patched them after released GA . 

 

Most of the bugs in 1903 is coming from post  GA release  security updates . It's not a insiders release  and  they  laid off there QA team in 2014 so the consumers are doing the beta testing of every update .What people dont get The QA titles have changed  now they call them "Customers" If you don't won't to beta test for business you need to buy a  Mac or use GNU Linux LTS witch is free . As long as  any version of  windows have updates they not testing them  . The only update testing that is going on is before it got released to consumers  (Insider releases .)   Once a version goes to Consumers  Home users that are not insiders are testing updates . Insiders are on a different version of Windows 10 with another list of bugs.

 

Why did Microsoft lay off 'Programmatic testers'?

https://www.linkedin.com/pulse/20140806183208-12100070-why-did-microsoft-lay-off-programmatic-testers

 

Microsoft Has A Software Quality Problem

https://www.thurrott.com/windows/windows-10/187407/microsoft-has-a-software-quality-problem

 

Blue Screen Stop 0x050 error reported for systems installing KB2976897, KB2982791, and KB2970228  Aug 14, 2014

https://www.infoworld.com/article/2608859/blue-screen-stop-0x050-error-reported-for-systems-installing-kb2976897--kb2982791-.html

 

Windows updates are at it again, reportedly hanging and slowing down systems April 13, 2019,

Windows 7 machines seem to be the most vulnerable

https://www.techspot.com/news/79639-windows-updates-again-reportedly-hanging-slowing-down-systems.html

 

 

 

Then there's something wrong with company culture in Microsoft, like what the article said earlier:

 

14 hours ago, steven36 said:

“Don’t blame Windows, blame company culture where features get people promotions but not bug fixing and optimizations. Same thing happens at Google frequently.”

 

[Karlston]

The problem is the failure of Microsoft’s experiment to replace professional inhouse testers with unprofessional Windows Insiders who tend to not use their installs for normal activities, connect few peripherals, and seemingly are more interested in new eye candy than doing any testing or reporting bugs.

[steven36]

8 hours ago, Edward Raja said:

Then there's something wrong with company culture in Microsoft, like what the article said earlier

The problem is the same in every company , they layoff workers in order to profit ,  Actuality there  doing much better   than it did in Bill Gates and Steve Ballmer  era . So there culture is achieving there main goal is  to profit. They put profit above people and that's any company . They gained a 19% Profit reported back in  July and manged  to stay out of US Antitrust probes this go around . None of the other Big tech giants can say  that there culture is way more messed up than  M$  is ATM. The  reason Bill Gates and Steve Ballmer  could never make as much profit as  the Satya Nadella  era is they was under US Antitrust fire witch stagnated there growth for years they was known as just the Desktop Windows software company. When that's mostly all you do that's were you put most of your investment in. That's not today's Microsoft anymore.  Windows users are stuck in the past in the good old days ,pre windows 10 when they had others running Microsoft.

 

• For the first time ever, the Intelligent Cloud division brought in the most revenue among the three groups. Intelligent cloud revenue rose 19 percent to $11.4 billion, powered by 64 percent annual revenue growth from Azure. Read more about the company’s cloud business performance here.
• In the company’s Productivity and Business Processes division, which includes Office 365 and LinkedIn, revenue increased 14 percent over last year to $11 billion in the quarter.
• Revenue in the company’s More Personal Computing division, which includes its Windows PC business, Surface products and gaming teams jumped 4 percent over last year to $11.3 billion. The gaming division saw a 10 percent drop in revenue in the quarter, cause growth to slow within the division as a whole.

https://www.geekwire.com/2019/microsoft-trumpets-record-year-126b-annual-revenue-14-quarterly-profits-beat-estimates/

 

The other stuff  they have is making just as much money as there PC division ,  there not going to invest a lot a money in  consumers were they not made much money on since 2012 the only thing that is saving there PC division  from  having the same fate is as there Smart Phone division is there business costumers . After years and years of losing profits on Windows it's no longer there main objective . Microsoft could stop making windows witch they want right now because of business costumers is buying it and still make a good profit  without  it .

 

No company is going invest a lot of money in something that is not profitable from a certain group of  users . In Microsoft case this is consumers .. Microsoft don't care about home users anymore ether you can beta test for them or use Linux or MAC OS .  They profit from Apple and Linux too . They own a software company that make stuff for Apple and  most of there Azure is Linux costumers.