> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-nordics/v400c/errors/wont-start.md).

# Won't Start

What to do when your V400c won't start — restart it with the buttons, then check the power and cables.

{% hint style="info" %}
**Use this page when** your terminal won't start up, is frozen, or isn't responding.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: won't start, won't turn on, won't power on, frozen, not responding, stuck, black screen, restart. Search terms: won't start, restart, reboot, green and red button, frozen, black screen, power cable, cables.

</details>

## Symptoms

You may see one or more of the following:

* The terminal won't start up.
* The terminal is frozen or doesn't respond when you press the buttons.

**Why this happens:** the terminal may have stopped responding and needs a restart, or a cable may be loose.

## Resolution

{% stepper %}
{% step %}

### Restart the terminal with the buttons

1. Hold down the **green (✓)** and **red (X)** buttons at the same time.
2. Keep holding until the screen goes **black**.
3. When the screen goes black, **release the red button** — but keep holding the **green button**.
4. When the screen turns **white**, release the green button.

The terminal should now restart.

✅ **Terminal starts — stop here.** ❌ **Still won't start — continue to Step 2.**
{% endstep %}

{% step %}

### Unplug the power cable

1. Unplug the **power cable** from the terminal.
2. Wait **10–15 seconds**.
3. Plug the power cable back in and wait for the terminal to start up.

✅ **Terminal starts — stop here.** ❌ **Still won't start — continue to Step 3.**
{% endstep %}

{% step %}

### Unplug and reconnect all cables

1. Unplug **all** cables from the terminal — for example the power cable, network cable, and dongle.
2. Wait a few seconds.
3. Plug all the cables back in. If you're not sure where each cable goes, see [How to Connect the Cables](/support-nordics/v400c/how-tos/how-to-connect-the-cables.md).
4. Wait for the terminal to start up. If it doesn't, try the button restart again, as in Step 1.

✅ **Terminal starts — stop here.** ❌ **Still won't start — contact Support below.**
{% endstep %}
{% endstepper %}

**If the terminal starts.** It's ready to use.

**If the terminal still won't start.** Contact Support below.

## Still not working?

{% hint style="info" %}
**Still need help? Contact Verifone Support.**

If the steps above haven't resolved the issue, <mark style="color:red;">contact Verifone Support</mark>. Tell us the troubleshooting steps you've already tried — it helps us get you to the right support faster.
{% endhint %}


---

# 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.verifone.com/support-nordics/v400c/errors/wont-start.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.