Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
We canβt find the reason; but, seams W10 drops the CmpEt1000Drv and reinstalls the std driver into our card.
I suppose W10 finds some conflict and goes for the std and known.
Apparently this happens when the EtherCAT network has problems with startup.
But if W10 changes the DRIVER ??? It's bad!!
How can we secure the DRIVER?
This happened, on July 7th. And it happened again yesterday.
Our network card is Intel i210 1 Gigabit
The driver for EtherCAT is Intel EtherExpressPro1000
https://us.store.codesys.com/media/n98_media_assets/files/2303000018-F/0/CODESYS%20EtherCAT%20Master%20SL_en.pdf
We canβt find the reason; but, seams W10 drops the CmpEt1000Drv and reinstalls the std driver into our card.
I suppose W10 finds some conflict and goes for the std and known.
Apparently this happens when the EtherCAT network has problems with startup.
But if W10 changes the DRIVER ??? It's bad!!
How can we secure the DRIVER?
Last edit: omar-escalante 2021-08-27
could you check if secureboot is enabled?