Vagrant Manager throws error using new Windows Terminal

[thetreythomas]

Describe the bug
If you are using the new Windows Terminal to launch PowerShell, Vagrant Manager throws an error.

To Reproduce
Steps to reproduce the behavior:

1. Have the new Windows Terminal installed
2. Launch PowerShell through Windows Terminal
3. Have a vagrant instance running
4. Start Vagrant Manager

Expected behavior
For Vagrant Manager to be able to detect the correct version of PowerShell when ran through Windows Terminal.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10, Version 1903 (OS Build 18362.418)

Additional context
Windows Terminal will be released officially in the May 2020 Windows 10 release, and appears to be the future for command line on Windows 10/Windows Server.

You can download it here:
https://github.com/microsoft/terminal

Release Information:
https://github.com/microsoft/terminal/blob/master/doc/terminal-v1-roadmap.md

[absalomedia]

As we're using node-vagrant inside Vagrant Manager, this looks to be an upline dependency issue in creating that command line call. The error you're experiencing has happened repeatedly across Vagrant itself & differing versions of Powershell e.g hashicorp/vagrant#8783 (comment)