With FNP-11.17, the HASP RTE has been upgraded to v 7.101 (to be upgraded further in v11.17.1 release). Any end user availing the HASP RTE of v7.100 or lower will face this issue. We have confirmed with Thales Support that issue mentioned on MS website is same as the one on Thales one. Although from the above URL, Thales has provided the resolution against these observations, which could be tried in the meanwhile to mitigate BSOD/installation issues. Since Microsoft has acknowledged to be working on this, hence we can only wait for this to be fixed in future Windows 10 releases. "Windows 10 Build 1909 is the latest OS version that FNP supports (as Build 2004 was only made available by end of May 2020) and currently we are not aware of any workaround against the reported issue by MS". Official Support Statement for Build 2004: (valid as of date July 17th, 2020) Issues updating or starting up devices when aksfridge.sys or aksdf.sys is present:
So an upgrade (FNP toolkit + driver) would be immediate solution. A s per the link provided by Gemalto, they have mentioned issue will be seen in version 7.100 and earlier. In FNO 11.17 toolkit, we have already upgraded this to v7.101 and in R3 release (11.17.1) it will be on v7.103. Please also be advised that this issue is only reported where Sentinel LDK Run-time Environment version 7.100 or earlier is already installed or will be installed. When Sentinel Run-time Environment is not installed: After upgrading Windows 10 to version 2004, installing Sentinel LDK Run-time version 7.100 or earlier may cause a stop error. Upgrading the operating system to Windows 10 version 2004 may fail (that is, the installation of Windows may fail, causing the installation to roll back). When Sentinel LDK Run-time Environment version 7.100 or earlier is installed: We have noticed issues with HASP configuration files reported by Thales as well as Windows.
0 kommentar(er)
