Issue with KB5001716

Topic

New Reply

I was able to confirm this behavior on two fully patched Windows 10 Pro systems.

Last evening …

1. Check for updates in Windows Update
2. KB5001716 downloads and installs successfully.
3. Check for updates again, and instead of showing ‘up to date, the same update tries to install again and fails
4. The update does not show up in ‘Installed Updates.’ It shows up the ‘Uninstall or change a program” list
5. Uninstalled the update
6. Windows Update then installs the update again successfully, 2 times (successfully installed 03/05/24) … Once for ‘2023-10’ and once for ‘2024-03’
7. Shut down the computer overnight.
8. Booted up this afternoon, and WU automatically checks for updates and shows the ‘Error Encountered’ message (Failed to install 03/06/24, 2x)

There seems to be no way out of this insane loop.

Thoughts?

Reply | Quote

Replies

What’s the exact error code?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

See attached screenshot. I also sent a message to the Patch Management list with screenshots.

1 user thanked author for this post.

Rob Kay

Reply | Quote

Try resetting Windows Update.

Copy the following code into Notepad, and save it as WUReset.bat on your Desktop.

Right-click and Run as administrator.

 

net stop cryptsvc
net stop bits
net stop wuauserv
::
reg delete “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v SusClientId /f
reg delete “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v SusClientIDValidation /f
::
if exist c:\windows\SoftwareDistribution.old rd /s /q c:\windows\SoftwareDistribution.old
if exist c:\windows\System32\catroot2.old rd /s /q c:\windows\System32\catroot2.old
::
rename c:\windows\SoftwareDistribution softwaredistribution.old
rename c:\windows\System32\catroot2 catroot2.old
::
net start cryptsvc
net start bits
net start wuauserv
::
wuauclt /resetauthorization /detectnow
::
PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()

 

 

Reply | Quote

I don’t believe the issue is with Windows Update. This behavior is reproducible on two (fully-patched) Win 10 Pro machines. The issue is with the update and/or the update not registering correctly after it is first applied. Resetting WU won’t fix that.

I can ‘fix’ the issue by uninstalling the update. Then WU will reinstall it with seemingly no issue. If you then ‘check for updates’ again, the error occurs because WU is trying to install the same update again that has already been installed. WU is not seeing that the update was already applied successfully.

Reply | Quote

Hide it.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Sueska

Reply | Quote

Turns out … this is being reported elsewhere:

https://www.youtube.com/watch?v=NZXp9U7BNFs

https://www.youtube.com/watch?v=vN1nwAtSSjs

https://www.tenforums.com/windows-updates-activation/211685-issue-kb5001716-update-march-5-2024-a.html

https://www.windowslatest.com/2024/03/07/microsoft-rolls-out-windows-10-kb5001716-and-it-fails-with-0x80070643/ > This article seems to indicate the issue is that after the 03-2024 version is installed, WU then tries to install the 10-2023 version thus triggering the error.

At any rate, feel pretty confident this is a MS server-side issue and not something that can be fixed locally (although I guess one could hide the update, but this is a KB that is occasionally re-released so you don’t want to hide this one indefinitely).

 

Reply | Quote

On Windows 10 22H2 Through Parallels On Macbook M3 Pro:

Update KB5001716 fails ton install with error code 0x80070643, same behaviour as KB5034441 with same error code.

 

As usual we are expecting that Susan will come up with a solution.

Reply | Quote

I am running Win10 22H2 on one old Dell laptop (hardware install), one Kaby Lake i7 iMac4K in a Parallels 18 VM, and one old Ivy Bridge i7 15″ MacBook Pro also in a Parallels 18 VM. See my experience with KB5034441 at #2628205 and #2629983. I was not offered KB5001716 with the last updates.

I am running Win11 22H2 in Parallels 19 VMs on an M1 MacMini and a 16″ M2Max MacBook Pro. Have not had partition-size problems on either of those, although there is no separate update associated.

