The fix within the development version works without error.

I am able to use the following and works in both cases:

if($session.FileExists($remotePath)) {
{
Write-Host "Remote file exists."
}
else
{
Write-Host "Remote file does not exist."
}

Thank you for all your work!

I have sent you an email with a development version of WinSCP to address you have used to register on this forum.

Thank you for the fix. It works as expected.

Implemented in PowerShell as function at top of script:

function FileExistsFix
{
[WinSCP.Session]$pSession = $args[0]
[string]$pPath = $args[1]
try
{
$pSession.GetFileInfo($pPath)
return $TRUE
}
catch [$pSession.SessionRemoteException]
{
return $FALSE
}
}

And called within main script body as:

if (FileExistsFix $session $remotePath) {
Write-Host "Remote file exists."
}
else
{
Write-Host "Remote file does not exist."
}

Thanks for your post.

This bug has been added to the tracker:
https://winscp.net/tracker/852

I have documented workaround here:
https://winscp.net/eng/docs/library_session_fileexists

I receive a "Recursive calls not allowed" error connecting to a Cygwin/OpenSSH system via PowerShell/.NET assembly and issuing a Session.FileExists.

Any recommendation?