Errors in Integrated Console when invoking some native applications (PSHostRawUserInterface)

System Details

• Operating system name and version: Windows 10 Insider 16232
• VS Code version: 1.14.1
• PowerShell extension version: 1.4.1
• Output from $PSVersionTable: Name Value

---

PSVersion 5.1.16232.1000 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} BuildVersion 10.0.16232.1000 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1

Copy / paste the below commands into the PowerShell Integrated Terminal, and paste the output here

code -v
$pseditor.EditorServicesVersion
code --list-extensions --show-versions
$PSVersionTable

Issue Description

In VSCode Integrated Terminal when using “Start-Transcript”, external commands (e.g. git.exe/ipconfig/nbtstat/etc/etc/etc) run as expected, but on completion a spurious error message is displayed.

This occurs if Start-Transcript is entered manually into the integrated console or if Start-Transcript is included in Profile.ps1. The error does not occur if transcripts are not being collected (or if Stop-Transcript is used).

The issue only occurs with external (.exe/.com etc) commands. Cmdlets do not cause a problem.

(I have tested with no profile scripts to eliminate anything in my profile)

More info available on request…

Attached Logs

#Example

PS C:\Data\Git> Start-Transcript -OutputDirectory ‘C:\Data’ PS C:\Data\Git> PS C:\Data\Git> arp /?

Displays and modifies the IP-to-Physical address translation tables used by <…snip…>

arp -a … Displays the arp table. Program ‘ARP.EXE’ failed to run: The method or operation is not implemented.At line:1 char:1

• arp /?

At line:1 char:1

• arp /?

•   + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed
  
  

PS C:\Data\Git>

[daviwil]

@dlwyatt Thanks Dave! I don’t know why I didn’t look at the call stack and actually figure out why this was happening. Looks like if I implement the method enough to satisfy this code the problem should go away:

https://github.com/PowerShell/PowerShell/blob/7c9b188c135ed001093641698d48a22fd016f6ab/src/System.Management.Automation/engine/NativeCommandProcessor.cs#L713

I’ll try to throw that in with the next Editor Services update.

[BladeFireLight]

I looking forward to this fix. We have transcription on via Policy also. right now any try/catch with a native command fails 100% of the time.