Looks like Microsoft updated the download
Seems the package was updated, please open a ticket with support for them to update sha1 values
ticket created…thanks
Hello @sdemonte , I’ve reached out to contacts at Microsoft for assistance on this item as the root of the problem is with the patch binary hosted in the catalog. Here is the supporting details:
If you manually download this binary and test / validate the sha1, you’ll see the differences between what is documented by Microsoft in the image above and also embedded in the filename:
Q: (base64 decode "KFYM+twQMKtg5A3azTaDFl9AvFg=") as hexadecimal
A: 28560cfadc1030ab60e40ddacd3683165f40bc58
T: 6328.420 ms
I: singular string
Q: sha1 of files "C:\Users\Gus\Downloads\windows10.0-kb5123099-x64_28560cfadc1030ab60e40ddacd3683165f40bc58.msu"
A: 57f2f2a6028a6f11d0fc96a5f6057912ef0ad4d5
T: 6328.349 ms
I: singular string
This is also applicable to fixlet 512309905 - MS26-SEP: Cumulative Update for Windows Server 2016 - Windows Server 2016 - KB5123099 (x64) as they share the same patch binary. More details to follow as they develop.
Thanks, Gus.
Any update this issue? I need to patch both 1607 and Windows Server 2016 Sept patches ASAP.
Thanks,
Scott
We start patching very soon, so let’s get moving.
Our Patch team is working with Microsoft on the issue. Aside from their security bulletin hash not matching their actual download binary, the patch itself also fails to install.
I see MS has still not updated their bulletin with a 'Known Issues' section, but there are definitely known issues as the archive appears to be corrupted. I'm seeing multiple reports of customer issues who've tried to install it manually - the patch doesn't work, regardless of BigFix at this point.
One example thread with some pretty detailed info at Reddit
Quality is such a lost art these days ![]()
FYI Both patches are working now. Thanks for all the help getting this resolved. I had one of each patch running and failing to download all day and then about 15 mins ago they both downloaded and installed with a good 3010 exit code. I then applied it to 108 1607 machines all good and 24 2016 servers and all good there too.
Hello all, Microsoft has fixed the digital signature in this patch binary.
BEFORE:
AFTER:
Therefore you may proceed with your patching efforts. No changes were required by BigFix as the content referenced the size, sha1 and sha256 that Microsoft originally provided. Apologies for the inconvenience but this was clearly outside of our control.
Thanks, Gus.
but what you could do from now on, try to download MS content and at least check the sha values before you decide to add to the external sites.



