WHERE IS PRESENT REAGENTC/DISABLE AND REAGENTC/ENABLE
Windows update (KB5034441) Error (0x80070643)
![](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)
Anonymous
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.
513 answers
Sort by: Newest
-
Anonymous
2024-04-14T07:53:58+00:00 -
Anonymous
2024-04-14T07:50:21+00:00 HOW TO SOLVE THIS PROBLEM ?
-
Anonymous
2024-04-13T19:53:00+00:00 I guess it is the
reagentc /setreimage /path ...we need to use for this after assigning a drive letter to the volume on the recovery partition. Why Microsoft did not use this technique to apply the update initially nor suggested this as a workaround?
It's only this:
reagentc /disable
reagentc /enable
with the new recovery partition in place. The Windows RE addresses the recovery partition automatically.
But it can't be the official solution as it requires BitLocker disabled.
-
Anonymous
2024-04-13T19:23:38+00:00 I don't believe it. I might have figured this out. At least for me.
I have 2 desktop PC's that are still running Windows 10 32-bit which was giving me this error to update for months.
I think it has to do with the video card drivers where something is conflicting and giving an error.
So I tried disabling the video cards (one AMD Radeon in one pc and the other a NVidia GTX 1050 in the other) in Device Manager, rebooted and successfully installed the update. I then re-enabled the graphics drivers.
At first I tried to change the boot graphic card in the CMOS to the IGfx (internal on-board graphics card) from the PCIe slot1 (Nvidia card) and swap my HDMI connector to connect to the Intel GC, but that didn't work until I disabled the NV card in my device manager and did the process in the above paragraph.
Hopefully it works for you. What a pain! Finally!
Unfortunately I may have to do this method with every subsequent update. Geez.
-
Anonymous
2024-04-13T12:55:32+00:00 Did you return Recovery Environment back to RE partition after the update applied? Did it fit? I guess it is the
reagentc /setreimage /path ...we need to use for this after assigning a drive letter to the volume on the recovery partition. Why Microsoft did not use this technique to apply the update initially nor suggested this as a workaround?