Firmware Update Guide for RX300, RX-RDP+, RX420 (RDP), RX440 (RDP), RX540, RX580, LEAF OS & EX500W Devices

Firmware Update Guide for RX300, RX-RDP+, RX420 (RDP), RX440 (RDP), RX540, RX580, LEAF OS & EX500W Devices

Introduction

This article walks administrators through updating firmware on NComputing RDP and LEAF OS endpoint devices:
RX-RDP+, RX420(RDP), RX440(RDP), RX540, RX580, LEAF OS (EX500W, EX600W, LEAF OS GO, x86-64 PCs/Laptops)
All supported devices share a common firmware-menu interface, but they belong to distinct firmware families with separate images, licensing models, and versioning tracks.
Identify your device family in the section below before proceeding.

Before You Begin

1. Device Families and Firmware Compatibility

NComputing devices fall into three firmware families. Do not cross-flash between families — applying the wrong firmware image will fail or brick the device.

Firmware Family Overview

DeviceFirmware Family
RX-RDP+RX-RDP+ Series
RX420(RDP)RX-RDP+ Series
RX440(RDP)RX-RDP+ Series
LEAFOS(PI4)*RX-RDP+ Series
RX540RX540/RX580
RX580RX540/RX580
EX500W, EX600WLEAF OS x86-64
LEAF OS GO (USB pendrive)LEAF OS x86-64
LEAF OS on x86-64 PCs/LaptopsLEAF OS x86-64

Notes
LEAFOS(PI4) is a special variant for RX420/RX440(HDX) customers migrating to the RDP platform. It uses the RX-RDP+ Series image and is not the same as the x86-64 LEAF OS software endpoint.

2. Licensing Requirements

A valid Device AMP license is required to apply firmware updates on all supported devices, whether updating manually or via PMC. Updates are silently blocked when the license is expired.

RX-RDP+, RX-420(RDP), RX-440(RDP) Series and RX540/RX580

  • Ships with 1 year of complimentary Device AMP.
  • After year 1, Device AMP must be renewed to continue receiving firmware updates.
  • Renewal SKUs: NC-AMP-RXRDP-1A through NC-AMP-RXRDP-5A.

LEAF OS x86-64

LEAF OS uses its own activation license. Device AMP is bundled differently depending on the license type:

SKULicense TypeDevice AMP Included
LEAFOS–PPerpetualYear 1 only — must renew after
LEAFOS–1A1-year subscriptionFull term
LEAFOS–3A3-year subscriptionFull term
LEAFOS–5A5-year subscriptionFull term

Info
EX500 (SKU: 700-0037) and EX500W (SKU: 700-0048) ship with an activated perpetual LEAF OS license pre-installed. Requires Device AMP after the 1 year complimentary period expires in order to update firmware.  
Info
For help checking or renewing Device AMP, refer to:  How to Use the Device AMP License Expiration Calculator


3. PCU File Requirement (for PMC Users)

Alert
Important! PMC cannot manage newly updated devices until the matching PCU file has been uploaded. This is the #1 overlooked step after a firmware update

Each major firmware version introduces new configuration parameters. The PCU (PMC Configuration Update) file tells PMC how to manage those parameters. Without it, PMC will not apply profiles or push settings, even if the firmware installed successfully.

  • The PCU file is included in the firmware download ZIP package.
  • It must be uploaded to PMC before or immediately after updating devices.

How to upload the PCU file:

  1. Extract the .pcu file from the firmware ZIP package.
  2. Log in to PMC Endpoint Manager.
  3. Go to Administration → Device Configurations.
  4. Under "Update Supported Device Configurations," click Browse, select the .pcu file, and click Upload file.

4. Pre-Update Checklist

Before starting any firmware update, confirm the following:
  1. Device AMP license is active and not expired
  2. Correct firmware image downloaded for your device family (see table above)
  3. PCU file available (if managing via PMC)
  4. Device configuration has been backed up
  5. Stable network connection available (for FTP/PMC methods)
  6. PMC version is 4.2 or higher (if using PMC push)

