Download Driver Ethernet Windows 10 (64-bit)
Laura N Gerard
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.
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.
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.
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.
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.
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.
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.
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.
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 ( for the whole lot, 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?
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
My main problem is that I need to sync my devices and iTunes won't detect them without the driver. Windows can detect my devices and they show up in File Explorer. I am also able to get photos and videos that I have taken off the devices and onto my computer with no problems.
Thank you so much for this, I was tearing my hair out. I followed the directions in your link, and the most useful part was when you mentioned that the device might be listed under "portable devices", where mine was. It didn't show as the Apple Mobile Device USB Driver at all, but I followed the rest of your instructions by pretending that "Apple iPhone" was the "Apple Mobile Device USB Driver" and it made my iphone 5S "magically" appear in iTunes. So, so happy, thank you so much!
What is the exact alert you get on screen and which version of Windows is it? I just plugged my iPhone into a machine that doesn't have iTunes installed and changed the auto launch options to do nothing each time I connect. It still makes the device connected noise but that is all.
I also tried to untrust the PC by resetting the Location and Privacy settings, after doing that it does NOT ask me if I want to trust, so it still must be trusted, that's somewhat of another bug/issue.
I also mentioned elsewhere that my iPhone 5 did NOT have the same problem, actually that is only partially true. I was using a mophie and there for connecting via micro USB vs. lightning, in that scenario it did not give the message, but I tried today with lighting and it behaves just like the iPhone 6s which makes more sense to me.
Windows already has a driver for the iPhone that supports it as a camera. You shouldn't need to install Apple Mobile Device Support and its driver just to suppress a connection dialog box, but you may need to tweak whatever is raising it. Can you post a screenshot of this alert? I've a feeling I'm missing something. BTW I was using a Windows 7 machine earlier and the only 10 system I have to hand already has iTunes on it so I cannot readily replicate your situation. Take a look at -autoplay-defaults-windows-10. You ought to be able to set autoplay to ignore the iPhone connecting.
i just installed iTunes and everything is fine, I'll probably just keep in on there with auto sync off as I don't want stuff on the computer. if I do uninstall iTunes I'll probably grab the driver first, did play with the auto play settings and whatnot.
Thank you! I got all the way to step 8 but there was no Apple Mobile Device USB Driver listed...just MTP USB Device. I successfully updated that. I restarted computer but still no luck. Thanks for the idea though.
Try the reinstall then. If you have a 64-bit system you could try the for older video cards release. Or you could revert to the previous build of iTunes that worked for you. See the roll back advice at iTunes installers.
4a15465005