SSH is not recognized as the name of a cmdlet - client is installed and path is correct

The OpenSSH client is installed. To be sure everything was OK I removed it and reinstalled, but that made no difference.

The Path variable included OpenSSH.

Windows Explorer shows that the folder C:\Windows\System32\OpenSSH exists.

Via Powershell, this folder does not exist. And SSH does not work. Well, the OpenSSH server works, but the client not.

How can I start the OpenSSH client on this system?

I think the errors are caused by using Powershell(x86) instead of Powershell. When using Powershell(x86), I also get an error:

But if I use Powershell, then everything is normal

Powershell (x86) is the 32-bit version while Powershell is the 64-bit version as described here:

On a Windows 64-bit edition, you will find a 32-bit and a 64-bit version of PowerShell for backward compatibility purposes. If you type “PowerShell” on a Windows Start Screen, you will see “x86” behind the 32-bit versions of PowerShell and PowerShell ISE.

By and large, the 64-bit and 32-bit PowerShell versions are compatible, and you shouldn’t notice much of a difference. Problems can arise if binaries are involved. For instance, if you want to extend PowerShell with snap-ins (compiled cmdlets), you have to ensure that you download the correct version. You can also run into problems if you want to instantiate an object of a 32-bit application (Microsoft Office, for example) with the 64-bit version of PowerShell.