I downloaded the trial version and spent some time trying to use it, with VS 2022 on Windows 11. It looks great, but there seem to be some things which are not working properly. Probably I'm doing something wrong. Can anyone help me?
1)      The “Micro Explorer” window is empty (all white), and I can’t use it. Why is this? How can I fix it? See first pic1 below. (Update: I tried it on my old Windows 10 machine, and this is working.)
2)      When I create a new project it now says “(Linux)” after the Sketch4 name, but I’m using Windows. The first project I created did not have this. This happened after I un-installed and re-installed the trial version in VS.
3)      The breakpoint works the first time I build and download (by pressing "> Start"). But after that it does not work, unless I close Visual Studio and re-open it, then it works well, just once. (Update: I have the same problem on my Windows 10 machine.)
4)      I get some OpenOCD errors when I start debugging by pressing “> Start”, see Output Window pic2, but the breakpoints work. The second time I run it, there are no errors, but breakpoints don’t work and the program does not seem to run, see pic2. Closing and opening VS makes it work, only once.

Micro Explorer window is not usable:


Output Window clip 1, the first time “> Start” is pressed, there are some errors, but it runs and the breakpoint is hit.
Output Window clip 2, pressing “> Start” the second time, the program downloads but does not run, no breakpoints etc.

Log file attached

Micro Explorer UI:

Can you try the latest release (2022.11.28-2) available from the top of the board below, and let us know if this resolves this part of the issue?
https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

Could you answer the below points so we can try to isolate the issue with the Micro Explorer:
1) Does the Serial Monitor work correctly?
2) Can you confirm which Theme you are using in Visual Studio?
3) Can you send us the JSON URL's (if any) which are added for the selected IDE on the IDE locations screen?

Thanks for the update, and the Arduino 2.x or Arduino 1.6/1.8 are the same ones selected on the vMicro > IDE Field.  Multiple can be configured to allow you switch easily between versions of the Arduino IDE or other IDE's such as Energia from TI.

The Arduino2 location isn't user configurable, and as the 2.x IDE does not come packaged with any boards (as the 1.x used to), we don't need to know its location so this is correct.

The 1.6/1.8 IDE location is normally either in C:\Program Files when using the installer, or a folder outside of LocalAppData if you installed from ZIP.  If you do not have the Arduino 1.x IDE installed on your machine the value can be deleted.   

Do you have the 1.x version of the Arduino IDE in C;\Users\matth\AppData\Local\Programs\Arduino IDE?

The IDE locations window allows you to cofigure more than one IDE. It always shows the full list of IDE's available for configuration. You do not select an IDE for use within that window, just configure locations if you want to work with more than one IDE.

You can then select an IDE and board for each project. You have Arduino 2 selected for the project in one of your earlier screen shots. The project will remember which you have selected.

You don't normally need any IDE's installed but because the platform explorer is not working for you then you need to use the board manager in arduino 2 or arduino 1 to install boards. We can see in your screen shot that you already have installed boards. Therefore, you don't need the platform explorer at this time.

You don't need the reset but it is available via "Tools>Import and Export Settings".

Hi Simon,
Simon@Visual Micro wrote on Dec 14^th, 2022 at 1:55pm:

Main screen: 175% (Recommended), 3840x2160 (Recommended)
Laptop screen: 150% (Recommended), 2560x1440 (Recommended)
Some dialog boxes are not well scaled, see the "Configure IDE Locations" screen shots above, but this does not account for the other behavior.

Forgive the delay (my evaluation license had expired).

I have updated to the latest version of Visual Micro, and I can confirm that the problems I had with the blank Micro Explorer and Serial Monitor windows on Windows 11 is now fixed.

But I still have problems when attempting to debug a simple sketch:

I’m using an Arduino Zero, VS 2022 latest, Windows 11.

When I open VS and press Start for the very first time, everything works perfectly. The breakpoint is hit, and I can step through the code. See 1st pic in attachment screenshots-20230420.pdf, and 1st log in log-20230420.txt.
But if I press Stop Debugging, then press Start for a second time, it does not work. The system seems to hang. The breakpoint is not hit and nothing works. See 2nd screenshot and log.
(But I don’t think you can see much from the screenshots.)
Pressing pause (Break All) causes the “Frame not in module” error, which I mentioned before. See 3rd screenshot.

Could there be something wrong with my configuration? (I do not understand all the “General / Global Options”, so I have not changed them.) Maybe I need a driver?

I have exactly the same behaviour on both my old Windows 10 machine and the new Windows 11 machine.
The Arduino IDE 2.0.4 works well on both machines. 
I tried the latest version of openocd, but that does not seem to make any difference to the behaviour.

Additional: Cosmetic. Visual Micro’s comment for the “Stop Debugger” button, when you hover over the button, suggests pressing CTRL+F5, but that does nothing. Should this be SHIFT+F5?

After pressing Stop Debugging (SHIFT+F5), arm-none-eabi-gdb.exe is still running. End Task does not help, neither does resetting the Zero.

In one instance I had a different set of errors:

-------------------------------------
Uploading 'Sketch3' to 'Arduino Zero (Programming Port) (arduino_zero_edbg)' using 'COM9'
Uploader started for board Arduino Zero (Programming Port) (arduino_zero_edbg)
Upload method will be: bootloader
Uploading via Bootloader 
uino7\bin\openocd.exe -d2 -s duino7/share/openocd/scripts/" -f riants/arduino_zero/openocd_scripts/arduino_zero.cfg" -c "telnet_port disabled; program ch3.ino.bin} verify reset 0x2000; shutdown"
Open On-Chip Debugger 0.12.0 (2023-01-14-23:37)
Licensed under GNU GPL v2
For bug reports, read
     http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: FW Version = 02.01.0157
Info : CMSIS-DAP: Serial# = OU3D5RJD677YO46I7TWW
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : clock speed 400 kHz
Info : SWD DPIDR 0x0bc11477
Info : [at91samd21g18.cpu] Cortex-M0+ r0p1 processor detected
Info : [at91samd21g18.cpu] target has 4 breakpoints, 2 watchpoints
Info : starting gdb server for at91samd21g18.cpu on 3333
Info : Listening on port 3333 for gdb connections
Error: CMSIS-DAP command mismatch. Expected 0x5 received 0x3
Polling target at91samd21g18.cpu failed, trying to reexamine
Error: CMSIS-DAP command mismatch. Sent 0x3 received 0x5
Error: CMSIS-DAP command CMD_DISCONNECT failed.
Error: CMSIS-DAP command mismatch. Sent 0x12 received 0x2
Info : SWD DPIDR 0x0bc11477
Error: CMSIS-DAP transfer count mismatch: expected 5, got 1
Error: CMSIS-DAP transfer count mismatch: expected 1, got 5
Error: CMSIS-DAP transfer count mismatch: expected 1, got 5
Error: CMSIS-DAP transfer count mismatch: expected 3, got 1
Error: CMSIS-DAP transfer count mismatch: expected 3, got 1
Error: CMSIS-DAP transfer count mismatch: expected 5, got 1
Error: CMSIS-DAP transfer count mismatch: expected 4, got 1
Info : [at91samd21g18.cpu] Cortex-M0+ r0p0 processor detected
Error: CMSIS-DAP transfer count mismatch: expected 3, got 1
Error: CMSIS-DAP transfer count mismatch: expected 2, got 1
Error: CMSIS-DAP transfer count mismatch: expected 2, got 1
Error: CMSIS-DAP transfer count mismatch: expected 3, got 1
Info : [at91samd21g18.cpu] target has 0 breakpoints, 0 watchpoints
Error: CMSIS-DAP transfer count mismatch: expected 3, got 5
Error: CMSIS-DAP transfer count mismatch: expected 5, got 3
Error: CMSIS-DAP transfer count mismatch: expected 5, got 3
Error: CMSIS-DAP transfer count mismatch: expected 2, got 4
Error: CMSIS-DAP transfer count mismatch: expected 4, got 5
Error: CMSIS-DAP transfer count mismatch: expected 1, got 5
Error: CMSIS-DAP transfer count mismatch: expected 5, got 2
Error: CMSIS-DAP transfer count mismatch: expected 1, got 4
Error: CMSIS-DAP transfer count mismatch: expected 1, got 5
Error: CMSIS-DAP transfer count mismatch: expected 3, got 1
Error: CMSIS-DAP transfer count mismatch: expected 5, got 1
Error: CMSIS-DAP command mismatch. Sent 0x10 received 0x5
Error: CMSIS-DAP command CMD_DAP_SWJ_PINS failed.
Error: CMSIS-DAP: Interface reset failed
Error: SRST error
[at91samd21g18.cpu] halted due to debug-request, current mode: Thread 
xPSR: 0x61000000 pc: 0x0000060c msp: 0x20007ffc
Error: CMSIS-DAP transfer count mismatch: expected 2, got 4
** Programming Started **
Error: CMSIS-DAP transfer count mismatch: expected 4, got 2
Error: Couldn't find part corresponding to DID 00000000
Error: auto_probe failed
embedded:startup.tcl:1516: Error: ** Programming Failed **
in procedure 'program' 
The uploader process failed
in procedure 'program_error' called at file "embedded:startup.tcl", line 1581
at file "embedded:startup.tcl", line 1516
Error: CMSIS-DAP command mismatch. Sent 0x3 received 0x5
Error: CMSIS-DAP command CMD_DISCONNECT failed.
----------------------------------

Driver
Could it be the driver? I opened Zadig, and it suggested this:

EDBG CMSIS-DAP (interface 0)
Driver   HidUsb (v10.0.22621.819)  ->  WinUSB (v6.1.7600.16385)

USB cables
I have also tried several different USB cables, with no changes to the behaviour. (And my Wilderness Labs Meadow F7 Feather arrived today, it works well in Visual Studio.)

Thanks. Yes, that seems to have fixed it! A timing problem? I will continue my evaluation...

Just one thing I noticed. If the sketch is running, and I add a new breakpoint by clicking in the margin, then I immediately get a strange exception/interrupt. See attached screenshot. Is this normal? Pressing "Continue >" seems to recover, and the new breakpoint is hit.