Visual Studio Build Tools 2022: official catalog size and SHA-256 mismatch on two networks

Samer Twal 0 Reputation points
2026-09-18T07:11:21.6966667+00:00

I am preparing to install Visual Studio Build Tools 2022, but the official catalog payload does not match the size and SHA-256 declared in Microsoft's Release channel metadata.

Channel:

https://aka.ms/vs/17/release/channel

Catalog:

https://download.visualstudio.microsoft.com/download/pr/bc92e2cb-33de-4a0c-995d-efa817f16b16/6e470016e4324c84c255ffd0beb3767d17ec89cc8561e9409ee3e1f6d29400f5/VisualStudio.vsman

Expected from channel metadata:

Size: 30,443,537 bytes

SHA-256: 6e470016e4324c84c255ffd0beb3767d17ec89cc8561e9409ee3e1f6d29400f5

Received:

Size: 17,954,732 bytes

SHA-256: f0a50ea157222c29abd5ea6ff01bfc3c33b04e011c5e45ee2ca38ef0778e5643

The same mismatch reproduced on two networks: the original connection and a phone hotspot. Retries used fresh download directories, no-cache request headers, and Accept-Encoding: identity, with automatic decompression disabled.

The catalog returned HTTP 200, with Content-Length: 17954732 matching the received bytes. No catalog redirect, Content-Range, or Content-Encoding was observed.

The original-network response included:

X-Cache: HIT, HIT

Age: 190054

X-Ms-Region: prod-neu-z1

The hotspot retry on 2026-09-18 at 06:18 UTC included:

Server: Kestrel

X-Ms-Region: prod-weu-z1

Content-Length: 17954732

Last-Modified: Thu, 10 Sep 2026 23:59:43 GMT

ETag: "0xB9BB9F38B9E5BB399742E1ECD63A7B4C2729479C5B4EF8BD7494D42F62B7AA0F"

This does not appear to be a locally truncated download, but I cannot determine the cause of the metadata/payload inconsistency.

Invalid catalog payloads were deleted and never executed or reused. The retained official bootstrapper has a valid Microsoft Authenticode signature but has not been executed. No installation or integrity-verification bypass has been attempted.

Could Microsoft please:

  1. Confirm the current valid size and SHA-256 for this catalog and the corresponding official channel metadata.
  2. Investigate whether this channel/catalog pair or its CDN delivery is inconsistent.
  3. Provide a supported corrected official acquisition path for Build Tools 2022 that passes integrity verification.

I do not want to override checksums, use mirrors, or install from unverified metadata.

Developer technologies | Visual Studio | Setup
0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest
  1. Tom Tran (WICLOUD CORPORATION) 5,945 Reputation points Microsoft External Staff Moderator
    2026-09-18T08:08:08.6433333+00:00

    Hi @Samer Twal ,

    Thanks for sharing the details.

    I checked both files, and they identify Visual Studio 2022 version 17.14.41, build 17.14.37710.0. This means the catalog appears to correspond to the correct release, but it does not explain why its raw size and SHA-256 differ from the values in the channel manifest.

    I cannot verify which values are authoritative because this requires access to the catalog publishing and delivery systems, and I could not find public documentation that explains the difference.

    I recommend reporting this through Visual Studio Developer Community. This is the appropriate channel for a product-level issue that requires further investigation by the relevant product team. The details you have already collected should be sufficient for the report.

    Until the appropriate team clarifies the discrepancy, I would not suggest bypassing the integrity checks or using an unofficial source.

    Hope this helps. If you found my response helpful or informative, I would greatly appreciate it if you could follow the instructions here. Thank you.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.