topic Intel VTune profiler not working in Analyzers

Intel VTune profiler not working

bigbadroy — Tue, 16 Jun 2026 12:58:10 GMT

Hi Everyone,

Previously I have been able to run Intel's VTune profiler, but a few months ago (I don't recally the exact period) it stopped working.

The issue seems to be that VTune creates self-signed certificates that its various components (GUI, Backend, etc) use to talk to each other on localhost.
Previously this worked, but at some point I assume the security profiles on our machines changed, and so the self-signed cert was no longer acceptable even for localhost communications.

I always used to start all components by running vtune-gui.exe, and this worked.
Now, I get
handshake failed; returned -1, SSL error code 1, net_error -202

========
PS C:\Users\micha633> & "C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune-gui.exe" --log-to-console --log-level=debug
PS C:\Users\micha633>
VTune Profiler GUI is accessible via https://127.0.0.1:53449/
info: UI Backend TCP Socket server listening on port 53450
debug: incoming XML: <msg> <handshake role="common-data-source"> <identityKey>common</identityKey> </handshake> </msg>
info: data source connected: common
[25288:0612/085910.003:ERROR:net\socket\ssl_client_socket_impl.cc:916] handshake failed; returned -1, SSL error code 1, net_error -202
debug: Incoming HTTP request with URL:/ui?passphrase=0c4d3f9f-0469-e457-f068-ff091d5c74d3
Query:{"passphrase":"0c4d3f9f-0469-e457-f068-ff091d5c74d3"}
Body:{}
========

The log that's shown if I run the backend directly shows explicitly that a self-signed certificate is used:

========
PS C:\Users\micha633> & "C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune-backend.exe"
No TLS certificate was provided as a --tls-certificate command-line argument thus a self-signed certificate is generated to enable secure HTTPS transport for the web server: C:\Users\INTERNAL_MICHA633_$\AppData\Roaming\Intel\VTune\settings\certificates\middleware.crt.
VTune Profiler GUI is accessible via https://127.0.0.1:57604/

========
How can I safely and securely continue to use the VTune profiler? Attached screenshot and log file. Thank you.

Re: Intel VTune profiler not working

bigbadroy — Wed, 17 Jun 2026 10:35:13 GMT

bump

Re: Intel VTune profiler not working

liam_carter — Wed, 17 Jun 2026 18:38:02 GMT

To safely bypass VTune's net_error -202 localhost SSL block, use one of these quick fixes:

Bypass via CLI (Easiest): Launch the GUI from PowerShell with flags to ignore certificate errors:

PowerShell

& "C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64\vtune-gui.exe" --disable-web-security --ignore-certificate-errors

Trust the Certificate: Locate middleware.crt at the AppData path shown in your backend log. Right-click, select Install Certificate, and place it into the Trusted Root Certification Authorities store for your current user.
Use your Browser: Copy the https://127.0.0.1:... URL containing the passphrase from your backend log, paste it into Chrome or Edge, and click Advanced -> Proceed to 127.0.0.1 (unsafe).

Re: Intel VTune profiler not working

bigbadroy — Thu, 18 Jun 2026 07:27:26 GMT

Hi Liam,

Thanks for this. I will let you know if this works.

Re: Intel VTune profiler not working

bigbadroy — Thu, 18 Jun 2026 07:48:12 GMT

Hi Liam,

Unfortunately, the first (nicest) option doesn't work:

I get

Unknown arguments: disable-web-security, disableWebSecurity, ignore-certificate-errors, ignoreCertificateErrors

Neither do those arguments work when applied to the vtune-backend program