Die Fehlermeldungen lauten:
1.      VS2022: „Unable to start debugging. Unable to establish a connection to GDB. Debug output may contain more information.“
2.      Der letzte Debugger-Befehl endet mit Fehler:  exited with code 1 (0x1).
3.      Setze ich den Befehl mit CMD kommt das Ergebnis:
\vmicro\\tools\\openocd-espressif-esp32-10.0.1\bin/openocd.exe"
Open On-Chip Debugger  v0.10.0-esp32-20190313 (2019-03-13-09:57)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
embedded:startup.tcl:63: Error: Can't find openocd.cfg
in procedure 'script'
at file "embedded:startup.tcl", line 63
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: Debug Adapter has to be specified, see "interface" command
embedded:startup.tcl:63: Error:
in procedure 'script'
at file "embedded:startup.tcl", line 63
4.      In Blink5.ino_DebugOpenOCD steht:
none
adapter speed: 2000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
Error: No J-Link device found.

Warn : Flash driver of esp32.flash does not support free_driver_priv()
Warn : Flash driver of irom does not support free_driver_priv()
Warn : Flash driver of drom does not support free_driver_priv()
Eine Neuinstallation von vMicro hat nichts gebracht. Was wäre da noch zu tun?

Die Schnittstelle wurde mit der Version Zadig V2.8 installiert. Mit folgendem Befehl wird meiner Ansicht nach der JTAG-Adapter erkannt? 
C:\ProgramData\vmicro\tools\openocd-espressif-esp32-10.0.1\bin>openocd -s tcl -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg
Open On-Chip Debugger  v0.10.0-esp32-20190313 (2019-03-13-09:57)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
none separate
adapter speed: 2000 kHz
Info : Configured 2 cores
esp32 interrupt mask on
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 2000 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32: Debug controller 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 0 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Debug controller 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : esp32: Core 1 was reset (pwrstat=0x5F, after clear 0x0F).
Info : Listening on port 3333 for gdb connections

I thought I had a Segger J-Link. But it is an ESP32 PROG and is connected as shown on your website. Now ESP32 PROG is also set in the debugger. The exit code is 1 (0x1).

I therefore set the output in Blink to GPIO 5.

The error message appears:
Microsoft Visual Studio
Unable to start debugging. Unexpected GDB output from command "-target-select remote localhost:3333". Remote communication error. Target disconnected.: (undocumented errno 10061).

"openocd.exe" or "xtensa-esp32-elf-gdb.exe were not active. I ran the debug option “Attach to process” again and the debugger stopped at the breakpoint!!! Why only now? I I'll continue testing and report back.

If you press the Debug > Start button it will perform the build and upload operations, and then automatically start the debugging process.

I can debug with the following process:
After starting with the “Start” button, the program is loaded onto the ESP32 after compiling. When the write cycle is around 70%, I call “Attach to Process” using the Debug button. Now debugging will start. The debugger stopped at the breakpoint. The message comes from VS: “Do you want to stop debugging? Yes No". If no, I can work with the debugger. This works with all other programs too.