Isaac Sim 6.0.0-rc.22 source build fails on Windows with nvcc: 'cudafe++' died with status 0xC0000409 using Visual Studio 18 / MSVC 19.51

Omniverse Isaac Sim
1

Hello,

I am trying to build Isaac Sim 6.0.0-rc.22 from source on Windows x86_64, and I am hitting a build failure in CUDA compilation.

Environment

  • Isaac Sim branch/version: v6.0.0-dev2

  • Reported build version: 6.0.0-rc.22

  • OS: Windows

  • Visual Studio detected by build: Visual Studio Community 18

  • MSVC toolset directory:

    • C:\Program Files\Microsoft Visual Studio\18\Community\VC\Tools\MSVC\14.51.36231

  • cl.exe version:

    • Microsoft (R) C/C++ Optimizing Compiler Version 19.51.36244 for x64

  • Windows SDK detected by build:

    • 10.0.26100.0

What I did

I cloned the repository and built using build.bat on Windows as described in the repository/README flow. The repository’s Windows C++ configuration documentation says the build toolchain is controlled from repo.toml under [repo_build.msbuild]. (github.com)

Main error

The actual build failure happens during CUDA compilation, for example:

  • source\extensions\isaacsim.core.nodes\cuda\CameraKernels.cu

  • source\extensions\isaacsim.ros2.nodes\nodes\ROS2PublishPointCloud.cu

  • source\extensions\isaacsim.sensors.rtx\nodes\IsaacSimSensorsRTXCuda.cu

The error is:

textCopyCUSTOMBUILD : nvcc error : 'cudafe++' died with status 0xC0000409
error MSB8066: Custom build for '...CameraKernels.cu' exited with code 9

I also saw the same failure pattern for other .cu files.

Important observations

  • Regular C++ compilation appears to proceed for many targets.

  • The failure seems isolated to CUDA/NVCC frontend compilation.

  • I know that cudafe++ died with status 0xC0000409 has been reported more generally in NVIDIA forums for CUDA + Visual Studio environments, so I suspect this may be a toolchain compatibility problem rather than an Isaac Sim source code issue alone. (forums.developer.nvidia.com)

Build log details

The build reports things like:

  • Linking against the discovered Microsoft Visual Studio Community 18

  • Compiler version check passed: {'vs_version': '18', 'msvc_version': 'v145', 'msbuild_version': '18', ...}

cl.exe exists and runs correctly:

textCopyC:\Users\Administrator\isaacsim\_build\host-deps\msvc\VC\Tools\MSVC\14.51.36231\bin\Hostx64\x64\cl.exe
Microsoft (R) C/C++ Optimizing Compiler Version 19.51.36244 for x64

Additional issue while trying to pin toolchain in repo.toml

When I explicitly set vs_path and also tried to pin msvc_version = "v145" in repo.toml, the build failed even earlier with:

textCopyBuildError: User set repo_build.msbuild.vs_path: C:\Program Files\Microsoft Visual Studio\18\Community
and repo_build.msbuild.msvc_version: v145 but Visual Studio installation at
C:\Program Files\Microsoft Visual Studio\18\Community does not contain a matching version
of the Visual Studio Build Tools.

However, the MSVC directory does exist:

textCopyC:\Program Files\Microsoft Visual Studio\18\Community\VC\Tools\MSVC\14.51.36231

So it looks like either:

  1. repo_build does not recognize this MSVC/VS18 combination correctly, or

  2. NVCC / cudafe++ is not compatible with this toolchain for Isaac Sim 6.0.0-rc.22 on Windows.

My questions

  1. Is Visual Studio 18 / MSVC 19.51 / v145 currently supported for Isaac Sim 6.0 source build on Windows?

  2. Is there a known issue with CUDA/NVCC cudafe++ 0xC0000409 for this toolchain?

  3. Is there a recommended repo.toml configuration for VS18 / VS2026-style installations?

  4. If this toolchain is not currently supported, what exact Visual Studio / MSVC / Windows SDK combination is recommended for Isaac Sim 6.0.0-rc.22 source builds on Windows?

Minimal command used

batCopybuild.bat -r -j 1 --verbose

If needed, I can also provide:

  • full build log

  • current [repo_build.msbuild] section from repo.toml

  • exact nvcc command lines that fail

Thank you.

3

Can you downgrade VS/MSVC to VS 17 / MSVC 19.4X and retry?

cudafe++ dying with 0xC0000409 (STATUS_STACK_BUFFER_OVERRUN / a structured exception) is a well-known symptom of NVCC receiving compiler flags or headers it can’t parse from an unsupported MSVC version. NVCC has a hard-coded whitelist of supported cl.exe versions, and MSVC 19.51 (VS 18 / VS 2026) is almost certainly beyond what the bundled CUDA toolkit was built to support.

5

How to configure Issac Sim with Visual Studio 2026? · isaac-sim/IsaacSim · Discussion #583 · GitHub is related.