> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/frequently-asked-questions/cannot-type-in-a-powershell-window.md).

# Cannot type in a PowerShell window

## Problem

When you type commands in a PowerShell window inside the Golden Image or on a user desktop, the characters do not appear. A [known issue](https://github.com/PowerShell/PowerShell/issues/17783) in PSReadline by Microsoft causes this behavior.  

##  Solution

A [known issue](https://github.com/PowerShell/PowerShell/issues/17783) in PSReadline by Microsoft causes this behavior.  

To solve this problem:

1. Close all PowerShell windows.
2. Run the following command in a Command Prompt window:

{% code overflow="wrap" %}

```powershell
powershell -noprofile -command "Install-Module PSReadLine -Force -SkipPublisherCheck" 
```

{% endcode %}

 3\. Confirm the action by pressing the Y button and wait for the installation to complete.

4. Reboot the machine.

If the problem persists, please reach out to our support department.

## Workaround

If the solution above does not work, try copying commands to the PowerShell window, or use Windows Terminal.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/daas-guides/daas-administrators-guide/frequently-asked-questions/cannot-type-in-a-powershell-window.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.