title: "Timed out waiting for debuggee to spawn" error for certain conda envs on vs code?
body: <p>Update:</p>
  <p>I just discovered that with a python 3.7 environment created with <code>Anaconda</code> (version number 4.11.0, which creates a python 3.7.11), this problem happens while python 3.8(.12) created by conda doesn't have this kind of problem.</p>
  <p>And I found a solution: I use <code>integratedTerminal</code> in the launch.json, and without specifying terminal type, the default integrated terminal would be <code>PowerShell</code> which has this problem. After I change the <code>terminal.integrated.shell.Windows</code> setting to cmd.exe, this porlbem goes away and the problem goes through.</p>
  <p>Original post:</p>
  <p>I am developing a python 3.7 application on <code>vs-code</code> on Windows. I am using Anaconda to manage my working environments (and I have created several evns on the same dev machine). The env I am using for this app is called <code>basic_env</code> which is of version 3.7.10. Previously it was working fine. But today, when I returned from my 10-day holiday, and after I upgraded the vscode (to <code>1.64.0</code>) and probably the python extension (version <code>v2022.0.1786462952</code>). The launching/debugging stopped working: a window popped up with an error mesage <code>Timed out waiting for debuggee to spawn</code> . I made a simple test python script using the same conda env. My script is only one line</p>
  <pre><code>print(&quot;test....&quot;)
  </code></pre>
  <p>And my launch.json looks like this:</p>
  <pre><code>{
          &quot;name&quot;: &quot;Python: Current File&quot;,
          &quot;type&quot;: &quot;python&quot;,
          &quot;request&quot;: &quot;launch&quot;,
          &quot;program&quot;: &quot;${file}&quot;,
          &quot;console&quot;: &quot;integratedTerminal&quot;,
          &quot;env&quot;: {
              &quot;PYTHONPATH&quot;: &quot;${workspaceFolder}&quot;
          },
      },
  </code></pre>
  <p>The same error showed up.</p>
  <p>I tried to google this issue, at first I thought <a href="https://github.com/microsoft/ptvsd/issues/1930" rel="nofollow noreferrer">this post</a> was the same as my problem: using venv caused this problem, and using the system-global python didn't have this problem. So maybe the bug which was fixed 2 years ago was back along with the updates? But then I tried some other conda envs, some worked and some didn't (but none of them was of version 3.7.10). I tried to upgrade this env to 3.7.11 by:</p>
  <pre><code>conda activate basic_env
  conda install python=3.7.11
  </code></pre>
  <p>(other existing 3.7.11 envs work fine) but the problem was still there. Also, I don't know how to get the ptvsd.adapter log file in the mentioned post. Could anyone help me track this problem?</p>
  <p>Thank you very much!</p>
  <p>Cheers</p>