KB4601318 fails to update, fails at 24% Windows Server 2016

Kevin S 96 Reputation points
2021-02-11T00:15:10.047+00:00

Hello,

I have 3 virtual servers that have this exact same issue where when I try to update KB4601318, it stalls at 24%. The servers are 2016 servers, I have disabled anti-virus, I have rebooted, followed instructions on this blog, added RAM and enabled and disabled firewall. I have updated 15 other servers in my environment successfully, running the same antivirus software, same kind of setup. The servers all have 2 or 4 processors, 8 GB or 16 GB of RAM and at least 200+ GB of available disk space. No errors in the event viewer that I can see.

I've let the update run on these machines for 2 hours and what happens is that it will install KB890830 and KB4601392 on all of these machines but not KB4601318 on any of them. It gets stuck at 24% and then eventually stops and reads "KB4601318 is available" "Updates are ready" and Download button is enabled. If I click it, it goes through the exact same cycle where it stalls at 24% again.

Any assistance would be appreciated.

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,400 questions
{count} votes

Accepted answer
  1. Zabaga, Robert (King of Prussia) 141 Reputation points
    2021-02-11T17:26:11.25+00:00

    I've successfully ran the KB on 2 machines at this point. Pretty much the steps other people listed. I can do on a few VMs but dozens or hundreds across an organization would not work for this....too resource intensive for 1 admin!

    -Download the update from Microsoft Catalog (.msu file)

    -Stop Windows Update Service. For me it didn't stop so I had to set the service to Disabled then go to a command prompt and run "sc queryex wuauserv" then do a "taskkill /f /PID xxxx" (where xxxx is the PID listed from the prior query command).

    Delete or rename the C:\Windows\SoftwareDistribution\ folder

    Now run the .msu update file. A few times I got a pop-up about a stub file error. What is that? Anyway, I waited a minute and ran the .msu again and it unpacked and ran successfully.

    Set Windows Update back to manual

    Reboot. KB installed.

    1 person found this answer helpful.
    0 comments No comments

33 additional answers

Sort by: Most helpful
  1. ronnie wang 1 Reputation point
    2021-02-12T03:25:48.577+00:00

    Dear all, I also encountered this issue. Then tried to reset the windows update. stop bits wuauserv and rename the softwaredistribution folder.
    And install the update manually. I tried again and again. Finally, the update has installed.
    However, after check update again, the server misses another ssu update. It was also stuck around 24%.
    So what makes this issue? Is it mean I have to reset and manually install for every update currently?

    By the way, we have 3 dev servers that always keep stop. When I start the VM in Azure, the updates have installed automatically without any delay.

    0 comments No comments

  2. JimSym 201 Reputation points
    2021-02-12T09:52:31.977+00:00

    @Jack Jack

    Thanks for the confirmation. I guessed it was the SSU that was causing the cum update for Server 2016 to stall.

    0 comments No comments

  3. John Storbeck 1 Reputation point
    2021-02-12T15:53:39.1+00:00

    In the fix to this problem before removing KB4601318 from the catalog they mentioned that you should disable Express Updates on your SCCM Software Update Config.

    Was everyone who had this issue with installing the Feb Cumulative Update also have the Check box to use Express Updates ticked?

    We deployed the 2016 SSU ahead of our normal patch window and are trying to decide if we should pull the Feb Cumulative Update for 2016.

    0 comments No comments

  4. Damon Rodriguez 1 Reputation point
    2021-02-12T18:32:27.057+00:00

    I just realized I posted in the wrong place. If we already downloaded and installed the SSU do we need to manually install the CU using the work around or should we wait for a fixed update?