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.
You are right. I noticed the same thing on my MBR drive / older PC. I corrected as you did. Some of the online videos do correct this procedure for creating and identifying the Recovery Partition. All my GPT drives / newer PCs did identify the Partition right. Hopefully Microsoft will get this resolved on their next release.
I see it is now entirely empty and so while I might have a recovery partition, there seems to be nothing there to recover from and this is an elderly machine. God knows where any media would be. Maybe the next thing to look at is how to create something in the recovery partition!
I have already tried to explain this. Windows RE has been enabled in C:\Recovery\WindowsRE and could easily be updated there, so KB5034441 could install.
Move Windows RE from there to the recovery partition by running
reagentc /disable
reagentc /enable
I noticed the same thing. It is a mystery what the MS folks are doing with this Partition since it is essentially empty on Win 10 MBR, Win 10 GPT and Win 11 GPT PCs. Perhaps they are storing some kind of instructions or smaller files there. I set all my PC's (MBR and GPT) up to 1024MB for the Recovery Partitions. I did notice the improper setting of the ID=27 on the MBR drives when I followed the MS Instructions. Some of the online videos did correct this error "those titled Creating a Recovery Partition in Windows 10. It is pretty easy to run the Set id=27 from Diskpart if needed.
The strange thing is my older PC completed this troubled update without a Recovery Partition identified? I can't explain that. The creating of a larger Primary Partition (not identified as Recovery) seemed to make it happy. It is best to have your Recovery Partition not displayed in File Manager, away from folks who might try something strange.
Moral of the story, be sure you have a Windows Recovery (full files and programs) on a separate Disk or Thumb. A newer Thumb Drive of 1-2TB with good Recovery Software will do this job easily and can be kept off-site, just in case.
I noticed the same thing. It is a mystery what the MS folks are doing with this Partition since it is essentially empty on Win 10 MBR, Win 10 GPT and Win 11 GPT PCs.
The partition is empty only after completing the MBR version of KB5028997. The partition is empty by default after running the disable command as Windows RE gets preserved on drive C. Every time the disable and enable commands are run, the recovery image changes its location. It fails to return to a partition that is not actually a recovery one and gets deployed on drive C instead.
The strange thing is my older PC completed this troubled update without a Recovery Partition identified?
With no recovery partition dedicated, the recovery partition is drive C which always has the necessary space available.
The strange thing is my older PC completed this troubled update without a Recovery Partition identified? I can't explain that.
I believe the explanation is that if there is no recovery partition, this 'whatever it is doing' element of the update is skipped hence no issue over partition size as that whole area of 'whatever is being done' simply doesn't run
