-1

When i start the C++ debugger, the "Diagnostic Tools" windows shows this error. "The diagnostic tools failed unexpectedly." The output windows shows

"Unzulässige Funktion." 
"Unzulässige Funktion."

It doesn`t matter what project i open, the error is still there

My windows is set to german language, my visual studio is english. I tried to change the language of visual studio also to german to match the language of windows, but the error was still there just in german.

I tried also uninstalling and installing of the modules "C++ Profiling" and "Test tools for core features" with the Visula Studio Installer.

Also a repair run with the Visual Studio Installer didn`t help.

Henry
  • 1
  • 1
  • 2
    Wayyyyy too little information to be able to help you. Please give a [mcve]. – JHBonarius Dec 04 '20 at 07:46
  • I can´t give an example, the error is not specific to the c++ project. It doesn`t matter what project i open, the error is still there. It seems that the VS2017 installation is somehow broken. I tried also uninstalling and installing of "C++ Profiling" and "Test tools for core features". Maybe i have to uninstall and install the whole VS2017. – Henry Dec 04 '20 at 07:54
  • 1
    Unrelated: Do you have to use VS2017? If you are not forced to use that version, do a fresh installation of VS2019. – Ted Lyngmo Dec 04 '20 at 07:55
  • 1
    O.T.: _I tried to change the language of visual studio also to german to match the language of windows_ I've used various versions of VS with the default lang. choice (German also in my case) for years and always struggled to communicate my issues or fix suggestions in sites like e.g. this one. Recently, I installed a brand-new VS2019 and, this time, I forced it to English. I immediately noticed that googling issues became much easier... ;-) – Scheff's Cat Dec 04 '20 at 08:24

1 Answers1

0

The almost unbelievable solution was to change the environment variable TEMP from R:\Temp back to the standard path C:\WINDOWS\TEMP. (R: is a RAM disk.)

Scheff's Cat
  • 19,528
  • 6
  • 28
  • 56
Henry
  • 1
  • 1
  • 1
    you don't want to use ram drive for %TEMP% location, ever! Installers use that path for downloading, saving logs, saving semaphore files or intermediary state, sometimes that requires restart and files will vanish...breaking your installation. That's how updates sometimes manage to brick Windows. If an application can work with volatile cache, it usually would have own setting to point at the preferable location. – Swift - Friday Pie Dec 04 '20 at 09:00
  • I am glad you have got your solution and thanks for your sharing, I would appreciate it if you mark them as answer and this will be beneficial to other community. – Barrnet Chou Dec 08 '20 at 06:16