Error 0x80888002 on build 22509

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

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

Hi,

From what I read, that bypasses all the MS checks. 😎

If the machine passes the latest PC Health Check for Windows 11, I'd rather wait for a MS fix.

Windows Insider Preview PC Health Check Application (microsoft.com)

I repeat, my system passed the very latest MS PCHealthCheck, but would not download IP 22509. I could have, as you have chosen, to simply wait for MS to fix the situation, but where is the fun in that? As an old, retired BSEE I have more time than most to apply to this problem (and similar) and having the typical engineer's refusal to just never give up, I just plug along until I find a solution. To each his own, I think. :-) BTW, I did mention that I made a full image of the C: drive before I started playing with it, didn't I? Playing around is always fun, but first make damn sure you always have a fallback position.

I repeat, my system passed the very latest MS PCHealthCheck, but would not download IP 22509. I could have, as you have chosen, to simply wait for MS to fix the situation, but where is the fun in that? As an old, retired BSEE I have more time than most to apply to this problem (and similar) and having the typical engineer's refusal to just never give up, I just plug along until I find a solution. To each his own, I think. :-) BTW, I did mention that I made a full image of the C: drive before I started playing with it, didn't I? Playing around is always fun, but first make damn sure you always have a fallback position.

That's ok, just your choice, I already found a different workaround which did not leave any changes in the system and did not have to use any script. 😉

Still, I'd like to see a MS fix that works without any workaround.

Have fun.

Good for you! I see you didn't give up so easily either - nice that you found one that works and you like. See, I told you half the fun is finding a solution - however it works - and then patiently waiting for MS to catch up. Keep on smilin'. :-)