Bork Tuesday, Any Problems Yet?

you ask now for an update from october'23? 6 month later?
idd you need to change something according your update strategy.

please try marked solution from "Tekkie Boy" if still not success.
https://answers.microsoft.com/en-us...3/bdc87bcb-6107-4da2-8cca-ac34c3e5dccb?page=2

 

I regularly update my comps and this update came in today. It's simple as it is.
The marked solution didn't work, it returned with info that the update is already installed. So I hit the mark saying it is a mystery update. ;-)

 

No luck here. Two Win10 machines, one Pro, one Home.

 

OK, thx for the info. I’m quite relieved MS needs to do their homework.

 

Thanks to that Reddit link, I have uninstalled that Oct 23 update, and will see how I go when I resume Windows Updates:

 

(Now) Gone but not forgotten...

 

if KB5001716 - have or had you issues with KB5034441/KB5034440?
if yes then its also caused by WinRE, any other update concerning winre will fail for you.

 

This didn't work. Win 10 stated it was already installed.

Here's my story on this recent KB5001716 bork.

Installed it w/o issue last night when Eset informed me a Win Update was available.

This morning after system restart, Eset again informed me KB5001716 update was available. Opened Win Updates and checked for updates. KB5001716 again started downloading and then installing. This install crapped out with 0x80070643 error. So did three additional attempts. Then I did Win Software Distribution folder delete and re-create per this article: https://www.majorgeeks.com/content/page/windows_update_failed_to_install_with_error_0x80070643.html . Important: Do Software Distribution folder re-name and delete processing only! Re-booted Win 10 and borked KB5001716 gone.

I just noticed Eset is again informing the update is available but I have no intention of doing a manual Win 10 update check again.

 

Some additional info on this recent KB5001716 update. It is listed in Win Program updates; not in Installed updates section. Something is very wrong presently with Win Update processing.

-EDIT- I just checked my Win 10 Reliability history from yesterday. It did a double update for KB5001716; one shows in Program updates and one for Installed updates. Again, something is very wrong with Win Updating it appears.

 

please dont use additional updaters, they probably will break your system or software with wrong versions or wrong languages. for windows let windows decide, no tweaker for update options, in special for home users.

what i dont get that you all get that update 6 month later as me. this machine in October, the other one in november (because its rarely used, its most times working on win11) if you can find out why you received it such late, then you have possible the cause why it fails now.

and ofc have always in mind, that other antivirus can break windows anyway, updates are common, and eset is no exception from this behavior. for firefox i know that eset broke firefox in several urgent ways and made it no longer usable.
i dont remember when i had eset installed for the last time, maybe v3 but it already had this stupid update checker and it was one of the first to get disabled.

see image

but, the KB article says files from february
https://support.microsoft.com/en-us/topic/kb5001716-update-for-windows-update-service-components-fb9dd3d3-d702-4f8a-af10-b9551cfa6e13
aha, ok, is released regularly. current is for windows 1004 to 22H2, no older.
https://www.deskmodder.de/blog/2024/03/06/kb5001716-windows-10-update-komponenten-werden-aktualisiert/[/url]
and that article (german) says, that its listed again although already installed.
it says too that the februar patch day is mandatory for this update.

 

I'm not taking any countermeasures. I believe that the March patches, due out next Tuesday, will somehow handle/resolve this.

 

I finally got this KB5001716 update mess resolved.

Referencing the comments in the above linked Reddit article, I opened Win 10 22H2 Settings -> Apps & Features. I then uninstalled the 03-2024 KB5001716 update. Note: This takes a while to run.

I then opened Win Updates and re-tried the failed 10-2023 KB5001716 update. Win downloaded and installed in the following order; 10-2023 KB5001716 update and 03-2024 KB5001716 Update. Green check mark for Win Update status;



It appears what caused this mess is the 03-2024 KB5001716 update being installed prior to the 10-2023 KB5001716 update which was my case. That is Microsoft borked the loading of this this on their update servers.

 

Do you have 10 Pro? I've got 10 Home and Apps & Features doesn't list Windows Updates and neither does Programs and Features in Control Panel. In fact, I can't find where anything named KB5001716 is installed on my system, even in the Uninstall Updates list in Settings. Oddly though, Windows Update MiniTool shows "2024-03 Update for Windows 10 Version 22H2 for x64-based Systems (KB5001716)" as installed but when I try to uninstall it it fails and says it can't uninstall because it isn't installed on my system.

When I check for updates, Windows Update shows 2023-10 (KB5001716) as available but it fails to install. My confidence in MS has reached an all-time low, if that's even possible.

 

Looks like the 10-2023 KB5001716 update issue not fixed after all. When I went to manually check for Win Updates, it downloaded it again with update failing as previously.

Looks like the problem is on the Microsoft update servers since Eset keeps informing me of the 10-2023 KB5001716 update although its now installed. I am also starting to believe this has something to do with the previous manual Recovery partition re-create since the failed 10-2023 KB5001716 update install error code is the same associated that fiasco.

Has anyone contacted Microsoft about this problem?

 

Okay, great. Got it uninstalled and then checked again. The 2023-10 and the 2024-03 both installed successfully. Then I checked again and it tried to install the 2023-10 again but failed. Looks to me like MS is sending a duplicate of something screwy. In any event I'm just going to hide the one that won't install and call it a day. Appreciate the help.

 

if you call on me, i think not. you haven't got in october, you cant get it now. why to fix something which is not clear and seems not broken? the next thought is - what makes your system so special that you always have failure from time to time with windows updates? or never get them?

for kb5034441 i can say, that windows is inconsistent when its partition is moved. my second machine got win11 and thus win10(1) and win10(2) got moved, reagentc links to disk0/part1 which win11 now and not compatible i guess. those win10 are neither nor vital, anyhow both got the kb5001716 as written.
my next steps are to remove both win10 and reinstall another win10 from scratch parallel to win11 (main os). this means only a day work, experience, and workflow is trained here. to mention that i never used an different antivirus on that machines, or other intruding security software. at least if you have no option to compare untouched windows with a daily-work windows would mean you never will find out what's going wrong and need tips and tricks. thats why i had an untouched win10pro and limited user account to check my programs against circumstances.

btw MS already know about
https://answers.microsoft.com/en-us/windows/forum/all/windows-update-error-0x80070643-for-kb5001716/7796e1a6-b1b7-49fa-a1ea-570f5fa9926f

 

I yesterday got a 2024-02 Cumulative Update Preview for Windows 10 (KB5031445).

Is that right? (It's March...)

 

I would wait for the regular monthly updates due out next Tuesday.

 

@stapp & @itman I’m sorry for your waisted time.

 

BleepingComputer just published the 10-2023 KB5001716 update fix I posted previously: https://www.bleepingcomputer.com/ne...date-fails-with-0x80070643-errors-how-to-fix/ . Appears Abrams didn't attempt to manually check for Win Updates again and observe the issue reoccur.

Also with the TechNet thread now approaching 6 web pages of postings on this issue, MS damn well knows there's a problem and is totally ignoring it. Appears to be more Win 11 forced upgrade harassment to me.