Skip to main content
Support Documentation

Upgrade Brightsign firmware

  • August 22, 2025
  • 6 replies
  • 1184 views

Prerequisites

 

Steps

How to upgrade BrightSign firmware via SD card:

  1. Power down your BrightSign player.
  2. Depending on the model of your BrightSign player, copy the appropriate .bsfw file (firmware file) onto the root directory of the SD card or USB stick. Ensure there are no other files with the .bsfw extension on it.
  3. Insert the SD card or USB stick into the player. Apply power.
  4. The player will automatically upgrade itself, remove the file from the SD card, and reboot into the new version.

 

How to Update via task:

  1. Host the firmware zip file on a publically available site, such as Google Drive. If you are using Google, share the file to Anyone with the link
    • Ensure that the *.bsfw file is in the root of the zip file. It will fail if it is nested in a folder. The name of the zip file is irrelevant.
  2. Copy the URL of the shared firmware file.
  3. Create an update BrightSign firmware task in device tasks on Appspace and enter the URL.
  4. Select save.

 

How to host .bsfw (using IIS):

  1. Open IIS (Run → inetmgr).
  2. Right-click default web site > and select explore.
  3. Create a new folder named BSFirwmare.
  4. Open the BSFirmware folder and paste the .bsfw file in this location. For this document, the file name is brightsign-xt4-8.5.47-update.bsfw.
  5. Go back to IIS. Right-click default web site and refresh. BSFirmware will appear.
  6. Select BSFirmware. The screen should look like the image below:

     

    BSfirmware.jpg?version=1&modificationDate=1721717860170&cacheVersion=1&api=v2&width=636&height=250

     

  7. Double-click MIME types.
  8. Under action (right-hand side column), select add.
  9. Add the following information:
    File name extension: .bsfw
    MIME type:

    application/octet-stream

    image-2024-7-23_15-7-11.png?version=1&modificationDate=1721718432047&cacheVersion=1&api=v2&width=647&height=250
  10. Select OK.
  11. To test, open a web browser and access http://servername/BSFirmware/filename.bsfw (e.g., http://myserver.domain.com/BSFirmware/brightsign-xt4-8.5.47-update.bsfw). A .bsfw file will be downloaded when accessing the URL.

 

The following has been provided by our user Lee below.

Note on Hosting Packages via Google Drive:

Once your package is built, it must be hosted for deployment. You’ve indicated that Google Drive will be used for this purpose. After uploading the package to Google Drive and setting the sharing permissions to “Anyone with the link”, you’ll need to modify the URL to enable automatic downloading.

How to Generate a Direct Download Link

  1. Copy the portion of the Google Drive file URL that appears between file/d/ and the following /.
  2. Append that value to the end of the following base URL:

https://drive.google.com/uc?export=download&id=

 

Example: 

Original URL:
https://drive.google.com/file/d/1UdxkyQcxtrUf_8hywarzHXfqREf-BfC5/view?usp=sharing

Direct download URL:
https://drive.google.com/uc?export=download&id=1UdxkyQcxtrUf_8hywarzHXfqREf-BfC5

 

Deployment in Appspace

Once the direct download URL is generated, you can assign the task to individual devices or groups by location, and schedule deployment accordingly.

6 replies

Lee
  • New Participant
  • October 1, 2025

Note on Hosting Packages via Google Drive

 

Once your package is built, it must be hosted for deployment. You’ve indicated that Google Drive will be used for this purpose. After uploading the package to Google Drive and setting the sharing permissions to “Anyone with the link”, you’ll need to modify the URL to enable automatic downloading.

How to Generate a Direct Download Link

  1. Copy the portion of the Google Drive file URL that appears between file/d/ and the following /.
  2. Append that value to the end of the following base URL:
https://drive.google.com/uc?export=download&id=

Example: 

Original URL:
https://drive.google.com/file/d/1UdxkyQcxtrUf_8hywarzHXfqREf-BfC5/view?usp=sharing

Direct download URL:
https://drive.google.com/uc?export=download&id=1UdxkyQcxtrUf_8hywarzHXfqREf-BfC5

Deployment in Appspace

Once the direct download URL is generated, you can assign the task to individual devices or groups by location, and schedule deployment accordingly.

 

 


  • Author
  • Support Documentation | Customer Care
  • October 8, 2025

Hello ​@Lee,

Thanks so much for participating in the sharing of knowledge across the Commonspace platform! This is a great note, and we’ve included it in the article above.

We greatly appreciate you engaging with us and helping our fellow Appspacers. This is what helps make Appspace better!

Best,
Lauren | Customer Care


Hi. I’m trying to get this to work, but the task does not seem to initiate the update on the device. It seems that google wants to scan for virus before you get it to download? 

Should it work with using the links directly from Brightsign?
https://firmware.bsn.cloud/cobra-9.1.92.1-update.bsfw

https://firmware.bsn.cloud/malibu-8.5.64-update.bsfw

Or does it have to be put in a .zip container first? 

 

Does anyone know, if the 9.1.92.1 update file can be pushed to device not capable of running this version? Will they skip the update? In my deployment its a mix of Brightsign Malibu and Cobra players, hence some devices are limited to 8.5.64, and its not easy to differentiate between the compatible models in Appspace. 

And what does this mean from the upgrade.brs file

message: "Please use the new Software Updates features in the Devices extension to manage BrightSign app updates. The Device Task has been blocked to avoid conflicts",


  • Employee
  • January 28, 2026

Hi Markus,

 

You can use the link from BrightSign as long as the player able to download it directly from the link.

 

To answer your question related to the update frimware, BrightSign players do not have a built-in filter to 'skip' incompatible firmware pushed via Appspace. If a Cobra (Series 4) player receives a Malibu (Series 5) firmware file, the update will fail. While BrightSign has safety checks, pushing the wrong file can cause the device to hang or require a manual SD card factory reset.

 

Hope this answer your questions.


  • New Participant
  • February 12, 2026

Is anyone else having issues with installing 9.1.92.1 using a task? Each series 5 player I’ve tried it with errors out with the below in the logs:
[ 751.204] BrightScript creation of roBrightPackage failed:

[ 751.204] ZipArchive error at line 91

[ 751.204]

[ 751.205] Script runtime error: 'Dot' Operator attempted with invalid BrightScript Component or interface reference. (runtime error &hec) in .../appspace/scripts/upgrade.brs(234)

[ 751.205]

[ 751.205] Press SVC to debug.

 

Then it reboots before I can hit the SVC button


Is anyone else having issues with installing 9.1.92.1 using a task? Each series 5 player I’ve tried it with errors out with the below in the logs:
[ 751.204] BrightScript creation of roBrightPackage failed:

[ 751.204] ZipArchive error at line 91

[ 751.204]

[ 751.205] Script runtime error: 'Dot' Operator attempted with invalid BrightScript Component or interface reference. (runtime error &hec) in .../appspace/scripts/upgrade.brs(234)

[ 751.205]

[ 751.205] Press SVC to debug.

 

Then it reboots before I can hit the SVC button



Howdy there Sam,

My names Jeter and I’m a Strategic Account Manager here at Appspace. The Firmware Update Device Task needs the full .zip URL. I was able to recreate your issue using the Device Task and submitting just the .bsfw URL. Once I applied the full zipped URL, this allowed the device to update the firmware successfully. 

Repo: https://docs.brightsign.biz/releases/brightsignos-releases 

​​​​​​Please also note, Firmware revisions newer than 9.1.75 and 9.0.218 contain the EU RED vulnerability patch. Once a device is update to a firmware version newer than those, it should not be downgraded.  https://docs.brightsign.biz/advanced/dws-local-access