SHA1 and file size mismatch might cause some Office 365 Fixlets to fail
cglimson 270004SV01 Visits (5337)
There is a known problem affecting Fixlets for Microsoft Office 365. This is due to the way Microsoft hosts patches within their Content Delivery Network.
Office 365 Fixlets might sometimes fail to download because the size and SHA1 hash checksum do not match.
Depending on the geographical location of the BigFix deployment, certain Fixlets might fail with an error:
To workaround the issue, perform manual caching of the patch.
1. On a machine that can access the internet, edit the host file.
2. Add the following entry.
3. Copy the URL of the failed patch and download it using a browser,
4. Optional: check the SHA1 hash of the file to ensure that it matches the "Requested sha1".
5. Rename the file to its sha1 checksum value. Remove the file extension if it exists.
6. Copy the renamed file into the BigFix Server download cache folder.
7. Undo the changes to the hosts file by removing the entry in step 2.
Note: BigFix is currently in discussions with Microsoft on this issue and hope to resolve it as soon as possible.
Application Engineering Team
NOTICE: This page has been updated to revise the IP entry from
Post Update (3/13/2017):
BigFix Patch has provided workaround Actions within three Office 365 Fixlets for users whose deployments are affected by the SHA value mismatch when downloading binaries over different Microsoft CDNs
365269 Office 365 Version 16.0.7369.2118 Available - Deferred Channel - Office 2016 (Update from Local Client Cache)
With the actions within these Fixlets, the BigFix server downloads the patch binary files without verifying the hash values. However, the Microsoft Office update installer still verifies integrity of the patch binary files.
Users can choose to download with nohash using silent installation or with status windows: