Community
cancel
Showing results for 
Search instead for 
Did you mean: 
BGhos2
Beginner
4,264 Views

v24.5 Drivers for Intel I211 on Windows 10 64-bit not working

I get this error after updating the drivers:

 

"Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

 

Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked."

 

The interface disappears from available adapters and I lose connectivity, rolling back to v24.3 works, please help. thank you.

0 Kudos
31 Replies
ZM1
Beginner
2,659 Views

I am also experiencing this with a fresh copy of Win 10 1909. My 219-V works fine, it's only the 211 getting the code 39 problem. To temporarily bypass it, I disabled device driver signing, but that's obviously not a permanent solution.

BvonB
Beginner
2,659 Views

I'm getting the same error and have done the same roll back.

 

Windows 10 Pro 64-bit

Version 1909 (OS Build 18363.592)

Have installed all available updates from Windows Update in the default/retail ring, not participating in Windows Insider

 

`sigverif.exe` output with Intel® Network Adapter Driver for Windows® 10 version 24.3:

Scan Results: Total Files: 263, Signed: 263, Unsigned: 0, Not Scanned: 0 File Modified Version Status Catalog Signed By ------------------ ------------ ----------- ------------ ----------- ------------------- [c:\windows\system32] e1r68x64.din 5/20/2019 None Signed e1r68x64.cat Microsoft Windows Hardware Compatibility Publisher e1rmsg.dll 9/26/2019 10.0.866.0 Signed e1r68x64.cat Microsoft Windows Hardware Compatibility Publisher [c:\windows\system32\drivers] e1r68x64.sys 9/26/2019 12.18.9.1 Signed e1r68x64.cat Microsoft Windows Hardware Compatibility Publisher

 

`sigverif.exe` output with Intel® Network Adapter Driver for Windows® 10 version 24.5:

Scan Results: Total Files: 263, Signed: 263, Unsigned: 0, Not Scanned: 0 File Modified Version Status Catalog Signed By ------------------ ------------ ----------- ------------ ----------- ------------------- [c:\windows\system32] e1r68x64.din 5/20/2019 None Signed e1r68x64.cat Microsoft Windows Hardware Compatibility Publisher e1rmsg.dll 12/3/2019 10.0.907.0 Signed e1r68x64.cat Microsoft Windows Hardware Compatibility Publisher [c:\windows\system32\drivers] e1r68x64.sys 12/3/2019 12.18.9.6 Signed e1r68x64.cat Microsoft Windows Hardware Compatibility Publisher

12.18.9.1 C:\Windows\system32\DRIVERS\e1r68x64.sys

Issued by: Intel External Issuing CA 7B Issued to: Intel(R) INTELND1820 Revocation Status : OK Serial number: 560000077b478c76c9afcafcaf00000000077b Signing time: ‎Thursday, ‎May ‎23, ‎2019 9:02:55 PM Valid from: 8/9/2018 to 8/8/2020   Issued by: Microsoft Windows Third Party Component CA 2012 Issued to: Microsoft Windows Hardware Compatibility Publisher Revocation Status: OK Serial number: 33000000857f83dc2a6ca979b8000000000085 Signing time: ‎Monday, ‎August ‎5, ‎2019 11:00:22 AM Valid from: 6/5/2019 to 6/3/2020

 

12.18.9.6 C:\Windows\system32\DRIVERS\e1r68x64.sys

Issued by: Intel External Issuing CA 7B Issued to: Intel(R) INTELND1820 Revocation Status: OK Serial number: 560000077b478c76c9afcafcaf00000000077b Signing time: ‎Monday, ‎November ‎25, ‎2019 8:22:00 AM Valid from: 8/9/2018 to 8/8/2020   Issued by: Microsoft Windows PCA 2010 Issued to: Microsoft Windows Hardware Compatibility Publisher Revocation Status: OK Serial number: 330000061929b7720a7076e4b4000000000619 Signing time: ‎Monday, ‎December ‎2, ‎2019 5:53:44 PM Valid from: 2/20/2019 to 7/31/2020

 

10.0.866.0 C:\Windows\system32\e1rmsg.dll

Issued by: Intel External Issuing CA 7B Issued to: Intel(R) INTELND1820 Revocation Status : OK Serial number: 560000077b478c76c9afcafcaf00000000077b Signing time: ‎Wednesday, ‎February ‎27, ‎2019 2:43:39 AM Valid from: 8/9/2018 to 8/8/2020   Issued by: Microsoft Windows Third Party Component CA 2012 Issued to: Microsoft Windows Hardware Compatibility Publisher Revocation Status : OK Serial number: 33000000857f83dc2a6ca979b8000000000085 Signing time: ‎Monday, ‎August ‎5, ‎2019 11:00:23 AM Valid from: 6/5/2019 to 6/3/2020

 

10.0.907.0 C:\Windows\system32\e1rmsg.dll

