This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
This fix didn't work for me. Everything was fine until 'format quick fs=ntfs label="Windows RE tools"'. This encountered an error "The parameter is incorrect. See the System Event Log for more information.". I checked the System Event Log, but there was not even a mention of the error. I should point out that this is an MBR disk.
Same persistent problem . When will Microsoft sort this out ?
It's been a month.
By experimentation, I found a resolution for the formatting error for the newly created recovery partition myself. If I booted from the MBR disk containing the recovery partition then the quick format would fail with "the parameter is incorrect". However, if I booted Windows from another disk (I have dual boot disks for resilience) then the formatting of the recovery partition worked fine. After formatting the partition I did need to set id=27 again to mark it as a recovery partition.
Having successfully increased the size of the recovery partition from 460Mb to 710Mb I optimistically retried the installation of KB5034441. To my dismay it failed in exactly the same way as previously.
What is clear to me is that Microsoft's suggested workaround for the KB5034441 problem is not a guaranteed solution. Of course, it is highly undesirable for end users to have to resort to such manual partitioning in the first place. Still waiting for a proper fix for this issue.
I don't want to repeat myself, but the workaround that I have suggested here definitely helps. It is a bit risky. But if you follow the step by step guide from Microsoft this should not be a problem to execute.
I do have to criticise the Microsoft approach a little bit, since they asume that 250 MB more should suffice.
In my case I increased the recovery partition from 530MB to 3000MB and the Update went through like butter... :-)
