Skip to content
  • There are no suggestions because the search field is empty.

Resolving Webgility Desktop Update Issues Triggered by Error Messages

This article helps Webgility Desktop users resolve error messages that are caused by running an outdated version of the software. It explains how updating to the latest version can fix common issues and improve performance.

Overview

Error messages in Webgility Desktop may sometimes be caused by outdated software versions. Updating to the latest version can often resolve these issues.


Identifying the Issue

If an error message appears while using Webgility Desktop and functionality is affected, it's possible the issue is related to a version mismatch or a known bug fixed in a newer release.


Resolution Steps

1. Check Your Current Version

To verify your current version of Webgility Desktop:

  • Open Webgility Desktop

  • Click Help > About

  • Note the version number


2. Update Webgility Desktop

Before starting the update, make sure to back up your data (Database > Backup > OK)and close all open Webgility sessions.

Choose the appropriate update method:

  • If you can access Webgility Desktop without login issues:

    • Open Webgility Desktop

    • Go to Help > Check for Updates

    • Follow the prompts to install the update

  • If you're unable to log in due to the error:

    • Visit portal.webgility.com

    • Download the latest version of the Webgility Desktop installer

    • Run the installer as an administrator

    • Follow the on-screen instructions to complete the installation

    • Restart Webgility Desktop after the update


3. Confirm the Resolution

After updating:

  • Launch Webgility Desktop

  • Repeat the action that previously triggered the error

  • Confirm that the error no longer appears and that normal operations have resumed


Additional Tips

  • Keeping Webgility Desktop up to date helps prevent compatibility issues and ensures access to the latest features and bug fixes

  • Ensure your system meets software prerequisites such as Windows OS version, .NET framework, and admin permissions before updating.


Reference Links: click here