Softpedia >News >Microsoft >Windows
Softpedia Homepage   

How to Fix Issues Caused by Windows 10 Cumulative Update KB3140743

KB3140743 said to break down some PCs installing it

Mar 3, 2016 13:12 GMT  ·  By
The update breaks down some PCs and makes it impossible to boot
   The update breaks down some PCs and makes it impossible to boot

The latest cumulative update for Windows 10 released by Microsoft, KB3140743, is wreaking havoc on a number of computers installing it and causing them not to boot anymore.

As we’ve already told you earlier this week, some PCs are unable to install the update, but it appears that even those who actually manage to do that are experiencing problems.

In some cases, hopefully isolated, the computer no longer boots and gets stuck with a spinning circle logo, making it impossible to get back to the desktop.

How to fix the issue

Thanks to Reddit user JJisTheDarkOne, there’s also a fix for this critical problem, and it involves booting into Safe Mode to uninstall the update and then hide it. Basically, once you are in Safe Mode, go to Control Panel > Programs > View installed updates, and look for the patch labeled KB3140743. Right-click and uninstall it, and then your computer should boot correctly.

The next step is to completely hide the update and make sure that it’s not installed automatically on your PC until a fix is provided.

To do that, you need to be on your now-working Windows desktop, download this tool, open a Command Prompt with administrator privileges by right-clicking the Start menu, and run the following commands one by one (supposing that the downloaded file is placed in the default “Downloads” directory - otherwise you need to manually navigate to it):


c:
cd \
cd users
cd name
cd downloads
wushowhide.diagcab
 Once the downloaded application launches, you need to click the advanced option and then select auto fix. Let it scan, select the option to hide updates, and choose KB3140743. Close everything, reboot the PC, and things should be fine.

We’ve also reached out to Microsoft to find out whether the company is aware of this problem or not and will update this article accordingly once an answer is provided.