This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have been struggling with this issue for well over a month, It first started with the "2018-02 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4090913)". Now its update Tuesday and this months cumulative update (KB4088776) is doing the exact same thing.
I have tried all 5 of the steps provided by microsofts here: (More than once)
https://support.microsoft.com/en-ca/help/910336/windows-update-error-0x80070002-or-0x80070003
Finally, I have done a clean install of windows 10 three times now in the past couple of weeks, to no prevail.
After each fresh install. the exact same issue.
I am running Windows 10 Pro Education, Version 1709, build 16299.15.
After each install it seems to update no problem, but seems to only be an issue once I reactivate my Windows 10 Pro Activation key.
I gave up weeks ago, and was hoping my problem would simply be solved by the latest update, but that is not the case.
Any help and suggestions would be greatly appreciated.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
solucionado:
You already had the *.old files from the last time you used this workaround. The person who replied that it did work probably hadn't used this workaround previously. Try deleting the two *.old files you created previously and try the workaround again.
That makes me so happy, HugoToledoUSA! I posted my fix so long ago that I just assumed that either (1) no one read it, or (2) it didn't work for anyone else. BTW, this same fix worked for me for the KB4089848 update, which superseded the KB4088776 update. If you type in winver in Cortana (or after clicking the windows box at the lower left of your screen), and then click on the "run command" that will pop up, it should say that your system is at: Version 1709 (OS Build 16299.334). If the last three numbers aren't 334, you still have to follow the same process for KB4089848. Good luck, and have a stress-free week (which will be easier for us all if Microsoft doesn't send us any more malfunctioning updates)!
K8Village! My hero, man! That did it. No reboots necessary for me.
Here's what was particularly amusing. After reading you recommendation, while waiting for it download I tried Microsoft's Virtual Assistant. It somehow managed, with this as its input: "2018-03 cumulative update for Windows 10 Version 1709 for Windows x64-based Systems (KB4089848) fails", to point me to a completely different fix for a different product! Oy!
I was then surprised when I saw I could have a human call me. I'm thinking this can't likely be very helpful -think of how much it would cost to provide that sort of support to a successful conclusion for free!- but what did I have to lose?
They called me back in about 20 minutes and after asking about my computer model and doing some checking, the fellow said,"the update failed because Lenovo does not provide Windows 10 drivers." Alrighty. I know that's not likely true. Anyway, that's certainly a reasonable means of getting folks off the line. :-)
Anyway, I then ran the download as you suggested and it worked perfectly the first time. No further reboots after the first one were required. All was up to date.
Thanks, again, for making this so easy!
You can stop it by doing some steps. I made a video for you if you see this then can be able to stop this in your laptop. How to Stop Windows Ten From Automatically Downloading & Installing Updates!