1 user thanked author for this post.

Rob Kay

Reply | Quote

howardagoldberg wrote:

feel pretty confident this is a MS server-side issue

I had both the 2023-10 and 2024-03 releases hidden in WAU Manager.

Just installed 5001716 (2024-03 release only) on a fully patched Windows 10 22H2 system…rebooted, and the 2024-03 version was installed.

Ran WAU Manager again looking for updates, and it did not show as “to be installed”.

So it doesn’t appear to be a server-side issue in my case.

 

Reply | Quote

Windows 10 KB5001716 install fails with 0x80070643 error but a fix seemingly exists – Neowin

1 user thanked author for this post.

lmacri

Reply | Quote

https://www.reddit.com/r/Windows10/comments/1b7sv67/comment/ktn8dm9/

”
23h ago
FOUND THE SOLUTION: ITS BECAUSE ITS ALREADY INSTALLED….. Go to settings, click apps, go to apps and features , scroll down till you see the update already there installed and uninstall it…go back into windows update and check for updates and it will re install it and then your done it will give you that nice green checkmark your waiting for. LET ME KNOW IF IT WORKS…WORKED FOR ME

https://www.reddit.com/r/Windows10/comments/1b7sv67/comment/ktlomww/
”
Apax-Legomenon
•
1d ago
•
Edited 23h ago
Same. If you notice, you most probably have the update already installed. I think that’s why we get the error. It’s the update that is shown separately in Apps & Features, version 8.94.0.0

It’s one of those features that help your Windows 10 with the update-process all-around.

Unless this one now is slightly newer version or something (for instance, it could be 8.96.0.0). I don’t know. I’ll try to simply uninstall from apps & features the installed update to try again.

EDIT: It did work. It’s now has been installed normally. However, it’s still the same version, 8.94.0.0. I guess a mistake from Microsoft’s part. However, searching for updates, it still gives me the “new” along with the error, again. Weird stuff”

Reply | Quote

howardagoldberg wrote:

I don’t believe the issue is with Windows Update. This behavior is reproducible on two (fully-patched) Win 10 Pro machines. The issue is with the update and/or the update not registering correctly after it is first applied. Resetting WU won’t fix that.

I can ‘fix’ the issue by uninstalling the update. Then WU will reinstall it with seemingly no issue. If you then ‘check for updates’ again, the error occurs because WU is trying to install the same update again that has already been installed. WU is not seeing that the update was already applied successfully.

Sounds about right. It keeps trying to install 2023-10 (KB5001716) and it’s already installed. I just hid it. Why keep trying to installing it when it’s already installed?

Reply | Quote

Although I show ‘2023-10 Update for Windows 10 Version 22H2 for x64-based Systems (KB5001716)’ was ‘Successfully installed on 3/6/2024’,
I am unable to uninstall it because KB5001716 is not listed under the updates to uninstall.

Reply | Quote

Is it listed and un-installable under Settings, Apps, Apps & features?

Reply | Quote

redwolfe 98 on Bleeping Computer reports that Microsoft has fixed the problem

https://www.bleepingcomputer.com/news/microsoft/windows-10-kb5001716-update-fails-with-0x80070643-errors-how-to-fix/

Reran Windows Update and error which showed up before is gone

4 users thanked author for this post.

Rob Kay, TechTango, lmacri, Alex5723

Reply | Quote

Yes. The problem seems to have been resolved, KB5001716  installed OK on 2 windows 10 PCs this evening.  There are now 2 instances showing in update history. Now if only MS would also fix 5034441 and the photo app.

Reply | Quote

Finally got around to unpausing WU on my Win10 Home pc today. Rushing to get FEB 2024 updates installed and WU paused before MAR 2024 updates became available tomorrow (Patch Tuesday). Was not expecting KB5001716 to download but it successfully installed without any error messages.

Reply | Quote