Share via

Windows 10 update 1809 error

Anonymous
2019-01-18T23:38:59+00:00

whenever I try to update it fails and gives me 2019-01 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4480116) - Error 0x80070002, anyway to resolve this issue?

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 No comments

12 answers

Sort by: Most helpful
  1. Anonymous
    2019-01-19T04:24:37+00:00

    Hello,

    I'm Independent Advisor and Microsoft MVP, here to help you with your question.

    Please run Windows Update troubleshooter from Settings app > Update & security > Troubleshoot. See if it works.

    If that doesn't work, try this:

    Open administrative Command Prompt and type following commands one-by-one followed by Enter key.

    net stop wuauserv

    net stop cryptSvc

    net stop bits

    net stop msiserver

    Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

    Ren C:\Windows\System32\catroot2 Catroot2.old

    net start wuauserv

    net start cryptSvc

    net start bits

    net start msiserver

    Close Command Prompt and see if Windows Updates works then.

    Let us know if this helps!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Vijay A. Verma 104.9K Reputation points Volunteer Moderator
    2019-01-19T00:38:41+00:00

    Run Built-in & Guided Walk through Windows Update troubleshooter

    Built-in : Windows Key+X > Click Settings > Click Update & security > Click Troubleshoot > Click Windows Update > Click Run the Troubleshooter

    Guided Walk though - https://support.microsoft.com/en-us/help/10164/...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Vijay A. Verma 104.9K Reputation points Volunteer Moderator
    2019-01-18T23:42:22+00:00

    Hi Danny0rtiz99,

    I am Vijay, an Independent Advisor. I am here to work with you on this problem.

    I recommend that you do a manual update for this KB.

    1. Windows Key+X > Windows Powershell (Admin)

    Type following (or copy and paste following) one by one and Enter

    net stop wuauserv

    net stop cryptSvc

    net stop bits

    net stop msiserver

    Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

    Ren C:\Windows\System32\catroot2 Catroot2.old

    net start wuauserv

    net start cryptSvc

    net start bits

    net start msiserver

    1. Type following in Windows Start Search box (Cortana) and hit Enter %systemroot%\Logs\CBS > Rename CBS.Log to something else.

    If it doesn't allow you to rename - Type services in Windows Start Search box > Click Services > Scroll down to find the Windows Modules Installer service and double-click on it > Set its startup type to Manual > Reboot your computer

    Go to C:\Windows\Logs\CBS > Rename CBS.Log > Reboot your computer > Then go back into the Services App and set Windows Modules Installer Service back to Automatic Startup (Note CBS log files contain information about windows update, SFC etc)

    (Source - https://partnersupport.microsoft.com/en-us/par_...)

    1. You can download the updates from Microsoft Catalog and update manually. Search for relevant KB in the Catalog.

    Microsoft Catalog - https://www.catalog.update.microsoft.com/Home.aspx

    Do let me know if you require any further help on this. Will be glad to help you.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Vijay A. Verma 104.9K Reputation points Volunteer Moderator
    2019-01-19T00:22:47+00:00

    You can skip this step.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-01-19T00:21:48+00:00

    I cant seem to find the CBS.log file to rename, and whenever I try to click services it tells me an administrator has blocked me from running the app

    Was this answer helpful?

    0 comments No comments