You just updated directly from Windows 10 (version 21H2) to Windows 11 (Build 22526)? How is that possible?
Error 0x80888002 on build 22509
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.
192 answers
Sort by: Newest
-
Anonymous
2022-01-07T13:54:58+00:00 -
Sumit 44,306 Reputation points Volunteer Moderator2022-01-07T13:37:48+00:00 Good tip. Appreciate that.
What is disappointing is, the issue isn't even mentioned in the notes. I am tempted to try a clean install next but it would take a couple of days to set everything up as I like.
-
Anonymous
2022-01-07T09:03:17+00:00 That happened the same with build 22523.
Same problem and same workaround.
Hi fg,
Don't know why but the same workaround has stopped working for me since 22518. I am using a 22504 appraiser.
Hi Sumit,
Maybe it is something that is blocked by appraiserres.dll and not just appraiser.dll.
I usually rename that to appraiserres.dll.bak so that it does not check for 2 other requirements.
What is weird is that you have a box that meets the requirements and should not need any hack. MS should see where they have the bug if you submit the FBH report.
It is too bad that they don't show what it is blocking the update.
I just updated a laptop from 19044.1415 in R.P. to 22526.1000 using the same workarounds. and went all the way through.
-
Sumit 44,306 Reputation points Volunteer Moderator2022-01-07T08:35:19+00:00 That happened the same with build 22523.
Same problem and same workaround.
Hi fg,
Don't know why but the same workaround has stopped working for me since 22518. I am using a 22504 appraiser.
-
Anonymous
2022-01-07T08:27:55+00:00 Windows 11 Insider Preview 22526.1000 (rs_prerelease) same problem downloading and installing. Works with same workaround. Didn't get fixed yet.
Happy new year!