Commands fail if in a remote session to Windows

[beechtom]

Originally reported as BOLT-1075

Issue

If you are remoted into a Windows machine and attempt to run a command, the command may fail with an Bad file descriptor error.

This was discovered during the Getting Started with Puppet training class.

This issue specifically arose out of entering a remote session with Enter-PSSession and then using the --password CLI option without a password after it, causing Bolt to prompt for the password.

Workaround

Interactive tools fail when run in a remote PowerShell session. For example,
using --password-prompt to prompt for a password when running Bolt triggers an
error. As a workaround, consider putting the password in a configuration file such
as bolt-defaults.yaml or bolt-project.yaml, in an inventory file, or passing the password
on the command line.