I can just launch using nsys.exe
C:\Users\Tim\Desktop>SET JULIA_CUDA_NSYS=c:\Program Files\NVIDIA Corporation\Nsight Systems 2022.2.1\target-windows-x64\nsys.exe
# this is only required because nsight isn't on path on this system
C:\Users\Tim\Desktop>"c:\Program Files\NVIDIA Corporation\Nsight Systems 2022.2.1\target-windows-x64\nsys.exe" launch c:\Users\Tim\.cache\jl\installs\bin\winnt\x64\1.7\julia-1.7-latest-win64\bin\julia.exe
_
_ _ _(_)_ | Documentation: https://docs.julialang.org
(_) | (_) (_) |
_ _ _| |_ __ _ | Type "?" for help, "]?" for Pkg help.
| | | | | | |/ _` | |
| | |_| | | | (_| | | Version 1.7.2 (2022-02-06)
_/ |\__'_|_|_|\__'_| | Official https://julialang.org/ release
|__/ |
(@v1.7) pkg> st
Status `C:\Users\Tim\.julia\environments\v1.7\Project.toml`
[052768ef] CUDA v3.8.5
[295af30f] Revise v3.3.3
julia> CuArray([1]).+1;
julia> CUDA.@profile CuArray([1]).+1;
[ Info: Running under Nsight Systems, CUDA.@profile will automatically start the profiler
WARNING: CUDA tracing is required for cudaProfilerStart/Stop API support. Turning it on by default.
WARNING: CPU context switches trace requires administrative privileges, disabling.
WARNING: CPU sampling requires administrative privileges, disabling.
Ôöî Info: Profiling has finished, open the report listed above with `nsys-ui`
Ôöö If no report was generated, try launching `nsys` with `--trace=cuda`
I’d file a report either way; there’s multiple users running into this, and it just shouldn’t fail like that.