ETC Nomad Issues with Windows 10 Pro May 2020 Release

I'm currently having installation issues with Eos Console Software V2.9.1 on the latest Windows 10 pro software release.

I successfully and easily installed the Nomad software on a PC running Windows 10 version 10.0.1862.752

However, when installing on the new computer currently running the latest Windows 10 2020 update (19041.1) the "Blue Screen of Death" or Windows Stop appears and continually fails. The computer doesn't resume normal operation until ETC/EOS is removed.

From what I can tell, the only difference between the computers is the software. I'm hesitant to update the computer running the older software, and successfully running EOS to confirm this.

It appears what is causing the failure is installing the drivers.

The computer that works successful installed in the ETC folder 5 folders, the computer that isn't working just 2 (see below). The folders that are missing are the driver ones.

Can anyone help on this issue?

 

  • The driver for the ETCnomad dongle that we install which comes from Thales/Gemalto is the culprit driver during the installation. Previous versions (including those used in Eos version 2.9.1 and earlier) of their driver installation package causes a BSOD on Windows 10 on the latest 2004 version. We have already updated this driver version on our unreleased v3 of Eos and do not expect this to be an issue there.

    However, we can't change the past so 2.9.1 currently will have issues installing and will reliably cause a BSOD on Windows 10 v2004. There is a workaround where installing a more recent version of the dongle driver before attempting to install Eos 2.9.1 will not result in a BSOD. You can go here and get their latest driver version and install it before installing Eos 2.9.1:
    https://supportportal.thalesgroup.com/csm?sys_kb_id=61fb0ee1dbd2e78cfe0aff3dbf9619ab&id=kb_article_view&sysparm_rank=2&sysparm_tsqueryId=91488758dbf9d41091a9742339961910&sysparm_article=KB0018320

    We are also working on making this package available with our 2.9.1 installer with instructions to enact this workaround.

  • Thanks @BrianH.

    I was able to wind back the Windows 10 version to the one before.

    If I do update (or more likely Windows 10 forces me) to 2004, will I encounter the same issue, or is it just in installation?

  • I believe it should only be during installation. At least, I'm not aware of the presence of the driver causing a BSOD in v2004 at this time. From the testing I did I wasn't able to get Windows to upgrade to v2004 with the dongle driver from 2.9.1 installed. So hopefully Thales and Microsoft get this sorted.

Related