TL;DR summary: all my Windows 10 computers fail on attempted install of this major update. Why? Is it a known bug? What does one do about it?
[/TL;DR]
I have virtual machines (Parallels, if you’re curious). I have a Windows 10 32-bit environment that was created from a previously existent Windows 7 Ultimate, and when I later needed a Windows 10 64-bit machine, I googled and downloaded an installer that overwrote it with the 64-bit OS.
WAY TMI TECHNICALS:
These guest OSs were originally run on Parallels 13. Time moved on and I got newer physical hardware running newer native operating system, and upgraded to Parallels 18 on the new box. The Windows 10 virtual machines were the same critters but at this point they diverged, with me being more lilkely to keep the copies that run on older Parallels 13 up to date and the copies on Parallels 18 get ignored and lag behind in their updates. Finally, I installed the newest MacOS (Sonoma, aka MacOS 14) and for compatibility put Parallels 19 on that and once again had clones of the two Windows universes converted to Parallels 19 format.
[/WAY TMI TECHNICALS]
That’s SIX separate Windows 10 environments: Three 32-bit Windows 10 (Parallels 13, 18, and 19) and three 64-bit Windows 10 (Parallels 13, 18, and 19).
I hit this error 0x80070643 trying to install this specific update on one of them, retried a few times, shrugged and went on to the next virtual machine and got the same error on the next Win 10 VM. Sometimes it first involved catching up on four or five updates that preceded that, but that’s where they all ended up.
Googled, learned how to reset the Windows operating system’s sense of “health”, doing all the things mentioned here and here and even the batch file command for Windows 11 (mentioned as a possible solution to Windows 10 update errors as well) cited here. Nope.
0x80070643, asshole, 0x80070643, you can’t update, no security update for you!
I’m just a Windows hobbyist and don’t really know my way around Windows. What do I do now? Can I get tech support? Is there a commonly known thingie that Windows folks know to do when this happens?