Skip to main content

Kiosk: an installation that never completes (no final status)

Applies to: Medulla – Kiosk
Version: All versions
Environment: On-Premise / Private SaaS / Shared SaaS
Category: Kiosk

Symptom: In the Kiosk, a software installation remains indefinitely in the “install in progress” state. The button never changes to “launch” or “delete,” and no error is displayed: no success, no failure, no final status.

This page explains how the installation status is reported to the Kiosk, why it may get stuck, and what to check to resolve the issue.


How the status is normally reported

When the user clicks Install in the Kiosk (see Medulla Kiosk):

  1. The Medulla agent on the workstation sends the installation request to the server.
  2. The server creates a standard deployment of the package on that computer. In the console, this deployment appears in the Audit tab with a name followed by @Kiosk@ (this is what identifies installations initiated from the Kiosk).
  3. During execution, the Kiosk button displays “install in progress.”
  4. When the deployment completes successfully, the button changes to “launch” / “delete”: this indicates the final “installed” status.

In other words, the Kiosk simply reflects the status of the deployment. As long as the deployment has not reached a final status (successful completion or failure), the Kiosk remains at “in progress.” The cause of a status that never finalizes is therefore, almost always, a deployment that never completes.

Starting point for troubleshooting: Open the Audit tab, locate the @Kiosk@ deployment for the affected computer, and check its status and the details of its steps (using the “View deployment details” action). This is where you can see what’s causing the blockage.


Possible causes and solutions

1. The package sequence never reaches its end (END_SUCCESS / END_ERROR)

This is the most common cause. A package is a sequence of steps that must end with END_SUCCESS or END_ERROR (see Create a package). If neither of these outcomes is reached, the deployment—and therefore the Kiosk—remains “in progress.”

Check/correct:

  • In steps of the type Run command or Execute script, check the On return code, goto branch: make sure that a return code always ultimately leads to END_SUCCESS or END_ERROR. An incorrectly configured branch may loop back indefinitely to an intermediate step.
  • Verify that no “goto” jumps create an infinite loop.
  • First test the package via a standard deployment on a test computer: if it still fails to complete during a normal deployment, the problem lies with the package, not the Kiosk.

2. A step is waiting for a response that never arrives

Certain actions put the deployment on hold: User Question, User Postpone Options, or an interactive command. If no one responds and no timeout is set, the step remains blocked.

Check/correct:

  • For these steps, always specify a Set timeout (maximum delay) and an exit path for the cases “no response,” “no user logged in,” and “timeout.”
  • Avoid interactive commands (which wait for user input) in a silently deployed package: use silent installation switches (e.g., /qn, /S).

3. An installer or command freezes

An installer that displays a window, waits for confirmation, or loops indefinitely blocks the step until its timeout—and if no timeout is set, for a very long time.

Check/correct:

  • Enable and set the step’s Set timeout (in seconds) so that a frozen command eventually fails cleanly (and thus reaches END_ERROR) instead of remaining “in progress.”
  • Use the silent installation command line provided by the publisher.

4. The computer disconnected during installation

The status update is sent via the agent’s (XMPP) connection to the server, through a relay (ARS). If the workstation shuts down, goes into sleep mode, or loses network connectivity during deployment, the completion signal is not sent: the deployment remains “in progress” on the server side, and so does the Kiosk.

Check/correct:

  • Verify that the computer is still connected (agent present) and that its relay is functioning.
  • Once the computer is back online, restart the deployment (see Software Deployment).

5. Progress is reported, but completion is never indicated

A package can display its progress in the Kiosk via the Kiosk Progression action (Kiosk notification). If the sequence sends progress percentages but does not conclude with an END_SUCCESS exit, the progress bar remains “in progress” without ever changing to “installed.”

Check/correct:

  • The Kiosk notification is for informational purposes only: what actually changes the final status is the sequence reaching END_SUCCESS. Make sure the package actually ends with this exit.

What to do immediately

  1. Click the refresh button of the Kiosk 
  2. Open the Audit and locate the computer’s @Kiosk@ deployment.
  3. Check its status: Is it actually stuck on a step, pending, or in a silent error state? Open the details (“View deployment details”) to see the current step.
  4. If the deployment is frozen or stuck in a loop, stop it and then correct the package (timeouts, return code branches, END_SUCCESS/END_ERROR exit).
  5. Restart a clean installation, first as a standard deployment on a test computer, then from the Kiosk.

Simple rule: if a package does not complete properly in a standard deployment, it will not complete from the Kiosk either. First, ensure the sequence is reliable (timeouts + END_SUCCESS/END_ERROR exits that are always reachable); the Kiosk status will follow.