Windows driver communication problems

Dear Forum-Community,

Due to major security leaks in Intel and AMD processors, Microsoft and other software / hardware vendors released security updates at the beginning of the year 2018. An issue in these updates leads to problems with zenon. The effect is a known issue in several Windows updates.

After applying one or several of these updates, various communication issues may occur. After a detailed analysis, we can verify that the issues recognized are based on the January 3rd security updates for various Microsoft Windows versions.

COPA-DATA has generated a ticket at Microsoft Tech Support in order to coordinate activities and is urging on the case with high priority. Microsoft is working on a resolution and we are waiting for the Windows updates that will fix these issues. Any new information will be communicated as soon as possible.

Download the full Tech Announcement from our COPA-DATA Homepage and don't hesitate to get in touch for further information.

Thank you very much!


Your COPA-DATA Team.

Dear COPA-DATA Team,

have you received feedback on your ticket to Microsoft?
Or can you give us any indication that might help us to identify these driver problems?

We have driver stability issues with current versions of Windows Server 2016.
Problems that do not occur with Windows 10 LTS Versions from 2016.
We are using Zenon 8.0 Build 60603.

Quote:

---

Originally Posted by MarkusL

Dear COPA-DATA Team,<br>
<br>
have you received feedback on your ticket to Microsoft? <br>
Or can you give us any indication that might help us to identify these driver problems?<br>
<br>
We have driver stability issues with current versions of Windows Server 2016.<br>
Problems that do not occur with Windows 10 LTS Versions from 2016.<br>
We are using Zenon 8.0 Build 60603.

---

<br>
<br>
Hi Markus,<br><br>the Problem was fixed in several zenon versions, including zenon 8.00. The fix is included in build <strong>44055</strong>. As you're using build 60603, the fix is included in your current version.<br>I would suggest that you reach out to your local support department to let them have a closer look at the behavior.<br>The issue might come from somewhere else.<br><br>Best regards,<br>Xandi