Skip to content

PowerShell does not support debugging this file type: 'extension-output-#4'. #1763

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ramroumlevrai opened this issue Feb 17, 2019 · 5 comments

Comments

@ramroumlevrai
Copy link

System Details

System Details Output

### VSCode version: 1.26.1 493869ee8e8a846b0855873886fc79d480d342de x64

### VSCode extensions:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]


### PSES version: 1.11.0.0

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.17763.316
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.316
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

I am experiencing a problem with the debugger, I get the following Error: PowerShell does not support debugging this file type: 'extension-output-#4'.

I've tried with different scripts, even simple ones and still the same error happens.

Expected Behaviour

I should be able to debug a PowerShell Script

Actual Behaviour

I can't the debug doesn't even execute due to the error

Attached Logs

Follow the instructions in the troubleshooting docs
about capturing and sending logs.

@TylerLeonhardt
Copy link
Member

Thanks for the info! Can you also attach the logs here so we can get a better idea of what's going on?

@TylerLeonhardt
Copy link
Member

Screenshots or gifs of your issue would be most helpful too!

@SydneyhSmith
Copy link
Collaborator

Closing this issue as inactive but will re-open if more info is provided!

@markcelo
Copy link

markcelo commented Nov 8, 2022

I experienced this issue with the debugger, even when the debugger worked right after installation.

It is easy to mistakenly add extra debugging configurations from the Debugger view of VC. If you got extra template of actions they are generic and not fully specified which caused the issue for me.

@ghost
Copy link

ghost commented Nov 8, 2022

Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants