Closed yellowpanda closed 3 years ago
A nasty side effect is that
Get-KbUpdate -Architecture x64 -OperatingSystem "Windows Server 2016" -Latest -Pattern "KB" -ErrorAction SilentlyContinue -Verbose:$false
takes multiple hours. The DownloadWinUpdates.ps1 takes ~17 hours in my case.
Thanks - something has obviously changed on the Windows Update feeds side, as you point out, as all of this worked well early in 2020. That said, I'm swamped right now, but will take a look when i can. I'm tempted to simply hard-code the paths to the relevant updates and that way, we know it will work every time, and then it's just a case of updating the path to the new updates on a monthly basis. You only really need the Servicing Stack Update, the latest CU and you're good.
One of the reasons the App Service may be breaking (or taking forever) is it may be trying to apply a CU without the SSU in place already - i know i've seen that in the past.
Feel free to fork the repo and adjust the scripts - i'll look into it too.
This should now be fixed in the latest release.
Describe the issue
In DownloadWinUpdates.ps1 is the following code responsible for finding the latest cumulative update:
The script end up assigning "KM" to
$KBs
. This is not a real KBxxxxxx of cause.If you open https://support.microsoft.com/en-us/help/4000825 in a browser and search for "Cumulative.Server.x64" then nothing is found.
Hardware N/A.
Send the logs Complete log send to your email.
Relevant log output from Logs2\20210224\WindowsUpdates\WindowsUpdates0224-061829.txt:
Additional context By the way, this if-statement will never work because
$cumulativekbID
will always have at least the valueKB