2018-03 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4088776) - Error 0x80070002

Anonymous
2018-03-14T01:51:57+00:00

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.

Windows for home | Windows 10 | Windows update

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.

0 comments

148 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-04-06T14:58:38+00:00

    To Microsoft Support:

    Why must we jump through a bunch of technical hoops to get this update to work?

    2018-03 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4088776) - Error 0x800f081f

    Just fix it, already! Sheeeeesh!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-04-06T17:10:56+00:00

    So my route was not to reinstall windows.

    I removed Malwarebytes and every other programme that could cause of the problem, including Avast. I left Defender running.

    Additionally, I did a clean boot as well as restart into safe mode to perform the following; remove windows updates with the incorrect installation date, then go back to the closest restore point. I think I had turned to manually windows update in services or had it on delayed automatic. If you don't have incorrect installation dates such as mine it might be make sense to remove the last update as the solution for me was via that it started installing updates as part of the system restore process - which I hadn't expected and was surprised to find worked.

    NB I have just seen that both strategies are suggested by m/s and others - conflict with intrusive software, and use 'restore point' process to clear the error.

    As a last resort I had planned to switch off windows auto-updates permanently to avoid the cumulative failures you have experienced as this slows everything.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-04-07T08:42:42+00:00

    same problem, nothing helps ((

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2018-04-07T10:30:57+00:00

    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!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-04-08T20:21:11+00:00

    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!

    Was this answer helpful?

    0 comments