I also found that by having a command in Microsoft.PowerShell_profile in C:\Users\MyUserName\Documents\WindowsPowerShell that prompted for input caused the Emulator to get stuck because it uses that profile just like any other PowerShell session. Removing the prompt allowed it to work properly.