I am having the issue; Windows Update successfully installed KB5001716 on March, 6, 2024 and then made multiple more attempts to install this update, for reason(s) I do not understand. I uninstalled the updates that were installed on the above mentioned day, rebooted, reinstalled, and the issue was not resolved. I have tried SFC /Scannow in a Command Prompt which found nothing. I sincerely hope this will not prevent me from receiving future Windows Updates. The image in the original post mirrors my own Windows Update history.
windows update error (0x80070643) for kb5001716
One windows update error (0x80070643) kb5001716
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.
137 answers
Sort by: Newest
-
Anonymous
2024-03-07T18:09:30+00:00 -
Anonymous
2024-03-07T17:55:07+00:00 I think that Microsoft is trying to force its users to install a new Windows and finally move to Windows 11.
A few months ago, they released a security update that requires more than 500 MB of free space in the Windows recovery partition ... to do such a thing without installing a new Windows was beyond the ability and knowledge of a normal user.
Again in the last few days the update "KB5034843" was released...which caused problems on my system...so that I can't find a solution for it in the forums...Microsoft expert also could not help me. .. I had to figure out this problem by myself
And now they released this update KB5001716 which generally prevents Windows from receiving new updates.
My system gets blue screen randomly after receiving this update
-
Anonymous
2024-03-07T17:46:52+00:00 Great instructions.
Tried everything on this thread, none worked.
5 Stars for the instructions - appreciate your submission.
-
Anonymous
2024-03-07T17:40:56+00:00 I just fixed the issue from January concerning recovery partition size, and one week later this update generated the same error code. Frustrating...
This time, the path forward is to hide the update until some future date. Too much time has already been spent in researching and manually fixing to have to manage a similar situation.