Windows update (KB5034441) Error (0x80070643)

Anonymous
2024-01-23T05:38:57+00:00

When I tried to install the windows update "2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" I received the error code (0x80070643).

I have already tried, restarting my computer, waiting a bit before retrying, running a memory diagnostic check, checking all my drivers for updates, installing optional updates, and running a malware scan.

When I tried to run the windows update troubleshooter it said "diagnosing problems" but never fixed them and I was still unable to install the update after running the trouble shooter.

Any help would be appreciated.

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.

0 comments No comments

513 answers

Sort by: Newest
  1. Anonymous
    2024-02-23T04:26:14+00:00

    All Microsoft has to do is (a) delete the update that doesn't work and (b) replace it with one that does - in the words of Maestro Cecchetti in order to learn the proper execution of a step you 1st have to admit that you don't know how to do it. All they have to do is determine what this update is supposed to do and place that solution in a different update. The big mystery is this - what exactly is this update supposed to do beside attempting to induce us to use Edge when we don't want to . It obviously isn't indispensable since everyone that can't load it is still using their computer - so unless they can show cause of why they persist with it they ought to just delete it.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-02-23T02:59:30+00:00

    Your right, and there is no way to bypass this update. It just has the annoying "red" exclamation point along with the "Retry" button. You can click that button a million times and nothing is going to change it from failed to success. Now I see why a lot of people don't do Windows Update. The are terrified of having their systems lock up on them.

    Let me know if you every figure out a way to resolve this annoying problem.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-02-23T02:22:29+00:00

    It's now February 22, 2024 and this still seems to be a problem with running the update KB5034441 with Windows 10. How long do you think it will take for Microsoft to fix this problem. Reason I'm asking is because at this point whenever I select "Check For Updates" I will repeatedly get this error message which says: "Try Again Later". Is there some way to mark this KB patch number so that it won't attempt to install whenever I run "Check For Updates"? I'd hope by now Microsoft would have resolved this problem by now.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-02-22T00:12:02+00:00

    I just tried all the tricks noted with the WinRE Partition on #6 Win 10 PC and had the same results of No change in the Error. I have had one out of six actually complete this update and I have no clue why. Lets see what MS can do to fix this. Not sure they want to fix it at all as they have Win 11 issues that take 99% of their efforts. Waiting and Wondering.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-02-21T12:44:48+00:00

    I just tried once again to do this security update - same error message. I have since gone into the options and changed it to pause updates for 35 days. Hopefully, MS can work on getting this fixed by then. They certainly haven't been making any progress on it up to this point.

    I was initially concerned that something I did caused the problem. My Windows 10 PC could not be upgraded (?) to Windows 11 and I ran a check to see why. The only thing holding it out was that it was running Legacy and I needed to change it to UEFI and Secure Boot capable, which I did after watching several YouTube videos. After that, I checked for any Windows updates and that's when this error appeared. After reading through 15 pages of this thread I see it is not something I did that is causing the problem.

    Also, I think I will wait on the Windows 11 update since I learned that Windows 10 will be supported until October, 2025. For some reason, I thought support for that ended at the end of 2023.

    Was this answer helpful?

    0 comments No comments