Current Firmware Versions (as of July, 2026)

Device Group

Latest Official Version

RX-RDP+, RX420(RDP), RX440(RDP), LEAFOS(PI4)

7.5.3

RX540, RX580

7.5.3

LEAF OS x86-64 (EX500W, EX600W, LEAF OS GO, PCs/Laptops)

7.5.3


Info
Download firmware from the official page: https://www.ncomputing.com/support/software-downloads

Firmware Update Methods

All device groups share the same firmware menu interface. Choose one method below.

Estimated Update Times

Method

Typical Duration

Method A — FTP / HTTP(S) URL

3–5 minutes

Method B — USB Stick

2–4 minutes

Method C — PMC Remote Push

Varies by deployment size

Method D — vSpace Server Push

Varies

Alert
Note: Do not interrupt the update! On RX-RDP+ series devices, a pause around 76% is normal. Do not power off the device. The update will resume and the device will reboot automatically.

Method A — FTP / HTTP(S) URL (Manual via Device GUI)

Applies to: All device groups

  1. Access the device's local Setup GUI.
  2. Navigate to Support → Firmware Update → FTP/HTTP Update.
  3. Enter the firmware URL from the NComputing Software Downloads page. NComputing's FTP is open — no credentials required.
  4. Click Update. The device downloads, installs, and reboots automatically.
Idea
Network tip: If the device cannot reach NComputing's FTP server due to firewall or content filtering, use a local FTP server instead (see Troubleshooting). 

Method B — USB Stick (Manual via Device GUI)

Applies to: All device groups

  1. Download the correct .upd file for your device family (see the compatibility table above).
  2. Copy the .upd file to the root folder of a USB stick formatted as FAT32, NTFS, ext3, or ext4.
    • Recommended: **8 GB**. Maximum: **32 GB**. Larger drives may not be detected.
  1. Insert the USB stick into the device.
  2. Navigate to Support → Firmware Update → USB. Refresh if needed.
  3. Select the firmware file and click Update. The device reboots upon completion.
Alert
Edge case concerning RX420(RDP) on older firmware 3.x. Manual, FTP and USB updates are disabled once the complimentary AMP year expires. PMC (Method C) is the only available update path in this scenario.

Method C — Remote Push via PMC Endpoint Manager

Applies to: All device groups
Prerequisites:
  1. PMC version 4.2 or higher
  2. Device AMP license active on all target devices
  3. PCU file uploaded to PMC for the target firmware version (see the section "Before You Begin" in this document)
Steps:
  1. Log in to PMC Endpoint Manager.
  2. Go to Administration → Files and upload the firmware .upd file.
  3. Navigate to Firmware Updates and select the uploaded image.
  4. Select the target device group(s).
  5. Schedule the update or click "Update Now".
  6. Monitor progress in Audit Events.
  7. Devices reboot automatically upon completion.
Notes
Postponed updates: If a user postpones a PMC-pushed update, it will trigger automatically when they sign off from their VDI session or local apps.
Notes
Using a local FTP source: In the Schedule Firmware Update dialog, select "Let the devices use the configured firmware update source and method" to have devices pull from a locally configured FTP server instead of the PMC-uploaded image.

Method D — vSpace Server Push (Applicable to vSpace connected Thin-Clients)

Firmware updates can also be pushed from vSpace Pro Enterprise Console for devices connected to a vSpace environment. PMC is the recommended path for modern deployments mentioned in this article.

Troubleshooting

PMC Cannot Manage Devices After Firmware Update

Cause: The PCU file was not uploaded to PMC after updating to a new firmware version.
Solution: Upload the PCU file from the firmware ZIP package via Administration → Device Configurations → Update Supported Device Configurations. See the PCU section under Before You Begin for detailed steps.

Firmware Update Fails — "Corrupted Archive" Error

