POS Terminal Stuck on a Boot Logo?
Read the Screen Before You Reinstall.
A terminal that reaches its splash screen and then stops has already told you something useful: the power supply is working and the board firmware has started. The fault sits further along the chain, in storage, in the operating system or in a device attached to the terminal. It follows the same order used across our retail hardware troubleshooting guides.
Which Boot Fault Do You Have?
“Stuck on the logo” describes at least five different faults. What happens in the seconds after the logo appears narrows it down before anything is opened, so watch the sequence twice and write down what you saw. That order is the evidence.
| What you see | What it usually means | Where to start |
|---|---|---|
| Logo appears, then the screen freezes with no further movement | Storage is detected, but the operating system will not start | Layer 5 — Software |
| Logo appears, then the terminal restarts and repeats | A boot loop: storage, power or thermal | Layer 1 / Layer 6 |
| Logo, then a black screen with a boot device error or a blinking cursor | The boot order is wrong, or the storage device is not being read | Layer 3 / Layer 6 |
| Logo appears and the progress animation stalls part way | Firmware or graphics initialisation does not complete | Layer 4 — Driver |
| Logo appears only when a USB stick or scanner is unplugged | A peripheral is taking the boot order | Layer 2 — Cable |
| Logo appears, then the unit restarts when the printer or drawer is attached | Power sag or a peripheral fault on the shared port | Layer 1 / Layer 2 |
| Logo stays for several minutes, then Windows eventually loads | Storage wear, or an over-loaded start-up sequence | Layer 6 — Hardware |
| No logo at all, not even a backlight | No display, or no power reaching the board | See the black screen guide |
Logo, then it hangs
The firmware found a bootable device, started reading it, and then stopped. That points at the operating system itself, at a failed update, or at a driver that loads early and never returns. Storage is usually present, so reinstalling is a later step rather than the first one.
Logo, then it restarts
A restart during boot is a different animal. The board is being reset, either because the drive stops answering, because the supply cannot hold up, or because the machine is protecting itself from heat. Note how far the progress indicator gets, and whether the fault arrives sooner from cold.
Nothing at all
If the screen never lights, this is not a boot fault. Display, backlight and power faults all look like this from the front of the counter, so start with the black screen diagnosis before reading further here.
Work Through the Layers in Order
A boot loop and a failed drive look identical from a meter away. Working outward-in is what stops a loose connector becoming a reinstall, and a reinstall becoming an unnecessary one.
Layer 1 — Power
A restart during boot is very often a supply problem rather than a software problem. Confirm the adapter is the rated unit for the model, that the DC plug is fully seated, and that nothing else high-draw shares the same outlet strip.
A marginal adapter that lights the indicator can still collapse when the drive and the display draw their start-up current together. If the terminal restarts at the same point every time, and sooner from cold, suspect the supply and the thermal path.
Layer 2 — Cable
This is the least expensive layer and the one that is skipped most often. Every USB device on the terminal is a candidate boot device as far as the firmware is concerned, and a scanner, a USB stick or a card reader left in place can hold the boot order.
Disconnect power, unplug every peripheral, and start the terminal with nothing attached except the display and the keyboard. Reconnect one device at a time afterwards. Inside the casing, the drive and its connector are also a cable-layer item on models where they are reachable without a full strip-down.
Layer 3 — Media, replaced by the boot medium
A POS terminal has no print consumable, so the media layer is read here as the boot medium itself: the storage device the firmware is trying to start from. The equivalent check is whether that device is present, seated and readable, and whether the firmware is being asked to start from the right one.
Two questions settle it. Is the drive listed in the board setup screen, and is it listed first? A drive that appears but is not first is a configuration fault, while a drive that does not appear at all has moved on to Layer 6.
Layer 4 — Driver
Two driver-layer faults produce a logo that never clears. The first is a storage controller mode that no longer matches how the drive was prepared, where switching between the legacy compatibility mode and the native mode leaves the operating system unable to read its own boot volume. The second is a graphics or chipset component that loads early and never hands over, which shows as a terminal that draws part of the progress animation and then stops but behaves correctly in a reduced-resolution mode.
Layer 5 — Software
This is where most stuck logos actually live. A failed or interrupted update, a damaged boot configuration, or a boot partition that lost its boot record all produce the same picture: a logo, then nothing.
The test is whether the terminal can start in a reduced mode or reach a recovery environment. If it can, the drive is healthy and the problem is in the installation. If it cannot, keep reading down the layers rather than starting a reinstall, because a reinstall on a failing drive will not hold.
Layer 6 — Hardware
The storage device, the memory and the mainboard sit here. Storage wear is the usual candidate on a terminal that has run for years of continuous shifts: the drive still answers, but not quickly or reliably enough to complete a boot.
A drive that is warm, that appears and disappears between restarts, or that fails to appear in the setup screen at all is a Layer 6 part. Board-level faults, where a drive confirmed working elsewhere is never detected, belong with your supplier.
Four Steps, in This Order
These four steps take the terminal from a stuck logo to a working desktop, or to a clear decision that the machine needs a part. Do them in sequence, because each one changes what the next one means.
Disconnect every external device
Power the terminal down, then unplug everything: USB sticks, scanner, printer, customer display, card reader, drawer lead, external keyboard, network cable. Leave only the display and the power adapter connected, and start the terminal again.
This step resolves the largest share of boot-logo calls, and it costs two minutes. If the terminal starts, reconnect the peripherals one at a time. If it still hangs with nothing attached, the fault is inside the terminal.
Confirm the storage is listed in setup
Restart the terminal and tap the setup key repeatedly as the logo appears. On TillNode terminals the key is one of Del, F2 or Esc, depending on the board. A USB keyboard can be plugged in for this if the terminal has no attached one.
- · The drive is listed and set first — storage and boot order are fine, so the fault is in the operating system. Go to step 3.
- · The drive is listed but is not first — correct the boot order, save and restart, then re-check before doing anything else.
- · No drive is listed at all — the terminal cannot see its storage, so treat it as a storage fault and read the next section.
Start in a reduced mode before you reinstall
A terminal that can start in a reduced mode, or reach a recovery environment, has a healthy drive and a damaged installation. That distinction saves a reinstall, and it saves the data on the drive. Interrupt the start-up twice during the animation, or use the recovery key combination for your model, and see what offers itself.
If a reduced mode starts, use it to undo the change that broke the boot: roll back the last driver, remove the update applied just before the fault first appeared, or revert the graphics component. If a reduced mode will not start either, the operating system needs restoring, which is a different job with its own safeguards.
Restore or reinstall the operating system
Restoring is the last of the four steps, not the second. Once you have established that the drive is detected, that no peripheral is involved and that a reduced mode will not start, the installation itself is the remaining candidate.
Back up first. POS configuration, license keys and any locally stored transaction data all have to be captured before the boot volume is touched. If the drive was replaced rather than repaired, the reinstall is mandatory, because a new drive arrives empty.
When It Is the Storage
A drive the setup screen cannot see, or one that appears and disappears between restarts, has moved from a software question to a parts question. Whether you can replace it depends entirely on the platform, and that is decided before any part is ordered.
✓ Windows platform — replaceable
- · Storage on a Windows terminal is an M.2 or mSATA module and can be replaced in the field
- · Models include the SN-B10, B20, C20, C30, F20, W50 and P10 to P90 series
- · Memory, the mainboard fan and the CMOS battery are replaceable on the same boards
! Android platform — soldered
- · On an Android terminal the storage is eMMC soldered to the board, together with the memory
- · Models include the SN-A10, SN-A15 and SN-F10
- · A soldered storage fault is a return-to-supplier job, handled as a board repair or exchange
Before you condemn the drive
Three cheap checks separate a drive that has failed from one that is merely not being read. Reseat the module and its connector and check detection on the next start. Confirm the boot order has not changed. Then confirm the drive is genuinely the one the terminal is trying to boot. A drive that is consistently detected but fails to start an installed operating system is a software problem on a working drive, while a drive that is consistently absent after reseating is a hardware fault.
Repair or Replace
Most boot-logo faults are resolved without a part. The ones that need a part are predictable, and so are the ones that should go back to the supplier.
✓ You can do this on site
- · Disconnect every peripheral and start with a clean set of connections
- · Correct the boot order in the board setup screen
- · Reseat the storage module where the model gives access to it
- · Start in a reduced mode and roll back the change that caused the fault
- · Replace the storage and memory on a Windows terminal
- · Restore or reinstall the operating system with the vendor image
! Contact your supplier
- · Storage is still absent from the setup screen after reseating
- · Soldered storage or memory on an Android terminal
- · Data recovery from a drive that no longer answers
- · A board-level fault, where a known-good drive is never detected
- · A boot loop that repeats with the storage and the supply both confirmed
Warranty and self-repair
Opening the casing to reseat a drive, or to fit a replacement module, does not by itself void warranty cover for non-human-induced defects. If the terminal later develops a fault unrelated to your work, it remains eligible.
Damage caused during the work is not covered. That includes static discharge, a connector or ribbon broken during removal, forcing a module into a slot, fitting an incompatible part, and liquid ingress. Replacement drives and spare parts carry their own warranty period.
Safety boundaries
- · Disconnect power and hold the power button for five seconds before opening the casing or touching the storage module.
- · Never flash firmware that did not come from your supplier. Firmware is updated over a verified channel, and an unofficial image can leave the board unable to start at all.
- · Back up configuration, license keys and local transaction data before any restore or reinstall. There is no second chance after the boot volume is written.
- · Do not reinstall onto a drive you suspect of failing. A restore onto a worn drive ends in the same boot loop, with the backup window spent.
- · Wear an anti-static strap whenever the casing is open. Retail floors and back offices are dry, and static damage to a module is permanent.
Related Troubleshooting Guides
Once the fault is narrowed to storage or to the installation, the guides below take the next half of the job.
POS Screen Is Black But the Terminal Is On
When there is no logo at all, confirm whether the display is being driven before reading a boot fault into it.
Windows OS Recovery on a POS Terminal
The recovery paths, the recovery environment and the clean-install procedure, with the backup order that goes first.
Upgrading RAM and SSD in a POS Terminal
Which platforms take a field-replaceable drive, and which have storage soldered to the board.
Mini PC Will Not Power On
The power and firmware checks that apply to the same industrial boards used inside Windows terminals.
Browse All-in-One POS Terminals
Terminals built with field-replaceable storage and memory, so a boot fault stays a same-day job.