I have two computers where nRF Connect for VSCode behaves differently in the sense that in one computer when I start debug it stops at the first line of the main and I see thread viewer correctly showing the threads and the other computer stops first in the debug at some setup or init script and not in the main. In addition the Thread Viewer is empty.
I use nRF Connect SDK 2.6.1 from c:\ncs\v2.6.1\nrf\west.yml
I did some cleanup by removing VSCode, Segger probe softwares, nRF Connect for Desktop and tools. Then I searched in Windows in %USERPROFILE% and %APPDATA% Local and Roaming anything I could find related to nRF, VSCode, Segger tools. Then I reinstalled and I use a shared profile and the same nRF52840DK board. In the profile is installed nRF Connect for VSCode Extension Pack, which in turn install what is needed.
Despite repeating the same cleanup and setup, in the home computer it works, and in the workplace doesn't.
I have a feeling that there are some hidden configs which I don't know, therefore is not enough to uninstall and cleanup in %USERPROFILE% and %APPDATA% .
I really wished to have reliable and repeatable setup. Does anybody where it is saved the configuration regarding where it stops first at the staring point of Debug session?
Where exactly have to be made manual cleanup, to completely reset the developer environment?