Error 0x80888002 on build 22509

Anonymous
2021-12-02T03:25:28+00:00

Split from this thread.

Windows 11 Insider Preview 22509.1000 (rs_prerelease)

Download error - 0x80888002

Windows Insider program | Windows Insider preview | Install, activate, and 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

192 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Anonymous
    2021-12-08T21:43:32+00:00

    No changes or fixes for this issue with build 22518.1000.

    Same workaround discussed earlier in this thread for users encountering the problem. 😉

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-12-08T23:36:12+00:00

    Strangely enough, this time I downloaded 22518 and it installed in a normal manner. 22509 never worked without a hack, but no problem with 22519. For an update with "no changes or fixes for this issue", pretty amazing. I have decided my computer is haunted. :-)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-12-08T23:47:10+00:00

    Strangely enough, this time I downloaded 22518 and it installed in a normal manner. 22509 never worked without a hack, but no problem with 22519. For an update with "no changes or fixes for this issue", pretty amazing. I have decided my computer is haunted. :-)

    There was nothing listed in the 22518 Blog about fixes for this problem.

    I have no idea why yours failed at 22509 and passed with 22518.

    That is question for Eddie. 😎

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-12-09T00:41:04+00:00

    Actually, this is my second time I had an upgrade not work and then the next one worked fine. I can't be sure anymore, but I think the first one was back in 2018-19(?). I've decided to treat this little adventure in the same manner I did the first one: give MS a little time "and this too shall pass". Nice for me: got to enjoy a little adventure finding a work-around and then MS drops a new, stable update right out of the box. And we move on...

    Was this answer helpful?

    0 comments