Issued by: Intel External Issuing CA 7B Issued to: Intel(R) INTELND1820 Revocation Status: OK Serial number: 560000077b478c76c9afcafcaf00000000077b Signing time: ‎Wednesday, ‎August ‎28, ‎2019 2:51:55 AM Valid from: 8/9/2018 to 8/8/2020   Issued by: Microsoft Windows PCA 2010 Issued to: Microsoft Windows Hardware Compatibility Publisher Revocation Status: OK Serial number: 330000061929b7720a7076e4b4000000000619 Signing time: ‎Monday, ‎December ‎2, ‎2019 5:53:45 PM Valid from: 2/20/2019 to 7/31/2020

 

Both signatures from both files from both driver packages claim "This digital signature is OK."

 

I don't know where the supposed revoked signing certificate is coming from, but it seems more likely to be a problem on Microsoft's side than Intel's since both driver packages' files were signed with the same Intel certificate but different Microsoft ones.

CrisselleF_C_Intel
Moderator
2,659 Views

 

Hello BGhos2,

 

Thank you for posting in Intel Ethernet Communities. 

 

Please provide the exact OS build version you are using as well. This will help us to further check the issue.

 

Looking forward to your response.

 

Hello ZM1 & BvonB,

 

Thank you for sharing additional information regarding this issue. We will closely monitor the thread and check on this issue.

 

Best regards,

Crisselle C

Intel® Customer Support

A Contingent Worker at Intel

BGhos2
Beginner
2,659 Views

Windows 10 Pro 64-bit Version 1909 (OS Build 18363.592)

CrisselleF_C_Intel
Moderator
2,659 Views

Hello BGhos2,

 

Thank you for the prompt reply.

 

While we are checking on this, we would also like to request for the System Support Utility (SSU) log of your system as well as from ZM1 & BvonB systems. This will allow us to check the system details and configuration. Kindly refer to the steps below.

a- Go to https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-?product=91... and download the software.

b- Open SSU.exe

c- Mark the box "Everything" and then click "Scan".

d- When finished scanning, click "Next".

e- Click on "Save" and attach the file to a post.

 

We look forward to your reply.

 

Best regards,

Crisselle C

Intel® Customer Support

A Contingent Worker at Intel

BGhos2
Beginner
2,659 Views

posted a file.
ZKłos
New Contributor I
2,659 Views

Same here. After upgrading to 24.5 drivers, I211 adapter no longer working (disabled) because of Error 39 / 'driver signing certificate has expired'. I219-V working fine.

 

Windows 10 x64 1909

 

I rolled back to 24.3 drivers and all is fine again.

CrisselleF_C_Intel
Moderator
2,659 Views

Hello BGhos2,

 

Thank you for providing the requested information. We will check on it and give you an update as soon as there is any findings but not later that 3 business days.

 

Hoping for your patience.

 

Hello ZKłos,

 

Thank you for reporting this issue to as well. Will you be also able to provide the SSU logs of your system? This would help us check the system details and compare it to other logs.

 

Looking forward to your reply.

 

Best regards,

Crisselle C

Intel® Customer Support

A Contingent Worker at Intel

ZKłos
New Contributor I
2,659 Views

Will SSU logs collected with 24.3 drivers be of any use to you ? I had to restore proper operation of the NICs and rolled back to 24.3 drivers instantly (all is working fine then).

ZM1
Beginner
2,659 Views

+1. I can provide SSU's of 24.3 and 24.5 if necessary, but if one from 24.3 would be sufficient that'd be great since I rolled back to 24.3.

ChrisM34
Beginner
2,659 Views

I have the same issue when I try to install the NDIS68 drivers from 2.45 (and 2.44) for my Intel(R) I211 Gigabit Network Adapter. I updated to this driver without any issue the other day, but today after reinstalling Windows 10, windows refused to activate the driver because of a problem with the certificate used to sign the file.

Previously, I updated this driver from a previous version fine on Windows 10 1909, and it didn't cause any error after upgrading to Windows 10 2004. Now that I did a clean install of Windows 2004, the driver doesn't activate with Windows complaining about an issue with the signing certificate. It also returns the same error on a clean install of Windows 10 1909.

 

 

There's also this message in the "Security" log of Windows log which is unrelated with any signing certificate error. The error shows up when I install brand new files (2.4.5 and 2.4.4 zip file) from your site.

 

Installing the drivers from the NDIS65 folder or NDIS68 drivers from the 2.4.3 drivers package doesn't cause any issue.

Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 1/22/2020 11:23:58 PM Event ID: 5038 Task Category: System Integrity Level: Information Keywords: Audit Failure User: N/A Computer: Chris-W10-PC Description: Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.   File Name: \Device\HarddiskVolume6\Windows\System32\drivers\e1r68x64.sys Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" /><EventID>5038</EventID><Version>0</Version><Level>0</Level><Task>12290</Task><Opcode>0</Opcode><Keywords>0x8010000000000000</Keywords><TimeCreated SystemTime="2020-01-22T22:23:58.2804185Z" /><EventRecordID>6565</EventRecordID><Correlation /><Execution ProcessID="4" ThreadID="6100" /><Channel>Security</Channel><Computer>Chris-W10-PC</Computer><Security /></System><EventData><Data Name="param1">\Device\HarddiskVolume6\Windows\System32\drivers\e1r68x64.sys</Data></EventData> </Event>

 

 

