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

192 answers

Sort by: Oldest
  1. Anonymous
    2022-01-08T20:03:52+00:00

    Hi fg,

    I just removed that from my signature last week 😂

    This is a Dell Inspiron 5590/Core i5 10th gen/12GB of RAM.

    On the machines you use the workaround, are they on green zone or yellow zone?

    Hi Sumit,

    I think I mentioned earlier, in my case I don't have any problems with fully compliant boxes, I have a Lenovo Yoga 920 laptop with I7 8550U, Dell Desktop 8930 with I9-9900K, Dell Desktop 8940 with I7 11700, all 3 complete the updates fine without any hack.

    I see the Error 0x80888002 only on red zone boxes, my only yellow zone box is my production machine, and I leave that alone, I don't use it for testing.

    Your box apparently is fully compliant, so the problem has to be a screwup on the MS check for the requirements.

    I got 2 machines in the red zone updated to 22526, but clearly those needed some known tricks to get over the blocks and the 0x80888002 error.

    MSI GT70-0NC Laptop and Dell XPS 8300 (Legacy Bios) are both up and running with 22526.

    I'm sure MS will come up with some other new block on next builds. 🤷‍♂️

    I have a green zone box and I first ran into the error with 22509. I was still getting the error when 22518 came out and was initially unsuccessful at installing that build as well using the appraiser fix plus several others I tried.

    It wasn't until I ran the Skip_TPM_Check_on_Dynamic_Update script from GitHub before doing the update that I was successful.

    I've since had no problems with 22523 or 22526.

    I never did get 22509 installed.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-01-08T20:09:57+00:00

    Hi fg,

    I just removed that from my signature last week 😂

    This is a Dell Inspiron 5590/Core i5 10th gen/12GB of RAM.

    On the machines you use the workaround, are they on green zone or yellow zone?

    Hi Sumit,

    I think I mentioned earlier, in my case I don't have any problems with fully compliant boxes, I have a Lenovo Yoga 920 laptop with I7 8550U, Dell Desktop 8930 with I9-9900K, Dell Desktop 8940 with I7 11700, all 3 complete the updates fine without any hack.

    I see the Error 0x80888002 only on red zone boxes, my only yellow zone box is my production machine, and I leave that alone, I don't use it for testing.

    Your box apparently is fully compliant, so the problem has to be a screwup on the MS check for the requirements.

    I got 2 machines in the red zone updated to 22526, but clearly those needed some known tricks to get over the blocks and the 0x80888002 error.

    MSI GT70-0NC Laptop and Dell XPS 8300 (Legacy Bios) are both up and running with 22526.

    I'm sure MS will come up with some other new block on next builds. 🤷‍♂️

    I have a green zone box and I first ran into the error with 22509. I was still getting the error when 22518 came out and was initially unsuccessful at installing that build as well using the appraiser fix plus several others I tried.

    It wasn't until I ran the Skip_TPM_Check_on_Dynamic_Update script from GitHub before doing the update that I was successful.

    I've since had no problems with 22523 or 22526.

    You are still using a hack on a green zone box and that is the bug.

    MS is asking for feedback on the FBH from users that have the problem on fully compliant machines.

    I cannot provide any feedback because my green zone boxes do not fail.

    https://aka.ms/AAf37jp

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-01-09T00:45:01+00:00

    For those who may be interested on using a 3rd party unofficial/unsupported ISO to update or clean install,

    AdGuard includes an automatic fix in the script.

    My laptop is Windows 11 compliant so I have no way to test this option, use at your own risk.

    All topics related to Windows Insider builds may be discussed in the Windows Insider Program forum. Sometimes users propose workarounds and third-party tools that are not supported or recommended by Microsoft. These topics are permitted for discussion, but Microsoft representatives will not comment on them.

    Hi Sibro,

    I have plenty of non-compliant boxes, I could check if that script does anything different than what I do manually, but I cannot find that script.

    Is there a direct link to download it? Is it for subscribers only?

    I thought I had it some time ago, but I cannot find it anymore and cannot find where and how to get it. 😎

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-01-09T00:58:40+00:00

    It's on GitHub.com. Go to that URL and then search around (I think top left corner) and you'll see the file to bypass ALL checks when upgrading. Goog luck...

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-01-09T01:11:03+00:00

    Hi fg, happy new year!

    Go to AdGuard site, select your build and download the .cmd file as you would with UUPdump, when you execute it, it will present you with the menu before downloading the rest.

    Was this answer helpful?

    0 comments No comments