[Mark P Promethean]

ActivBoard 100, 300 AB500 Firmware now released

As part of Promethean’s commitment to our existing customers using our legacy ActivBoard products, we have been extensively investigating a number of solutions for this issue.

A major part of this investigation centered around driver certification for these legacy products on Windows 10.

“Blue Screen” occurs with Promethean AC1, AC2, or ActivHub on Windows build 1903 and above

These products were first introduced over a decade ago.

We have found that in some instances the use of a these products when connected to a computer running Windows 10 1903 and above can cause a “Blue screen” crash.

As part of Promethean’s commitment to our existing customers using our legacy products, we have been extensively investigating potential solutions to this issue. A major part of this investigation centred around driver certification for this legacy product on Windows 10 build 1903 and above.

Two certificates have a major impact on the operation of the products:

• A code signing certificate lets users know that the software comes from a ‘trusted source’. Our installers, including ActivInspire & ActivDriver, are signed with a code signing certificate.  Our certificate that provides this did recently expire, and was renewed.
• A hardware device driver certificate is provided by Microsoft and is embedded into third party kernel mode device drivers, and allows the driver to be run without any of the driver certification protection being turned off.
  Windows 10 1903 has introduced a different way of communicating with the kernel mode device drivers which form the core of our ActivDriver is when it is being used with all of our legacy ActivBoards and ActivHubs. The technology limitations of the ActivHub combined with the new certification, makes it impossible to achieve device driver certification.

Despite our best endeavours, this change introduced in Windows 10 build 1903 means Promethean can no longer offer support for drivers or software for our AC1, AC2 or ActivHubs when used with Windows 10 build 1903 and above.

What alternative does Promethean offer?

To try to help our long time users of these legacy products, we have produced a modified ActivDriver that appears to avoid the blue screen problem when used with our legacy ActivHub. However this driver is not supported by Promethean. Promethean has not put this modified driver through normal formal testing and quality assurance procedures. Therefore installation and use of this ActivDriver is entirely at your own risk. We cannot guarantee that the download and installation of this unsupported driver will fix the problem and we also cannot guarantee that the installation and download of this driver will not have other unintended consequences. As such, we recommend that you test this unsupported driver in your local environment before making a decision to roll it out broadly.

IMPORTANT:  If you wish to access this unsupported ActivDriver please use the details below.

The link to the unsupported ActivDriver is here:

64 bit
32 bit

 

The use of this unsupported ActivDriver may require you to perform one of the additional options detailed below in order to get a successful connection to your ActivBoards after the installation.

Option 1: Disable  ‘Secure Boot’ in your computer BIOS if it is supported by your computer/ operating system.

Option 2: Disable driver signature enforcement within Windows 10.

·        Click the Start menu and select Settings.

·        Click Update and Security.

·        Click on Recovery.

·        Click Restart now under Advanced Startup.

·        Click Troubleshoot.

·        Click Advanced options.

·        Click Startup Settings.

·        Click on Restart.

·        On the Startup Settings screen press 7 or F7 to disable driver signature enforcement.

 

Users of 100 series, 300 series and 500 series ActivBoards

A new version of ActivBoard firmware is now available for these ActivBoards that fixes the problem. Details on how to update your ActivBoard to this firmware are contained within the following support article:

https://support.prometheanworld.com/article/1779/

[stephenlawJSRHS]

Our computers are set to Secure Boot with BitLocker encryption enabled due to our new data privacy/security law.  Started the process on one laptop but we hit with entering the BitLocker key. Has this process been tested with such a system.

REALLY could use a signed driver and any new firmware for the boards sooner instead of later. Have three more users reporting the problem.

[Mark P Promethean]

Hi stephenlawJSRHS,

As described above, Promethean cannot release a signed hardware driver that will resolve this problem.

We are only going to be offering a firmware update for AB100, AB300 and AB500 users.

This is due to the technology limitations in the 1st and 2nd generations ActivBoards, meaning we cannot develop a new firmware for these boards.

Thanks

[henriksen]

“Users of AB100, 300/ AB500 will be getting access to a firmware update which will resolve the problem.” Any update when this will be released? Hopefully sooner than the end of October?

[Adam K Promethean]

Hi Henriksen,

We hope to have further information on this soon.

Once we have this, we will be sure to let the community know.

Kind regards,
Adam

Promethean Support

[Steve W]

As it’s been a few weeks, do you have any updates on this firmware?

[Mark P Promethean]

Hi Steven

The firmware is is still undergoing verification prior to release.

We are still currently targeting this firmware being released for 100 series, 300 series and AB500 ActivBoards before the month is up.

Thanks

[Amy Goebel]

Are you working on this for MacOS as well?

[Mark P Promethean]

Hi Amy…this thread and updates are only applicable for Windows 10 1903 users and an issue that Microsoft changes have introduced.
If you have specific issues with macOS please contact our support team with full details.

 

[Amy Goebel]

I have but I haven’t heard a response.

[Javier Alonsoperez]

Hi my name is Javier, we need to know if at today did you have a solution for these case.

I have an ActiveBoard AB100 first generation.

ABV364E100

I try to implement this solution  in my Acer Aspire E15-576-81GD

Bios Release 1.49

Windows 10 release 1903

I can’t back the soft of windows to the previous release.

Thanks in advance.

 

 

[Adam K Promethean]

Hi Javier,

The part code you have provided is not part of the 1st Generation ActivBoard range though is part of the 100 series range.

If you are experiencing the same issues as outlined in this thread, we are still currently targeting this firmware being released for 100 series, 300 series and AB500 ActivBoards before the month is up to help with this issue.

Thanks,
Adam
Promethean Support

[Javier Alonsoperez]

if I can found a computer with windows 7, it’s could works? I mean if I can block the update of windows 10 in order to works as never the update of windows 10 took place?

what is the limitation of the total system in this case?

we have to work in the meantime,

best regards

 

 

[Adam K Promethean]

Hi Javier,

This issue only affects the ActivBoards when using Windows 10 build 1903.

So if you have a Windows 7 operating system, you would not get the same errors that happen.

Thanks,
Adam

Promethean Support

 

[Adam Veatch]

Today’s the day. Any updates coming our way? We’ve already prepared our Gen1 and Gen2 users that the end is nigh, but we’re getting increasingly nervous about virtually everything else purchased 2008 to 2017 having to be replaced in the next 18 months.

[Adam K Promethean]

Hi Adam Veatch,

Thanks for your patience whilst our teams have investigated this issue.

You can now see the below post which refers to the update:

https://community.prometheanworld.com/forums/topic/update-activboard-100-300-ab500-firmware-now-released/

Thanks

Adam

Promethean Support

 

[Author]

Posts