Nsight Systems fails to start profiling on Win 10 x64 with runtime target side error

Hi,

I am having trouble getting the latest version of Nsight Systems (2023.1.1) to work on my Windows 10 x64 system. The error I am getting is as follows and appears to be related to permissions:

RuntimeError (120) {
    TargetSideError (1100) {
        ErrorText: C:\dvs\p4\build\sw\devtools\Agora\Rel\QuadD_Main\QuadD\Common\ProcessResumer\Windows\ProcessResumerImpl.cpp(45): Throw in function __cdecl QuadDCommon::ProcessResumer::WindowsProcessResumer::WindowsProcessResumer(class QuadDCommon::StrongType<class QuadDCommon::LimitedNumber<unsigned int,4294967295>,class QuadDCommon::ProcessIdTag>)
            Dynamic exception type: struct boost::wrapexcept<class QuadDCommon::SystemException>
            std::exception::what: SystemException
            [struct QuadDCommon::tag_errno_text * __ptr64] = Access is denied
            [struct QuadDCommon::tag_message * __ptr64] = Failed to open thread 19884 from process 10604
            [struct QuadDCommon::tag_winapi_error_code * __ptr64] = 5
            [struct boost::errinfo_api_function_ * __ptr64] = OpenThread
            
        ServiceName: AnalysisService
        MethodName: Init
        SystemError (124) {
            ErrorText: Failed to open thread 19884 from process 10604
            ApiFunction: OpenThread
            OriginalFile: C:\dvs\p4\build\sw\devtools\Agora\Rel\QuadD_Main\QuadD\Common\ProcessResumer\Windows\ProcessResumerImpl.cpp
            OriginalLine: 45
            OriginalFunction: __cdecl QuadDCommon::ProcessResumer::WindowsProcessResumer::WindowsProcessResumer(class QuadDCommon::StrongType<class QuadDCommon::LimitedNumber<unsigned int,4294967295>,class QuadDCommon::ProcessIdTag>)
            OriginalExceptionClass: struct boost::wrapexcept<class QuadDCommon::SystemException>
        }
    }
}

I updated to the latest driver and tried running as administrator but no difference. Interestingly, I can get the 2020.3.4 version to start profiling, but this now complains about a driver mismatch and fails to collect any CUDA events. I would appreciate any insight into what could be going on here.

@dofek can you respond to this?