Cause: A firewall or proxy is corrupting the firmware file in transit during download.
Solution: Redirect devices to a local FTP server:
  1. In PMC → Devices tab → select the affected group → Update Firmware → select "Let the devices use the configured firmware update source and method."
  2. In the device Profile → Support → Firmware Update: set Method to FTP/HTTP URL and enter your local FTP server address (e.g., ftp://<server_ip>/firmware.upd).

RX420(RDP) on Firmware 3.x — Cannot Update via USB or FTP

Cause: On 3.x firmware, USB updates are disabled after AMP expiry.
Solution: Use PMC (Method C). 

LEAF OS / EX500 Cannot Reach NComputing FTP (Strict Network)

Cause: Outbound traffic restrictions block access to the NComputing FTP server or Management Portal.
Solution: Either:
  1. Whitelist 104.218.10.224 (NComputing FTP) and the NComputing Management Portal in your firewall, or
  2. Deploy a local PMC instance on-premises to manage updates within the secure network.

FAQ

Can I skip firmware versions?

Yes. You can update directly to the latest official version from any prior version, unless otherwise noted in the release notes or the Software Downloads site. Always check the release notes for any intermediate step requirements.

Can I downgrade firmware?

Firmware downgrades are generally not supported and not recommended. If you need to roll back, contact NComputing Support.

Does updating firmware erase my configuration?

No. A standard firmware update preserves device configuration. Always back up your configuration before updating as a precaution.

Can I update multiple devices simultaneously?

Yes, via PMC (Method C). Select a device group and push to all devices at once. Individual FTP and USB methods update one device at a time.

Does firmware update require a reboot?

Yes. All update methods trigger an automatic reboot upon completion.

What happens if power is lost during an update?

Be sure to make all preparations to prevent that from happening. Any interruption on the firmware process and the device could become bricked. Contact support for steps on restoring your device. Notice that warranty does not cover power failure or firmware interruptions. 

Does updating firmware require an active Device AMP license?

Yes it does. Visit the section Before You Begin → 2. Licensing Requirements above this article. 
 

Best Practices

  1. Back up device configuration before every firmware update.
  2. Never power off or unplug during an update — especially during the 76% pause on RX-RDP+ series.
  3. Upload the PCU file to PMC before pushing updates to devices.
  4. Verify Device AMP status before initiating any update.
  5. Use official firmware only. Download from https://www.ncomputing.com/support/software-downloads
  6. Special note for LEAF OS on 8 GB storage devices: A separate upgrade procedure is required. See: How to update LEAF OS on devices with 8 GB internal storage.


Article ID: KB‑874
Last Updated: July, 2026



    • Related Articles

    • Where can I purchase Device AMP licenses for RX, LEAF OS, and EX devices?

      Each RX-RDP+, RX420(RDP), RX440(RDP), RX540, RX580, LEAF OS, and EX500W device includes a perpetual license for PMC software, along with first-year of complimentary software maintenance (Device AMP for RX, LEAF OS and EX devices) for any firmware ...

    • [Release Notes] PMC Endpoint Manager

      NComputing PMC Endpoint Manager Version 4.2.1 Release Notes PRODUCT RELEASE NOTES: NCOMPUTING PMC ENDPOINT MANAGER, VERSIONS 4.2.1 Product: NComputing PMC Endpoint Manager Version: 4.2.1 Supported virtualization environments: VMware ESXi 6.7.0, ...

    • PMC Version 4, Start Guide

      Overview This document based on the release notes of PMC 4.1.1. It covers everything you need to know, in-depth, regarding installation and deployment of PMC. It is always recommended that you use the current release notes of every PMC version that ...

    • Understanding AMP Licensing: vSpace AMP vs. Device AMP

      Introduction The Annual Maintenance Program (AMP) from NComputing is a family of support and software maintenance plans designed to enhance the value of your NComputing environment. However, it's important to understand that there are two distinct ...

    • NComputing LEAF OS software endpoint overview

      NComputing LEAF OS is a next-generation software endpoint solution that transforms any x86-64 PC or laptop into a secure and centrally managed endpoint. Designed and optimized for Amazon WorkSpaces, Citrix, Dizzion Frame, Microsoft (RDS, AVD, Windows ...