The process of installing, configuring, and customizing Visual Studio to support development workflows across languages, platforms, and workloads.
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^
- 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.
- Check File Explorer → Properties → Details → Product version.
- 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^
- 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