USBDriverInst V2.20 Programming Leads Blocked by Windows

[MPC]

Hi All,

      Has anyone got round the Windows security block on the legacy EASY800-CAB-USB driver. Now unable to connect to EASY-800 series units that we still maintain.

I assume that this affects old EASY400/500/800 & EC4P device programming leads.

Will Eaton update the USBDriverInst V2.20 founnd on https://applications.eaton.eu/sdlc/ ??

Many thanks in advanced.

Mark

[JansenDa]

Hi,
which Win Version are you exactly using?
BR
Daniel

[MPC]

I am used Windows 11.

I am hoping to find a solution within Window.

Reagrds Mark

[JansenDa]

Hi Mark,

sorry, i mean which Version of Win 11? Service Pack, Build. etc.

Daniel

[MPC]

Edition   Windows 11 Business
Version   25H2
Installed on   ‎22/‎03/‎2025
OS build   26200.9106
Experience   Windows Feature Experience Pack 1000.26100.334.0

Regards Mark

[DiRa]

Do you have local admin rights ?

see documentation page 3-4

What is exactly the content of "Windows security block" ?

[OlaKu63]

Hi Mark,
It would be helpful if you could post a screenshot of the blocked driver. Please open your Device Manager > Connections (COM & LPT) > EASY800-USB-CAB (COM3) > Characteristics > Common. If any other helpful information is on other tabs like Events or Driver please post these screenshots as well.
Thanks in advance!
Olaf

[MPC]

Here are a few screenshots as requested.

From device manager, Easy Comms prompt and, Window link pop up when inserting USB-CAB.

Many thanks Mark

[DiRa]

Hello Mark,

could you check the event ID on your Windows for the two mentioned numbers ?
You can verify whether the Windows driver policy is responsible by checking the Code Integrity event logs using the following two methods.

Manually querying Code Integrity events

Right-click the Start button and select Event Viewer.

In the left pane, navigate to: Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational
Search or filter the log for events with these IDs:
Event ID 3076 – A driver was audited (it would have been blocked but was allowed because the policy is in audit mode).
Event ID 3077 – A driver was blocked from loading because it violated the enforcement policy.
Look for the Policy ID field in the event details. Events caused by this feature reference one of the following policy GUIDs:

Audit policy: {784C4414-79F4-4C32-A6A5-F0FB42A51D0D}
Enforcement policy: {8F9CB695-5D48-48D6-A329-7202B44607E3}

Thanks
Ralf

[DiRa]

Hello Mark, I had send you a mail via forum mail function.

[MPC]

Many thanks for looking in to this Ralf.

Here are the event logs:
Regards Mark

[DiRa]

Hello Mark, could please contact me via form mail function ?