This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 34%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hi Team,
I've been trying to run GPU Usage tests from a command line for a while now. So far I've been able to generate .diagsession files from agent configuration files by following the steps described in "Measure application performance from the command line" - https://learn.microsoft.com/en-us/visualstudio/profiling/profile-apps-from-command-line?view=vs-2022.
In order to be able to run the GPU test, a .json file was created that contains a GpuProfilingCollectionAgent.dll and its COM CLSID, but when trying to start the diagnostic session, in the same way as described above (as described in "Measure application performance from the command line"), an error appears as seen in the attached image.
I would like to know how to start GPU performance tests from the command line? And why does the procedure described above not have the intended effect?
Beast regards,
Maja
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hi @Maja , may I ask, where did you get/find the CLSID of GpuProfilingCollectionAgent.dll file? Can you confirm that the CLSID is correct?
Hi @Tianyu Sun-MSFT , I found the CLSID in Windows Registry Editor and hope it is correct.
Hi @Maja , I searched in Registry and found several related data(CLSID) about the specific .dll file, but it doesn’t work. I also checked the existing CLSID for DiagnosticsHub.CpuAgent.dll(and other config files which were mentioned in .json files), and looks like the CLSID is not the one stored in the Registry. I believe the issue is caused by using the wrong CLSID.
So, on your side, can you search and find the same CLSID, like 4EA90761-2248-496C-B854-3C0399A591A4, for DiagnosticsHub.CpuAgent.dll in Registry? If you can find it in Registry, the data or the information may help us to know where to find the correct CLSID.
Like you, I also can't find the given CLSID for DiagnosticsHub.CpuAgent.dll, or any of the other CLSID codes from AgentConfigs .json files in the Registry. What to do in this situation? Is there any other way to solve this problem?