CrisselleF_C_Intel
Moderator
2,659 Views

Hello ZKłos & ZM1,

 

Yes, you may provide the SSU logs collected with 24.3 and we'll check on it. We understand that uninstalling then reinstalling the driver will take extra effort for you and we want to avoid that. Just in case we'll be needing SSU logs with 24.5, we'll let you know.

 

Hello User15797322156621988880,

 

Thank you for reporting the issue as well. Rest assured that we are closely looking into this.

 

Hello All,

 

Can you share if you have tried performing Clean Driver Installation? If not yet, sharing the steps below on how perform a clean driver installation for any Intel® Ethernet Controller/Adapter

1. Open Windows* Device Manager:  

Windows® 10:Right-click Start > Device Manager

2. Double-click Network adapters to expand the section.

3. Right-click the Intel® Ethernet Connection (model) and select Properties.

4. Click the Driver tab.

5. Click Uninstall.

6. Check "Delete the driver software for this device" and click OK.

7. Press the Windows key + R, then type "%Temp%" (without the quotation marks) delete everything from that folder, then install our latest driver from the Download Center.

https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapter-Complete-Driver-Pack

 

Please send us an update if this makes any difference with the issue you encountered.

 

Awaiting to your response.

 

Best regards,

Crisselle C

Intel® Customer Support

A Contingent Worker at Intel

BGhos2
Beginner
2,659 Views

Hello,

 

I followed these instructions and ended up with the same error and the device didn't work.

 

 

 

BGhos2
Beginner
2,659 Views

I also noticed that Checking "Delete the driver software for this device" did not remove the software under control panel > programs, so I had to manually uninstall it, but it didn't work by doing that too.

ChrisM34
Beginner
2,659 Views

The issue has nothing to do with leftover drivers files, I installed the drivers directly/manually in the Device Manager from the PRO1000/Win64/NDIS68 folder on a clean install and still got the error message.

 

It's an issue with the certificate that was used to sign the file, either because unlike every other .sys file in the 2.4.5 driver package, this driver is signed with a "Microsoft Windows PCA 2010" certificate, or I don't know.

ZKłos
New Contributor I
2,659 Views

I confirm that difference. The other three NDIS68 drivers in 24.5 package are signed by Microsoft certifcate issued by 'Microsoft Windows Third Party Components CA 2012' CA.

The driver used by I211 (e1r68x64.sys) is signed by Microsoft certificate issued by 'Microsoft Windows PCA 2010' CA.

For some unknown reasons some Windows 10 installations do not trust certificates issued by this 'PCA 2010' CA or certificates issued by this CA are treated as expired.

 

I checked drivers in 24.3 package and ALL four NDIS68 drivers there are signed by Microsoft certificate issued by 'Microsoft Windows Third Party Components CA 2012'.

 

This is clearly driver signing issue...

CrisselleF_C_Intel
Moderator
2,659 Views

Hello All,

 

Thank you for the reply and cooperation as well.

 

Please allow us to further check on this issue. Rest assured that we will provide an update within 1-3 business days. 

 

Hoping for your patience.

 

Best regards,

Crisselle C

Intel® Customer Support

A Contingent Worker at Intel

CrisselleF_C_Intel
Moderator
2,659 Views

Hello All,

 

We sincerely apologize for the delay on this matter.

 

After further checking with our engineers, we regret to inform you that this is a known issue and the fix will be available in the SW release 25.0. In the mean time, the temporary workaround is by disabling secure boot and disabling device driver signing. 

 

Thank you for the patience and kind understanding.

 

Best regards,

Crisselle C

Intel® Customer Support

A Contingent Worker at Intel

CUllr
New Contributor I
2,659 Views

The broken drivers are still available for download today, and this issue is not even mentioned in the readme.txt file on the download pages (https://downloadcenter.intel.com/download/22283/ for the whole lot, https://downloadcenter.intel.com/download/25016/ for Windows 10), let alone on the pages itself. Are you going to withdraw the download, or at least put a warning on the download pages?

 

Right now, there is nothing to stop your customers wasting lots of time with this release.

CrisselleF_C_Intel
Moderator
1,156 Views

Hello All,

 

Good day!

 

Please be informed that SW 25.0 was now available for download. Sharing the download link below with you and feel free to update us after trying it out.

https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapter-Complete-Driver-Pack

 

We look forward to your response.

 

Best regards,

Crisselle C

Intel® Customer Support

A Contingent Worker at Intel

Reply