Visual Studio 2022 Build Tools 17.14.45 – Catalog SHA-256 mismatch

Jigar 0 Reputation points
2026-11-17T04:43:47.0866667+00:00

I am preparing an offline layout for Visual Studio 2022 Build Tools 17.14.45 (build 17.14.37906.3).

The official Visual Studio Current channel manifest references VisualStudio.vsman under Microsoft.VisualStudio.Manifests.VisualStudio.

Manifest-declared catalog:

  • Size: 30,447,538 bytes
  • SHA-256: da49c304df0fff4e75c20849171840a06840e845ce814104d709dfb5cd461668

Received catalog:

  • Size: 17,959,942 bytes
  • SHA-256: d1d8109899558618035724949673f69f8c1b5704f542a2e76f31d87e425d5710

The catalog was retrieved over HTTPS using .NET HttpClient with Accept-Encoding: identity, automatic decompression disabled, and redirects disabled. The response body was read to EOF before hashing. Exact HTTP response headers were not retained.

Questions:

  1. Why might the received catalog differ from the manifest-declared size and SHA-256?
  2. Which exact byte representation does the manifest hash cover?
  3. What is the Microsoft-supported procedure for verifying the catalog and obtaining authenticated dependency and package-size information before creating an offline layout?

No installer has been executed, and no layout packages have been downloaded. Installation remains blocked pending verification.

This concerns Visual Studio 2022 Build Tools, not Visual Studio Community Edition.

Developer technologies | Visual Studio | Setup
0 comments No comments

3 answers

Sort by: Newest
  1. Tom Tran (WICLOUD CORPORATION) 5,970 Reputation points Microsoft External Staff Moderator
    2026-11-17T07:19:18.4966667+00:00

    Hi @Jigar ,

    Thank you for sharing the detailed catalog information and SHA-256 comparisons for Visual Studio 2022 Build Tools 17.14.45.

    I notice that recently there are many similar inquiries regarding this matter and I was able to find a thread with the most attention on Visual Studio Developer Community, involving discrepancies between the channel metadata and the downloaded VisualStudio.vsman catalog. The discussion also includes reports involving Visual Studio 2022 Build Tools.

    At this time, there isn't an official explanation confirming why these values differ or which exact byte representation the manifest's SHA-256 covers. The supported procedure for independently verifying the catalog before creating an offline layout also requires further clarification from the Visual Studio engineering team.

    Therefore, I recommend following the existing Developer Community discussion for updates from the engineering team, as this is where the issue is currently being investigated.

    Alternatively, if you have an eligible Visual Studio subscription that includes technical support benefits, you can consider submitting a support request for further assistance.

    If you found my response helpful or informative, please consider following this guidance. Your feedback not only supports me but also helps other community members who may face the same issue in the future.

    Thank you for your patience and understanding.

    Was this answer helpful?

    0 comments No comments

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. AI answer

    2026-11-17T04:44:51.8133333+00:00

    Do not accept or reinterpret the mismatched VisualStudio.vsman; use the fixed-version Build Tools 17.14.45 bootstrapper to create the layout, then let Visual Studio Setup validate the downloaded metadata and packages with --verify.

    What the mismatch establishes

    The received object is not byte-for-byte the object described by the channel-manifest entry:

    • Declared: 30,447,538 bytes, SHA-256 da49…1668
    • Received: 17,959,942 bytes, SHA-256 d1d8…5710

    Neither content encoding nor line-ending normalization can be assumed to explain this. Because the HTTP response headers were not retained, the response’s status, Content-Type, Content-Length, cache/CDN metadata, and any intermediary behavior cannot now be established.

    There are matching public reports for Build Tools 17.14.45 and earlier 17.14 servicing releases, but no accepted answer or public Microsoft specification explaining an alternate byte representation that should legitimately produce this mismatch.^1^

    Consequently:

    • Do not hash parsed, reserialized, decompressed, or newline-normalized JSON in an attempt to obtain the declared value.
    • Do not use the received file as authenticated input for dependency or package-size calculations.
    • The available Microsoft documentation does not define whether that field covers a transport representation, decoded entity body, canonicalized document, or another internal artifact. An exact byte-level answer would require confirmation from the Visual Studio Setup team.

    Microsoft-supported acquisition and verification

    Microsoft publishes a fixed-version Build Tools bootstrapper for 17.14.45 / build 17.14.37906.3. Fixed-version bootstrappers stamp the layout with the corresponding channel identity and are the supported way to target a servicing release.^2^

    1. Download the Build Tools bootstrapper from the 17.14.45 row of the release-history page—not the evergreen Build Tools link, which follows the latest Current-channel release.
    2. Check File Explorer → Properties → Details → Product version.
    3. From an elevated Command Prompt, create a new layout in an empty directory. For a selected workload:
    vs_BuildTools.exe --layout C:\VSBT-17.14.45 ^
      --add <workload-or-component-ID> ^
      --includeRecommended ^
      --lang en-US
    

    Omit --includeRecommended if those dependencies are not required; add --includeOptional only when needed. If --add is omitted, Setup downloads all available workloads and components. Microsoft documents these switches as the supported mechanism for selecting workloads and their required, recommended, and optional dependencies.^3^

    1. After creation completes, verify the layout:
    C:\VSBT-17.14.45\vs_BuildTools.exe ^
      --layout C:\VSBT-17.14.45 --verify
    

    --verify checks the layout for missing or invalid package files and prints any failures. It depends on metadata generated in the layout and works only for the latest servicing release of the applicable Visual Studio minor version.^3^

    If verification reports corruption or missing files, use:

    C:\VSBT-17.14.45\vs_BuildTools.exe ^
      --layout C:\VSBT-17.14.45 --fix
    

    --fix repeats verification and redownloads invalid or missing files; it requires Internet access.^4^

    Dependency and size information before download

    The public documentation does not provide a supported standalone procedure for taking VisualStudio.vsman, independently authenticating it, and deriving an authoritative dependency closure and exact package size before layout creation.

    The supported dependency resolver is the bootstrapper/installer invoked with --layout, --add, --includeRecommended, and --includeOptional. Therefore, authenticated dependency resolution and layout validation occur as part of creating and verifying the layout—not through a separately documented raw-catalog API.

    If policy prohibits downloading any package until the catalog discrepancy is independently explained, keep the process blocked and escalate the following to Visual Studio Developer Community or Microsoft Support:

    • Fixed bootstrapper filename, version, and Authenticode signature details
    • Channel-manifest URL and retrieval timestamp
    • Catalog URL exactly as supplied by the manifest
    • Complete response status and headers from a fresh, non-destructive retrieval
    • Declared and received lengths and SHA-256 values
    • A minimal reproduction showing redirect and decompression settings

    Ask specifically for the byte-level hashing contract for Microsoft.VisualStudio.Manifests.VisualStudio and confirmation of the expected 17.14.45 catalog object. Cache clearing, installer repair, certificate installation, and layout --fix are not applicable yet because no installer or layout operation has failed.


    References

    1. Visual Studio Build Tools 2022 17.14.45: VisualStudio.vsman size and ...
    2. Visual Studio 2022 Release History | Microsoft Learn
    3. Create and maintain a network installation of Visual Studio
    4. Use command-line parameters to install, update, and manage Visual Studio
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.