NVIDIA NSight Visual Studio Edition install fails when the user folder name is not English

Hello everyone,

I wanted to share a frustrating installation issue I recently experienced with NVIDIA Nsight Visual Studio Edition (packaged with the CUDA Toolkit). As a globally recognized, mature technology company, NVIDIA typically delivers highly polished products, so I’m quite surprised that this problem still exists.


Steps to Reproduce

  1. Non-English Username: Use a Windows user folder name containing non-English characters (in my case, Korean).
  2. Attempt Installation: Run the CUDA Toolkit installer, which includes Nsight Visual Studio Edition.
  3. Failing Installation: The installation fails during the Nsight component installation, often without a clear error message.

Observations

  • Root Cause: The installer seems unable to correctly parse or handle non-English characters in the user profile path. In my specific case, the path was something like C:\Users\대한민국\, which apparently caused the parsing issue.
  • Unexpected from NVIDIA: Given NVIDIA’s standing in the industry, it’s quite unexpected and disappointing that the installer doesn’t account for non-English usernames.

Workaround

  • Rename the User Folder: I had to rename my user folder to an English-only name via registry edits—a process that can be complicated and risky if done incorrectly.
  • Result: After changing the folder name, Nsight Visual Studio Edition installed without any problems.

Request/Feedback

  • Future Releases: I respectfully suggest that NVIDIA address this issue in future releases of Nsight or the CUDA Toolkit so that it properly handles non-English user folder paths. Many developers around the world use localized systems, and being forced to rename the user folder is inconvenient and error-prone.
  • Alternate Solutions: If there is a simpler workaround or official fix available, I’d appreciate any guidance from NVIDIA or others who have resolved this more gracefully.

I hope sharing this experience helps others who run into the same problem.

Thanks for taking the time to write this detailed bug report, KRPark. I have filed a bug against Nsight Visual Studio Edition and assigned this to my development team.