VS installation fails on PowerShell 2.0

[jberezanski]

On Windows 7 with .NET 4.6.1 and choco 0.10.15:

cinst -ydv visualstudio2017buildtools --version 15.0.26228.0

Parsing the component manifest
VERBOSE: Required engine version determined from the component manifest: '1.18.1049.33485'
Running 'Install-VSInstaller' for visualstudio2017buildtools with Url:'https://download.visualstudio.microsoft.com/downl
oad/pr/82e3dcda-e8a0-44e4-8860-eb93a12d4e80/debc235546e664edf27e81d2945921eb58e8bfec4f4e6eb271fecb9aca320b76/vs_BuildToo
ls.exe' Checksum:DEBC235546E664EDF27E81D2945921EB58E8BFEC4F4E6EB271FECB9ACA320B76 ChecksumType:SHA256 RequiredInstallerV
ersion:'1.18.1104.625' RequiredEngineVersion:'1.18.1049.33485' Force:'False' UseInstallChannelUri:'False' DoNotInstallIf
NotPresent:'True'
Determining whether the Visual Studio Installer needs to be installed/updated/reinstalled
VERBOSE: Visual Studio Installer is not present.
The Visual Studio Installer is not present
VERBOSE: No ISO to dismount
ERROR: Command execution stopped because the preference variable "ErrorActionPreference" or common parameter is set to S
top: The input object cannot be bound to any parameters for the command either because the command does not take pipelin
e input or the input and its properties do not match any of the parameters that take pipeline input.
    at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable error
Results, Boolean enumerate)
   at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionCo
ntext context)
   at System.Management.Automation.ParseTreeNode.Execute(Array input, Pipe outputPipe, ExecutionContext context)
   at System.Management.Automation.AssignmentStatementNode.Execute(Array input, Pipe outputPipe, ExecutionContext contex
t)
   at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputP
ipe, ArrayList& resultList, ExecutionContext context)

[jberezanski]

Works correctly after upgrading PowerShell to 3.0.
(or, rather, the native VS installer fails, but the package scripts execute correctly)

[jberezanski]

Full success after .NET upgrade to 4.6.2.