Answered by:
Windows Server 2019 Refuse installing KB4495667 Update.

Question
-
Hello everyone,
Maybe someone that is well-versed knows the cause of the occurring error. I've tried googling my solution without avail, sadly.
Windows Update will not install update KB4495667 (2019-04 Cumulative Update For windows Server 2019), no success either when downloading and attempting to install it manually.
The error I get prompted with; Installation Failure: Windows failed to install the following update with error 0x800706BE.
Two other problems seem to correspond with the issue above, which is: Faulting Application name: wuauclt.exe and TiWorker.exe.
What I done thus far;
- Clear Windows update Cache folder.
- Server Reboot.
- Used Windows troubleshoot (Found nothing wrong with Windows Update)
- sfc /scannow
- dism /online /cleanup-image /restorehealth
Hopefully someone can assist me a little, that would be awesome. :)
- Edited by Master-DXT Sunday, May 5, 2019 1:18 PM
Sunday, May 5, 2019 10:57 AM
Answers
-
I found that after 2019-05 installed successfully this week it was still being offered as an update - I completely reset the Windows Update files on each machine and it's now gone.
- Proposed as answer by Queeg505 Tuesday, May 21, 2019 7:47 AM
- Marked as answer by Master-DXT Saturday, May 25, 2019 4:49 AM
Sunday, May 19, 2019 8:43 AM
All replies
-
Same issue here with my 2019 Servers. While I don't have resolution, at least you know it's not only you.
I did have this issue in the past with a previous update. The issue resolved itself when the next patch was released (for us, it will likely be 5/14/19).
Monday, May 6, 2019 12:43 PM -
Then all we can do is wait, sadly.
Hopefully the Cumulative Update did not obliterate my Windows Server installation.
- Edited by Master-DXT Monday, May 6, 2019 7:32 PM Edit
Monday, May 6, 2019 7:30 PM -
Hi,
Make sure the latest SSU (KB4493510) is installed.
Also, try to reset windows update component:
1.Press Windows Key + X on the keyboard and then select “Command Prompt (Admin)” from the menu.
2.Stop the BITS, Cryptographic, MSI Installer and the Windows Update Services. To do this, type the following commands at a command prompt. Press the “ENTER” key after you type each command.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
3. Rename the SoftwareDistribution and Catroot2 folder using the following commands:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
4.Now, let’s restart the BITS, Cryptographic, MSI Installer and the Windows Update Services. Type the following commands in the Command Prompt for this:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
5. Type Exit in the Command Prompt to close it.
Best Regards,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Wednesday, May 8, 2019 2:59 AM -
Thank god it just not just me. been trying for 2 days to figure out why it doesn't work....Wednesday, May 8, 2019 12:12 PM
-
The mentioned update is already installed and tried what you put down. Nonetheless, thank you.
Edit;
Not going to wait around for a solution so I set-up a fault-tolerance and demote my broken DC. :P
- Edited by Master-DXT Thursday, May 9, 2019 5:49 PM
Wednesday, May 8, 2019 1:55 PM -
I'm seeing the same on many 2019 servers, old and fresh installs alike, and also on full and core servers.
Saturday, May 11, 2019 9:20 AM -
Ditto Im getting the same issue, any updates on this?Sunday, May 19, 2019 8:15 AM
-
I found that after 2019-05 installed successfully this week it was still being offered as an update - I completely reset the Windows Update files on each machine and it's now gone.
- Proposed as answer by Queeg505 Tuesday, May 21, 2019 7:47 AM
- Marked as answer by Master-DXT Saturday, May 25, 2019 4:49 AM
Sunday, May 19, 2019 8:43 AM -
I found that after 2019-05 installed successfully this week it was still being offered as an update - I completely reset the Windows Update files on each machine and it's now gone.
I can also now confirm that stopping the Windows Update service, clearing the contents of the Windows\SoftwareDistribution folder, restarting the server and then re running check for updates resolves this issue.Tuesday, May 21, 2019 7:47 AM