Update for Windows Security platform - KB5007651 (Version 1.0.2109.27002)

Anonymous
2022-05-21T22:21:42+00:00

I got an error for this Update for Windows Security platform - KB5007651 (Version 1.0.2109.27002) and can't seem to find a solution. Install error - 0x80070643 Anyone got any ideas?

Windows for home | Windows 11 | 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

163 answers

Sort by: Newest
  1. Anonymous
    2022-06-26T05:06:52+00:00

    Okay, thanks...will give it a go and let you know

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-06-25T20:55:01+00:00

    So, are you suggesting I unhide this update and try again? If trying again, how would one try (i.e. long edit registry, short repair/reset of windows update, A/V on/off, do nothing - just unhide only, etc.)?

    Per my earlier posts, I unhid it, retried WU several times, and it has disappeared, probably pulled. I'd suggest you unhide it, recheck via WU, and if you see no trace of it anywhere, then carry on as usual.

    As Microsoft now employ the user base as post release guinea pigs, we can be pretty sure that they'll fail to inform and fail to act promptly. Business as usual there.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-06-25T19:27:09+00:00

    So, are you suggesting I unhide this update and try again? If trying again, how would one try (i.e. long edit registry, short repair/reset of windows update, A/V on/off, do nothing - just unhide only, etc.)?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-06-25T14:45:02+00:00

    Looks like Microsoft pulled it as it isn’t offered anymore and under history all failed installation attempts are gone.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-06-25T09:20:31+00:00

    seems that automatically Microsoft fixed this issue....

    Was this answer helpful?

    0 comments No comments