I did the in place upgrade today. All went well and easy to do, didn't loss any thing and my pc updated KB5032189, pc now up to date. should have done it earlier
Installation Failure for 2023-10 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5031356) 0x8007000D
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!
Windows for home | Windows 10 | 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.
68 answers
Sort by: Most helpful
-
Anonymous
2023-11-18T11:04:37+00:00 -
Anonymous
2023-10-30T12:50:57+00:00 So I don't have Twitter but I did use the feedback hub. I forgot to go back on the other day and pause updates again so I'm sure when i log back in I'll have to undo everything it tried to do again 😖.
-
Anonymous
2023-10-30T12:27:12+00:00 you should try to use the feedback Hub in windows 10 to try to bring attention to this issue, additionally, we can also tweet the microsoft, windows, windowsdev, windows support etc twitters to bring more attention to it.. hopefully at some point someone will start bring it to the developer's attention
If everyone does this they will have to do something
press on the windows button bottom left of the task bar and its under F
-
Anonymous
2023-10-14T02:30:37+00:00 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!!!
-
Anonymous
2023-10-14T01:17:21+00:00 Hope that Microsoft comes up with a fix for this problem.