"2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in 64-bit W10 Pro.

Hello, I am glad I am not the only one having an issue installing "2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)". Every time I try to install I get this error "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80070643)" Not sure what it is, I have tried tons of different methods, from disabling anti virus, all non Windows services, checking for corrupt system files, nothing is working. I wanted to try manually installing the update, but (KB5034441) does not show up in Microsoft Update Catalog. What I was able to do is get the update to download onto my computer, by stopping wuauserv and stopping bits. Then deleting all the data in C:\Windows\SoftwareDistribution then turning wuauserv and bits back on which redownloads all the files in C:\Windows\SoftwareDistribution. That allowed Windows update to download KB5034441, but it errored out during the installation process. Any help would be appreciated.

PS: I am using 64-bit W10 Home

Ugh. 2 Windows 10 Pro systems fully patched other than this. Neither can run 11 or they would be. Both use Bitlocker in password mode.

The Haswell system installed it fine apparently. The ~2 year newer Skylake system fails.

I tried DISM and SFC before searching and finding this, and they found no problems.

It sounds like at least this bug affects my PCs' security if it's physically compromised, but not my online security?

If I'm understanding that right, I can at least keep using my PC, but it still needs to get fixed.

What's bad is I'm aware of no way to report this.

Oh, the skylake PC does have a TPM, but I'm not using it for bitlocker, if that matters.

They want you to increase what you have by default, 563MB, up 250MB more.

I just increased mine to 1000 MB.

If your partition is on the front, you'll end up deleting that, shrink you primary partition by 1000MB, then add the new recover partition.

This is a horrible fix to go through but it did work for me.

Jeff

Windows Update KB5034441 is a security update to the WinRe environment, but people are running into problems trying to get it downloaded and installed. KB5028997 tells how to resize your recovery partition so that this update can be installed, but it applies only to Windows 11 computers. I am in the same boat as John Dow 987654 and ULtraGreG. I need a workaround that applies to Windows 10 computers, if there is one.

I have Windows 10 which I understand is supported thru 2024. Like the others, I need a simple (NOVICE) solution to this problem update (KB5034441).

Please advise for those of us that are not "Tekies", and don't have administrator's access! Looking forward to Microsoft assistance with this security problem caused by the original Microsoft security designers who created this risk in the first place by ignoring the possibility of the risk this update is attempting to mitigate.

Win10 is suppose to be supported until October 2025 but with the way MS is putting out updates like this I would not care if they stopped sooner. Personally I am getting tired of chasing rabbits down holes every patch Tuesday and I do not call that support. I would not hold my breath waiting for MS to do anything about this anytime soon. Maybe we will get a fix next patch Tuesday. Good luck.

Windows Update KB5034441 is a security update to the WinRe environment, but people are running into problems trying to get it downloaded and installed. KB5028997 tells how to resize your recovery partition so that this update can be installed, but it applies only to Windows 11 computers. I am in the same boat as John Dow 987654 and ULtraGreG. I need a workaround that applies to Windows 10 computers, if there is one.

I have Windows 10 which I understand is supported thru 2024. Like the others, I need a simple (NOVICE) solution to this problem update (KB5034441).

Please advise for those of us that are not "Tekies", and don't have administrator's access! Looking forward to Microsoft assistance with this security problem caused by the original Microsoft security designers who created this risk in the first place by ignoring the possibility of the risk this update is attempting to mitigate.