> 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/v660p/errors/stuck-checking-for-updates.md).

# Stuck Checking for Updates

What to do when a V660P gets stuck on the Checking for Updates screen during setup.

{% hint style="info" %}
**Use this page when** a new terminal won't move past the **"Checking for updates"** screen during setup.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: stuck checking for updates, stuck on updates, setup stuck, looping updates, won't finish setup, no device ID prompt, wrong device ID. Search terms: checking for updates, stuck, setup, device ID, updates loop, OOBE, reset setup wizard.

</details>

## Symptoms

You may see one or more of the following:

* The terminal stays on the **"Checking for updates"** screen and won't move on.
* The screen keeps looping and never asks you to enter a **Device ID**.
* You entered a Device ID during setup, but it may have been incorrect.

**Most likely cause:** the terminal hasn't received a valid Device ID, so it can't finish setting up.

## Which situation matches yours?

Pick the one that matches what you're seeing.

<details>

<summary>The terminal never asked me for a Device ID</summary>

If the terminal keeps looping on the "Checking for updates" screen and never asks for a Device ID:

{% stepper %}
{% step %}

### Open the information panel

On the "Checking for updates" screen, tap the **information icon (ⓘ)** in the top-right corner. A small panel opens over the screen.
{% endstep %}

{% step %}

### Show the connection address

In the panel, find **Terminal Management** and tap **Show URL** next to it. This shows the web address the terminal is trying to connect to.
{% endstep %}

{% step %}

### Check the address

You only need to look at the start of the address:

* If it begins with `vhqhome.verifonehq.net`, the terminal is pointing to the wrong place and will need to be **swapped** — see **Still need help?** below.
* If it begins with `vhq2.vfims.com`, that's the **correct** address — carry on to the next step.
  {% endstep %}

{% step %}

### Reset and set up again

Tap **More info** at the bottom of the screen, then scroll to the very bottom and tap **Reset Setup Wizard**. When the terminal restarts, follow the [Terminal Setup (Out of Box)](/support-nordics/v660p/how-tos/terminal-setup-out-of-box.md) guide to set it up again.
{% endstep %}
{% endstepper %}

</details>

<details>

<summary>I entered the wrong Device ID</summary>

If setup got stuck because the wrong Device ID was entered, reset the terminal and enter the correct one:

1. On the stuck screen, tap **More info** at the bottom, then tap **Reset Setup Wizard**.
2. Set the terminal up again using the [Terminal Setup (Out of Box)](/support-nordics/v660p/how-tos/terminal-setup-out-of-box.md) guide.
3. When you're asked for the **Device ID**, enter the correct one. You'll find it on your **welcome email**. If you don't have the email, <mark style="color:red;">contact the Helpdesk</mark> and we'll help you find it.

</details>

## Still need help?

{% hint style="info" %}

* **If the terminal needs to be swapped** (its connection address was wrong), <mark style="color:red;">contact Support to log a replacement terminal</mark>.
* **For anything else** — including finding your Device ID — <mark style="color:red;">contact Verifone Support</mark>.
  {% 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/v660p/errors/stuck-checking-for-updates.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.