Microsoft’s Windows 10 Network Bug Fixing Update Causes a Network Bug

Microsoft rolled out an out-of-band update for Windows 10 a few days ago to resolve an issue breaking down VPN connections on some devices.

But as it turns out, this bug-fixing update itself is causing another bug, with some users now complaining of an issue breaking down Wi-Fi connections.

Windows update KB4554364 landed to resolve a problem that potentially prevented some users from working remotely, something that considering the existing pandemic is terrible news. As per the official changelog:

“Addresses an issue that might display a limited or no internet connection status in the notification area on devices that use a manual or auto-configured proxy, especially with a virtual private network (VPN). Additionally, this issue might prevent some devices from connecting to the internet using applications that use WinHTTP or WinINet.”

It goes without saying that many rushed to install this update on their devices to restore the normal VPN functionality. Some, however, discovered that KB4554364 then prevents their computers from connecting to Wi-Fi networks for a reason that’s yet to be determined.

No workaround so far

A report from HTNovo shows that no workaround has been discovered so far, other than removing the update completely. In which case, users are left without the VPN patch, of course.

Connecting to a Wi-Fi network fails with the following error if the bug occurs on the device:

“Socket error 0×2200021. c:/windows/sywow64/appidpolicyengineApi.dll, instruction cannot be read.”

Microsoft is yet to acknowledge the issue, but with a new Patch Tuesday just around the corner, there’s a chance the company waits for this patching cycle to release more fixes. This month Patch Tuesday takes place on April 14, and as usual, new cumulative updates including both security and non-security fixes will be shipped to all Windows 10 versions out there.

https://news.softpedia.com/news/microsoft-s-windows-10-network-bug-fixing-update-causes-a-network-bug-529628.shtml

Leave a Reply