Windows Update Error

I have run Windows Update daily with no issues; mostly to make sure that my Windows Defender is current. But today when attempting that, I encountered the error code: 0x80070643. It still won't install after multiple retrys. Upon checking, it appears that the 2023-10 update for Windows 10 version 22h2 for x64-based systems (KB50001716) not installing is causing the problem.
Looking back in my update history, I found that that particular update was successfully installed on 10/4/2023.
I ran the Windows Update troubleshooter, and found "Troubleshooting couldn't identify the problem". All of the checks inside found "issue not present". A reboot didn't help either.
So I'm guessing I have to somehow remove that update from attempting to install a second time. Sorry for the long winded post, and thanks for any help.

 

First, if you have not changed the defaults, there is no need for you to manually run Windows Update for Microsoft Defender (formally Windows Defender) updates. Defender automatically checks for updates several times a day. Again, this is the default setting. So Defender is essentially, always current.

By default, Defender is constantly running in real-time, always checking for threats. But it also periodically runs additional scans and it always checks again for updates before running those scans. And, if you manually initiate a scan, it checks again before starting that scan. So there is no need for you to keep checking.

If you are worried something might slip by you (the user is ALWAYS the weakest link in security) or Defender, I recommend manually running a scan with a secondary scanner. I generally recommend Malwarebytes for that. And that recommendation stands regardless your primary security scanner of choice. Everyone should always have and periodically scan with a current secondary scanner - for peace of mind if nothing else.

For the record, Defender has been my primary scanner for over 10 years on all our computers here. Not once has Malwarebytes ever found anything malicious Defender let in. Not once.

As for your error, this is a known problem. I am surprised you are only discovering it now since it first surfaced and widely reported in early January.

Back when W10 was installed, a small "WinRE" recovery partition was created on your boot drive. It was initially thought its size would always be big enough. But even Microsoft cannot see that far into the future and now, with that update, it was discovered a bigger recovery partition was needed. Sadly, the update needing it didn't know how to make it happen. Hence the error.

You have a few options. One is to simply wait it out and eventually [hopefully] Microsoft will release an update that automatically fixes this. There is no harm in leaving this until that happens. Or you can search the web for tutorials to learn how to manually resize your partitions. I found the one from TheWindowsClub to be good. Or you can use a partition manager program like AOMEI Partition Assistant Standard (free for home, non-commercial users). You can also use Disk Management in Windows.

Or you can see this Microsoft KB article, scroll down to the section titled, "0x80070643 - ERROR_INSTALL_FAILURE" check out the two options there.

A word of caution: While I have not heard any reports of corrupt drives or missing data cause by resizing this partition for this problem, it is always a possibility something could go wrong. A drive might decide to fail at that moment or there could be a sudden power outage. So it is always wise to ensure you have a good backup of any file you don't want to lose - something you should have anyway.

 

Thank you for the quick reply.
I just dread digging too deeply into my system, and am content to leave well enough alone.
So if I understand your reply correctly, I can simply discontinue to manually check for updates, and Windows will automatically do the necessary updating for me?. The error will continue to show up on Windows Update, but just ignore it? And hope that at some point in the future some techie at Microsoft will decide to address the issue, and make my error message go away? Thanks.

 

If you have not dinked with any of the Windows Updates default settings, that is exactly what will happen. Defender and Windows will stay current - a good thing.

Well, there is one caveat. Defender will stay current regardless but Windows Update tries to run when you are idle so it does not bog down your computer when you are trying to use it. If you regularly remove power from your computer when you are done using it for the day, Windows may not be able to keep itself updated on a timely basis. For this reason, I recommend you simply let Window and your computer go to sleep when you are done using it. If you prefer, you can still "shutdown" through the start menu. That technically is still a standby mode and Windows can still update (typically 2 - 3 in the morning). But if you unplug the computer from the wall, flip the master power switch on the back of the computer, or if your wall outlet is switched (as typical in the UK) and you switch it off, then updates may be delayed.

For the record, I never shutdown or remove power from my computers, except to do maintenance or if I will be away from home for several days. I always just walk away and let them go to sleep.

As far as this issue eventually going away with a future MS update, "in theory" that is true. Or at least that is the plan. But since partition sizes are done at the hardware level, and typically BEFORE the operating system comes into play, the OS may never be able to do this through an Windows Update. I quickly add, this is WAY out of my area of expertise (I'm an electronics technician, not a programmer). I do know Windows does have embedded tools to manage partitions, I just don't know if a Window Update can do it. I hope so because there certainly are many, perhaps millions, in the same boat as you.

 

Thanks again.
As you have told me, it isn't necessary to manually run Defender scans, but my routine has been to run a full scan once weekly during nighttime hours. Then followed by an Microsoft Defender offline scan, which will reboot when finished. I've only had 2 instances where anything was found, but was quarantined and deleted. I too have used Malwarebytes, but it never found anything that Defender missed, so I uninstalled and quit using it.
I too only shut down when I'm going to be away from the house for an extended period of time, which hasn't occurred much lately. Do you think that the weekly offline scan and reboot is advised or necessary? Or maybe just a periodic reboot instead?
So my plan going forward will be to quit manually updating, and let Windows take over. Then hope for the best. Thanks again for answering my questions.

 

I use MBAM FREE and would not be without it. It looks for things that Defender doesn't look for. I have seen it pop up that it has blocked something a few times along the way. But that is just my opinion

 

No. Defender runs scheduled scans once a week anyway. And again, it is constantly scanning everything coming in. So additional scans are actually redundant and for peace of mind.

The need for periodic reboots are a thing of the past. Windows rarely needs it. In fact, I would say Windows almost never needs it. But sadly, some programs running with Windows may not release resources properly and so, because of them a reboot may help - though terminating those processes in Task Manager would probably do it.

It is not uncommon for a Windows Update, or some other program update to require a reboot. So one will likely happen soon anyway.

I say, if the system "feels" normal to you, there's no need for a reboot.

Well, before believing it caught something we think Defender should have, we need to research those items carefully.

I chose my words carefully above when I said Malwarebytes has never found anything "malicious" Defender let in. But it has found things.

I use Malwarebytes Free on a couple machines here, and Premium on this and a couple other systems. Malwarebytes has occasionally blocked access to a few sites. But investigating further showed the site was not secured to the latest standards - for example, http and not https. Or it contained "unknown" objects, and to err on the side of caution, it tagged them. But scans with Website Safety Checker or Norton Safe Web showed they were safe.

I have also had Malwarebytes find a couple safe and "wanted" PUPs (potentially unwanted programs). But again, they were actually safe. So I consider all these "false positives". False positives are not really good - but MUCH MUCH better than false negatives (calling something malicious "safe".) So, for my secondary scanner, I can accept a false positive now and then.

 

Thank you Bill. You have answered all of my questions, plus given me some valued opinion and advice. Frank

 

Hi Bill,
I'm not sure what happened, but my problem fixed itself. I was able to manually run update, and it updated ok. Thanks again.

 

Well, back in my old radio maintenance days, we used to call that "FM" - but it was not for frequency modulation but for a certain type of magic!

That it seems to be sorted and thanks for coming back and posting your follow-up.