For Windows and other Microsoft media, checksum hashes (such as SHA1/SHA256) are published only for specific downloads where Microsoft explicitly provides them, typically on the same page as the download.
In the provided material, an example is the Safe OS Dynamic Update package for Windows 10, version 2004 and 20H2, where Microsoft lists SHA1 and SHA256 hashes for each .msu file directly in the bulletin:
| File name |
SHA1 hash |
SHA256 hash |
| Windows10.0-KB4586858-x86.msu |
EEF391495ABE6DD1B9B9288EE6A19FB8DEEBAF73 |
648C5E2E6A72996418B150E42B7283C9C76265EFC209CBE83483E552A42E55F7 |
| Windows10.0-KB4586858-x64.msu |
8713EE767680867DDCADA8C85165C06A07DA4D68 |
EC37BF1CD31573276E26B1552B63D146FB9C60BBB59028E624E28BF0F19D40F0 |
| Windows10.0-KB4586858-arm64.msu |
5C94BADAC0D9929794DB1185A826F05495623729 |
93DD13B908EC4023C30485DC0A803A5681D08669F3EDD88F7309F831A58E5B0B |
Similarly, for monthly security release ISO images, Microsoft publishes the ISO download links on a dedicated support article, but that article does not include checksum values; it only provides the ISO URLs for each month and year.
For ISO files such as SW_DVD9_NTRL_Win_10_2004_64Bit_MultiLang_FOD_1_X22-21311.ISO and SW_DVD9_NTRL_Win_10_2004_64Bit_MultiLang_FOD_1_X22-21313.ISO, no checksum information is provided in the supplied material. When Microsoft does publish hashes for such media, they appear on the specific download or support page for that file, in the same way as shown for the Safe OS Dynamic Update packages.
References: