Error 0x80888002 on build 22509

سلام متاسفانه نتوانستم دانلود کنم

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...

Perhaps it worked because you did not undo the workaround changes that you mentioned in your post last time for the previous build?

I don't think MS put out any fix for this problem yet. 😉

From your post:

"Okay, here's a work around: My Ryzen 3 system (3600X@ 4.2GHz, 16GB DDR4, 500GB Samsung M2, 1TB Samsung 970, AMD 570X-8GB) which passes all MS MyPCHealthCheck tests and had previously (through 22504) always updated but would not go beyond 10% on IP 22509. Just pisxed me off. :-) So, looked around and found this solution: Go to GitHub and download their Media Creation Tool. Unzip and click the Auto Update button (near the top of screen) and let it run. Reboot and go back to Windows Update and hit Retry. BAM, worked like a charm for me. GitHub advises to the go back and run the Media Creation Tool a second time to undo the changes, but for now I'm going to leave the changes in place and see what happens with the next IP. Good luck! :-) "

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...

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. 😎

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. :-)