Title: Installing Build Tools for Visual Studio messes up the MSBuild path · Issue #61275 · nodejs/node · GitHub
Open Graph Title: Installing Build Tools for Visual Studio messes up the MSBuild path · Issue #61275 · nodejs/node
X Title: Installing Build Tools for Visual Studio messes up the MSBuild path · Issue #61275 · nodejs/node
Description: Version 24.12.0 Platform Microsoft Windows NT 10.0.20348.0 x64 Subsystem No response What steps will reproduce the bug? [not a core node.js issue, bit I figured it's worth sharing at least as a caveat and to help others recover] I instal...
Open Graph Description: Version 24.12.0 Platform Microsoft Windows NT 10.0.20348.0 x64 Subsystem No response What steps will reproduce the bug? [not a core node.js issue, bit I figured it's worth sharing at least as a cav...
X Description: Version 24.12.0 Platform Microsoft Windows NT 10.0.20348.0 x64 Subsystem No response What steps will reproduce the bug? [not a core node.js issue, bit I figured it's worth sharing at least as a...
Opengraph URL: https://github.com/nodejs/node/issues/61275
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Installing Build Tools for Visual Studio messes up the MSBuild path","articleBody":"### Version\n\n24.12.0\n\n### Platform\n\n```text\nMicrosoft Windows NT 10.0.20348.0 x64\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\n_[not a core node.js issue, bit I figured it's worth sharing at least as a caveat and to help others recover]_\n\nI installed via the Windows MSI, which worked great by itself. But I also chose the option to install the VS Build Tools for C++, and that ended up messing up my system. The symptom was that attempting to do a .Net build in a 64-bit terminal would fail with:\n```\nThe NuGetSdkResolver did not resolve this SDK because there was no version specified in the project or global.json\n```\nI didn't save the whole output, but the key hint from the remaining message was that it was looked for the .Net SDK under \"C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\BuildTools\\MSBuild\\Sdks\\Microsoft.NET.Sdk\\Sdk\", and I don't have such a path.\nIt turned out that the Build Tools for Visual Studio 2022 installer had put a bunch of x86 paths at the front of the system PATH, including \"C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\BuildTools\\\\MSBuild\\Current\\Bin\\amd64\", and that resulted in either the wrong build of msbuild.exe running (in spite of that \"amd64\" at the end of the path) or wrong base path to search for SDKs.\n\nResolved by uninstalling the Build Tools for Visual Studio 2022.\n\n\n\n\n### How often does it reproduce? Is there a required condition?\n\nSelect the option to install the Build Tools for Visual Studio\n\n### What is the expected behavior? Why is that the expected behavior?\n\n.\n\n### What do you see instead?\n\nBroken .Net SDK resolving\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/changov","@type":"Person","name":"changov"},"datePublished":"2026-01-04T20:00:24.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/61275/node/issues/61275"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:54610f72-a207-a8b1-7f8f-d0f9de53097b |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B2B6:2D647F:6CDC36:90DE40:69648631 |
| html-safe-nonce | 27fc09146616525a38354396a8b508c93f08e4b92cf0218ff55fa76c1bf58d52 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMkI2OjJENjQ3Rjo2Q0RDMzY6OTBERTQwOjY5NjQ4NjMxIiwidmlzaXRvcl9pZCI6IjQ5OTcxMDYyMDYyNjYxMzIwMTciLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 32ecf7d101de9f513767a4749a0a8de5e02a284f5447f510a38dd05c6e094cf1 |
| hovercard-subject-tag | issue:3779592387 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/61275/issue_layout |
| twitter:image | https://opengraph.githubassets.com/046d215bd0c72f31829776712e5fb4cf70f519098df4f9c53d425cba9200b4c5/nodejs/node/issues/61275 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/046d215bd0c72f31829776712e5fb4cf70f519098df4f9c53d425cba9200b4c5/nodejs/node/issues/61275 |
| og:image:alt | Version 24.12.0 Platform Microsoft Windows NT 10.0.20348.0 x64 Subsystem No response What steps will reproduce the bug? [not a core node.js issue, bit I figured it's worth sharing at least as a cav... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | changov |
| hostname | github.com |
| expected-hostname | github.com |
| None | baa7d9900fdf7b27d604f36887af878d569cfbdcf97126832a5f4f0caf0c6ba5 |
| turbo-cache-control | no-preview |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 842eff1d11f899d02b6b3b98fa3ea4860e64b34e |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width