Updater service: when it isn't updating
Purpose: Fix the most common reasons the workstation's auto-updater (the VitaPay Updater) doesn't apply a new version.
When to use this: A workstation is stuck on an old version, or a new build hasn't rolled out to it.
The VitaPay Updater runs alongside the payment service and applies updates on its own. When it isn't updating, it's almost always one of the two reasons below.
1. The update window hasn't been reached
The updater only applies updates during a set time window, usually 4:00 AM to 6:00 AM local workstation time. Outside that window it leaves the workstation alone, by design, so an update never interrupts service.
What this means in practice:
- If the workstation was off, asleep, or offline during the window, it won't have updated. Leave it powered on and online overnight, then check again after the next window.
- The window is set at the merchant level and can be adjusted. To change it for a site, contact a Vitabyte admin. It isn't something you change on the workstation itself.
2. A failure marker is blocking updates
After an update fails, the updater writes a failure marker and then refuses to try again until that marker is cleared. This stops a single bad update from looping. If a workstation stopped updating right after a failed update, this is usually why.
Fix:
-
On the workstation, open the Vita program folder. The failure marker lives at:
C:\Program Files (x86)\Vita\failureYour base Vita folder may differ by install, but the failure marker sits under it.
-
Delete the failure marker.
-
Restart the VitaPay Updater service: open the Services console (
services.msc), right-click the VitaPay Updater entry, and choose Restart. Or simply wait for the next update window.
Only clear the failure marker when you intend to let the update run again. If the underlying update keeps failing, the marker will come back. Capture the workstation's logs with Upload Logs Now and escalate, rather than deleting it over and over.
Verify
- After the next update window (or a service restart), the failure marker doesn't reappear and the workstation moves onto the current build.
- If you're unsure which version a site should be on, confirm with a Vitabyte admin.
