The Windows 10 KB4515384 cumulative update has proved to be quite buggy, with some compromising the Start menu and Windows Search, and others causing audio issues. Users have now reported on further issues that they’re experiencing with the update.
On Microsoft’s Feedback Hub, a user reported a bug that came with the update, that disables Ethernet or WiFi connectivity.
Cumulative update (kb4515384) causes the NIC to fail to enable with a code 10 error. Reinstalling network drivers from Intel or Windows Update sources does not resolve the issue. However removing the update through the ‘Programs & Software’ panel or using a recovery point set *before* the update fully resolves the issue.
Another user reported that their network adapter stopped working after they applied the update:
KB4515384 breaks ethernet and wifi adapters on my PC. Appears to create new devices as they’re labelled ‘#2’ and when exposing hidden devices in Device Manager the previously named devices appear. Uninstalling these / new or old drivers do not fix the issues (i.e. “ethernet unplugged” which it is clearly not). Only option was to uninstall this update.
Additionally, users have been unable to open Action Center after installing the update.
After installing KB2515384 I’m unable to open the Action Centre or Microsoft Edge. This is on Windows 19H1 18362, Tried repair and reset of Microsoft Edge. No success. Ended up removing the update. Last month I also had to remove the previous update KB4512941 that was causing SearchUI to use excessive CPU and stress the cooling fans.
In addition to a broken Action Center, this user was also unable to open certain app icons, leaving them no choice but to uninstall the update:
Update KB4515384 is causing problems on my PC with high CPU from Search and my audio icon won’t open, nor will Action Center. Only thing that makes things normal is uninstalling the update.
Users experiencing these issues are recommended to uninstall the update until an official bug fix is released; but for the broken network adapters bug, disabling and re-enabling the adapter in Device Manager has worked for some people.