I have same issues with Windows 10 21H2. We have tested manually and KB5031356 was failed leaving the SSU installed Servicing Stack 10.0.19041.3562
I have tried 10 machines and 5 were success and 5 were failed.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi, I am unable to install latest Windows 10 22H2 Cumulative Update, with the error 0x8007000D. I have tried downloading the KB from Microsoft Update Catalog and run manually but I am getting this error as well. Has anyone else faced this issue and does anyone have a solution for this?
Thank you!
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.
I have same issues with Windows 10 21H2. We have tested manually and KB5031356 was failed leaving the SSU installed Servicing Stack 10.0.19041.3562
I have tried 10 machines and 5 were success and 5 were failed.
Same problem here with Windows 10 Pro and plenty of space and memory... idk what to do.
Thanks for your reply. Hope Microsoft gets the message and addresses this problem. My computer with the problem is HP Pavillion desktop that came with win 8.1 and successfully updated to win 10 but it is not compatible with win 11. It works great and I was hoping to keep it going until support ends for win 10. I sorta thought that this update is preparing for win 11 and that it is not compatible with my graphics card or maybe some other hardware on my computer. Hope Microsoft comes up with a fix for this problem and provides a comprehensive update that works on my computer and the many others that I see here and on Reddit that are having the same problem with this update.
Just noticed that kb5031356 is for 22H2 builds 19044.3570 and 19045.3570 and that my HP pavillion desktop is Win 10 22H2, build 19045.3448. Could this be my problem? And, why is not my build 19045.3448 not up to date? And how do I get it up to date. Maybe some of the earlier updates going to 22H2 did not work properly either??? Just noticed that this update is suppose to update the build to 19045.3570, so guess that is not the problem!!!
Hope that Microsoft comes up with a fix for this problem.