Error with Windows Update KB3000850

Anonymous
2014-11-19T14:40:18+00:00

Hi,

This update, KB3000850, is quite large -- something like 720+Mb.  After quite some time downloading (seemed to get stuck at 4% and 90% downloaded), I got error 800700002 when I tried to install this windows update.

Right after starting download, I disabled my real time anti-virus.

Can anyone suggest ways to overcome this problem???

Thanks

Windows for home | Previous Windows versions | 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

64 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-12-16T01:25:11+00:00

    <Data Name="ErrorCode">2147942402</Data>

    That's  0x80070002  decimal as a Qword.  Have you tried the DISM command?

    For more detail I would use the ReportingEvents.log to get the timestamp.  Then find the portion of CBS.log which corresponded to that.  It might give a clue about which module is "missing".

    Robert,

    OK, where do you find the ReportingEvents.log -- what folder is it in and is there something you have to do to create?

    Thank you

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-12-06T19:08:21+00:00

     -- CBS    Appl: Selfupdate, Component: amd64_microsoft-windows-errorreportingfaults_31bf3856ad364e35_0.0.0.0_none_efffadd33d50fea5 (6.3.9600.17415), elevation:4, lower version revision holder: 6.3.9600.17031

    And it goes on for several pages

    Thoughts?

    Those aren't errors.  Just reporting events which involve directories or files which contain that word.   Please go back to ReportingEvents.log and see what the problem is AND ITS TIMESTAMP.  The timestamp will give you some context for the CBS.log.  Or do you think that you are already doing that?

    FWIW in my CBS.log strangely I am finding errorreportingfaults for 16521 and no entries at all about 17415.  I have not tried going back into any of the archived pieces of it.

    Powershell can be used to show that I do have .manifest files for those, though I think that mine are probably compressed (so the checksum part of the name may be different):

    PS C:\windows> dir -re -fi "*errorreportingfaults*17415*" ft Length, FullName -AutoSize<br><br><br><br><br><br>Length FullName <br><br>------ -------- <br><br>       C:\windows\WinSxS\amd64_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.3.9600.17415_none_611217891086c435 <br><br>       C:\windows\WinSxS\x86_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.3.9600.17415_none_04f37c05582952ff <br><br>4074   C:\windows\WinSxS\Manifests\amd64_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.3.9600.17415_none_611217891086c435.manifest <br><br>4073   C:\windows\WinSxS\Manifests\x86_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.3.9600.17415_none_04f37c05582952ff.manifest

    We would need to find a method of decompressing .manifest files to get more clues from those.

    BTW my approach to diagnosing your problem symptom would be to use ProcMon to provide a supplementary trace of the whole failed install procedure.  I don't have access to the source or support documentation to enable me to "read between the lines" what error messages mean--even when we do have some to look at.

    HTH

    Robert

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-12-06T16:23:06+00:00

    Robert,

    The enigma continues; just tried installing this update and here are the errors reported in the CBS log:

     -- CBS    Appl: SelfUpdate detect, component: x86_microsoft-windows-errorreportingfaults_31bf3856ad364e35_6.3.9600.17415_none_04f37c05582952ff, elevation: 4, applicable: 1

     -- CBS    Appl: Selfupdate, Component: x86_microsoft-windows-errorreportingcore_31bf3856ad364e35_0.0.0.0_none_4450a7c34e0e781f (6.3.9600.17415), elevation:4, lower version revision holder: 6.3.9600.17031

     -- CBS    Appl: SelfUpdate detect, component: x86_microsoft-windows-errorreportingcore_31bf3856ad364e35_6.3.9600.17415_none_b563117921443daf, elevation: 4, applicable: 1

     -- CBS    Appl: Selfupdate, Component: x86_microsoft-windows-errorreportingui_31bf3856ad364e35_0.0.0.0_none_f23f204a4a418a02 (6.3.9600.17415), elevation:4, lower version revision holder: 6.3.9600.17031

     -- CBS    Appl: SelfUpdate detect, component: x86_microsoft-windows-errorreportingui_31bf3856ad364e35_6.3.9600.17415_none_63518a001d774f92, elevation: 4, applicable: 1

     -- CBS    Appl: Selfupdate, Component: amd64_microsoft-windows-errorreportingui_31bf3856ad364e35_0.0.0.0_none_4e5dbbce029efb38 (6.3.9600.17415), elevation:4, lower version revision holder: 6.3.9600.17031

     -- CBS    Appl: SelfUpdate detect, component: amd64_microsoft-windows-errorreportingui_31bf3856ad364e35_6.3.9600.17415_none_bf702583d5d4c0c8, elevation: 4, applicable: 1

     -- CBS    Appl: Selfupdate, Component: amd64_microsoft-windows-errorreportingfaults_31bf3856ad364e35_0.0.0.0_none_efffadd33d50fea5 (6.3.9600.17415), elevation:4, lower version revision holder: 6.3.9600.17031

    And it goes on for several pages

    Thoughts?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-12-03T23:08:44+00:00

    Märchenhaft! Danke schön!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-12-01T23:40:40+00:00

    I tried creating an accessibility folder off my menu, no luck

    Did you check to see if that was necessary?  My suggestion was to use  ReportingEvents.log to find a timestamp and then see if you could find anything interesting and relevant at that time in CBS.log.  Uwe used that suggestion to devise a solution for his case.  What's yours?

    Was this answer helpful?

    0 comments