Besides the security updates in Internet Explorer and Microsoft Edge, there are also many fixes and some known issues that are still unresolved.
Strange enough, there’s nothing from Adobe and some users are intrigued by that:
Relative small patch Tuesday, and nothing from Adobe
Amongst the Windows 10 versions that received updates, Windows 10 v1903 seems to be the one that is currently affected by the above mentioned unresolved issues and also by some new ones.
KB4517389 causes Critical Error
Some users are complaining that after installing the KB4517389 on their PC’s, they can’t use the Start Menu and encounter a Critical Error:
KB4524147 originally caused a critical error when using Start Menu AND it prevented my printer from printing. The latter was because of some mess up with the print spooler. I uninstalled KB4524147 and BOTH problems disappeared. This morning, I updated with KB4517389. The printer seems to work, BUT I receive a critical error when using the Start Menu.
The problem doesn’t seem isolated, as other users reported it on Reddit:
Off to an inauspicious start… KB4517389 broke my W10 1903 test VM. After installing, I get “Critical Error. Your start menu isn’t working.” Rebooting doesn’t change, but uninstalling the patch gets it back.
For now, there isn’t an official resolution. The only thing that seems to work is to uninstall the update.
Also, if you didn’t updated yet and want to avoid similar bugs and issues, you can block the update.
Printer drivers issue
As we already know, Microsoft has released a silent update on October 3rd to solve an issue with printer drivers. Supposedly, the issue was solved then.
Again, with the release of the October 2019 Patch Tuesday updates, the tech giant confirmed that the issue was solved:
Despite that, some users are still encountering the problem:
Tested on one computer, still broken. Edit: Removing KB4524147 / KB452148 before installing the October cumulative update seems to work
For now, the only workaround is to remove KB4524147 / KB452148 before installing the October Patch Tuesday updates.
Search is still not working for some
Windows Search is causing problems for a lot of Windows 10 users. The problem was first reported months ago, and it’s still not working for some, despite Microsoft addressing it several times.
Here’s what one user says:
will test on if Windows Search works and report back EDIT: it doesn’t EDIT: it doesn’t and it might be because I have VMware Pro 15 apparently.
If you encounter the same issue, besides uninstalling the update, there is another unofficial workaround.
You’ll need to copy ActivationStore.dat from another Windows 10 working PC to C:ProgramDataMicrosoftWindowsAppRepositoryPackagesMicrosoft.Windows.Cortana_22.214.171.12462.
If you can’t view/copy in the AppRepository folder, edit the folder permissions to authorize yourself. As we already said, this is an unofficial workaround, but it worked for some.
Give it a try, as it might work for you, too.
Mouse issues after the update
Other users are reporting problems with their peripherals after the update:
After updating to the 1903 i have experienced an issue with my mouse cursor. It started when i tried to load any page on my browser and when gaming (Football Manager 2019). The cursor at some points just jumps or skips. Dont know why..no cpu spikes or any spike of any kind. i kind of fixed it when i updated some drivers on device manager but then another cumulative update came a week ago and the issue started again. i reinstalled windows to the 1903 build and nothing changed.
If you bump into the same issue, don’t worry. We’ve already dealt with this problem. Follow the simple steps from this guide and you’ll get rid of the problem in no time.
Connectivity issues are not that uncommon when it comes to Windows 10 updates. But some users claim that the latest KB4517389 broke their Bluetooth all-together:
I am running windows 10 pro 64 bit, my computer is at this update, and it broke bluetooth completely.[…]One thing that is weird, is after I tried checking the device manager on **** is going on, it shows a broke entry under the USB controllers called “Unknown USB Device (Device Descriptor Request Failed)”.
This can happen if files get corrupted and Bluetooth gets reassigned as a USB controller. There isn’t yet a confirmed solution for this problem, but there are a couple of things that you can try:
- Update that certain USB driver in Device Manager.
- Update your drivers and your BIOS.
- Update the Bluetooth driver from the manufacturer’s website.
- Uninstall the Bluetooth driver and let Windows install the default driver.
If you don’t know how to update your BIOS, check out this awesome guide and get the job done without any problems.
Qualcomm Atheros AR9485 not working properly
As we already mentioned, connectivity issues are not that uncommon after an update, but they usually get resolved pretty quickly. That’s not the case with Qualcomm Atheros AR9485, as some users reported:
Devices with Qualcomm Atheros AR9485 experience problems with WiFi dropping and network adaptor needing to be reset. Microsoft are aware there is a problem with their Windows 10 updates since their 1607 upgrade, yet seem incapable of rectifying the problem.Their latest update is showing same problem.
This is a pretty old problem, but we already dealt with it. You can try the steps in this dedicated guide, as it may help you solve the connectivity issues quickly and easily.
Besides these problems, there are also a lot of installation issues and boot errors affecting the latest KB4517389. Check out this article to find out more info about that.
Also, Microsoft Edge seems to stop working on some Windows 10 PCs after updating to KB4517389. If you want to know more, take a look at this dedicated article.
Have you encountered any other issues after updating to KB4517389?
Share your experience in the comments section below and we’ll be sure to take a look.
- Some Patch Tuesday updates may cause black screen issues
- How to fix performance issues after installing Patch Tuesday updates
- Windows 10 forced update to v1903 gets stuck for many users