VTune 2023.2.0.49484 completely broken for Windows accounts with non-ASCII characters

[psiha]

I suspect this due to buggy path string handling: if I move the installer into a path without non-ASCII characters it will at least install but will then fail to launch (only a brief 'blink' of the splash screen) and even worse: it broke my Visual Studio installation so that it wouldn't launch even after I uninstalled VTune!!

[Soumya_M_Intel]

Hi psiha,

Thanks for letting us know about the concern. We are checking on the issue with our resources. Please wait for 2-3 business days. We will get back to you as soon as possible.

Regards,

Soumya

[ArpanB_Intel]

Domagoj, please share the below information with us:

- OS build on which you are installing the software

- Is the installer an online or an offline package?

- Version of Microsoft Visual Studio installed along with it's build version

- Other versions of Intel® Parallel Studio XE or Intel® oneAPI already installed on the system

- Screenshots of the error screen

- Installation Log files

The default path for a log file for a oneAPI installation is: C:\Program Files (x86)\Intel\oneAPI\logs

The default path for a log file for a Parallel Studio XE installation is: %temp%\pset_tmp_PSXE<version>_<username>

We would like to know.

[psiha]

- Windows 11 Business 22H2 22621.1992

- happens the same with either

- Professional 2022 (64-bit) 17.6.5

- none

- attached (trying to open the log file from the installer also does not work as can be seen from the error in the screenshot)

- attached

*note: the attached error logs are for the first case - when I run the installer from my Downloads directory (which is under my user directory, C:\Users\DomagojŠarić, which has diacritics in its name) and the installer fails immediately (I will not try the second approach again - running the installer from a different location - because then the installation succeeds but breaks my VS installation so badly that I have to fully reinstall and reset it - and then configure it from scratch)

I also tried

- making a symlink to my user directory with a plain ascii name and running the installer from there - didn't help

- moving/merging my user TEMP and TMP directories into the system (Windows\Temp) directory - 'helped only a little' judging from the log - the installer was able pass the 'moving the log file phase' (probably because the log file was no longer in a 'problematic path')

- running with admin privileges didn't help (attached both logs for both approaches)

[ArpanB_Intel]

Domagoj, thank you for sharing the logs. We will check and share our findings soon.

[ArpanB_Intel]

Domagoj, the path requires ASCII characters. Was the installation successful when you used ASCII characters for your Windows accounts?

We would like to know.

[ArpanB_Intel]

Domagoj, unfortunately we were unable to hear back from you.

If you have any further queries, please post a new question as this thread will no longer be monitored by Intel®.