> Source: [sk93411](https://support.checkpoint.com/results/sk/sk93411)

# sk93411 - Logging in with WinSCP causes CLISH process to utilize 100% CPU or a connection timeout 

| Property | Value |
|----------|-------|
| Solution ID | sk93411 |
| Date Created | 2013-07-07 |
| Last Modified | 2020-06-18 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * When the user tries to log in with WinSCP, the CLISH process reaches 100% CPU utilization.
* In R77.30 and R80.10, the user might see the following error: ` Connection has been unexpectedly closed . . . Server sent command exit status 0 . . . Error skipping startup message. Your shell is probably incompatible with the application (BASH is recommended).`  

  ![](https://sc1.checkpoint.com/sc/SolutionsStatics/sk93411/Untitled1804240144.png)

## Cause

The account default shell is CLISH instead of /bin/bash.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content