[ad_1]
The cumulative update of Windows 10 KB4515384 has been pretty buggy, some compromising the Start menu and Windows Search, and others causing audio problems. Users have now reported other issues related to the update.
On the Microsoft Feedback Hub, a user reported a bug that came with the update, which disables Ethernet or WiFi connectivity.
The cumulative update (kb4515384) prevents activation of the NIC with a code error of 10. Reinstalling network drivers from Intel or Windows Update sources does not resolve the problem. However, removing the update via the 'Programs and Software' pane or using a set of recovery points before the update completely fixes the problem.
Another user reported that his network card had stopped working after applying the update:
KB4515384 breaks Ethernet and wifi adapters on my PC. Appears to create new devices because they are labeled "No. 2" and when exposing hidden devices in Device Manager, previously named devices appear. Uninstalling these new / old drivers does not solve the problems (ie "ethernet unplugged", which is clearly not the case). Only option was to uninstall this update.
In addition, users could not open the Maintenance Center after installing the update.
After installing KB2515384, I can not open Action Center or Microsoft Edge. This is on Windows 19H1 18362, tried to repair and reset Microsoft Edge. Without success. I ended up removing the update. Last month, I also had to remove the previous update KB4512941 which was causing excessive use of the processor by SearchUI and was forcing the cooling fans.
In addition to a damaged action center, this user was unable to open some application icons, leaving them with the choice of uninstalling the update:
The update KB4515384 causes problems on my PC with a high Search CPU, my audio icon does not open, nor does the Action Center. The only thing that makes things normal is to uninstall the update.
It is recommended that users encountering these issues uninstall the update until the release of an official bug fix; but for the bad network card bug, disabling and reactivating the card in Device Manager worked for some people.
Source: windowslatest
[ad_2]
Source link