What Folder Do I Download Intel Proset Software and Wifi Drivers.
Introduction
This web log will be all nigh installing Intel I211, I217V, I218V and I219V drivers on Windows Server 2016 with EUFI kicking. I'm running Windows Server 2016 as my master Os for lab, testing, Hyper-5 with nested virtualization etc. I like information technology that way because I have all the options of the server OS at my disposal. Especially with the nested virtualization an NVME deejay comes in handy. I also kick from NVMe so I demand UEFI and utilize secure kick. That's OK as it's mode better than the old BIOS and enables more scenario.
Windows Server 2016 doesn't have any drivers for the I211, I217V, I218V and the I219V NICs.
The Intel driver for them are only for Windows x and won't install on a server OS. As you tin see in the screenshot higher up that'south a system where I have the I211 driver already installed actually. We'll piece of work on the I218V equally an example hither.
That'south nothing new and we've dealt with this earlier by editing the .inf file for the commuter. What might be new to some people as EUFI & NVME become a bit more popular is how to get a driver with an edited .inf file installed on your Windows Server Os.
Don't worry even with an Os booting from EUFI with secure kicking you lot can nonetheless disable driver signing / integrity checking when needed. We'll walk you through an approach for installing Intel I211, I217V, I218V and I219V drivers on Windows Server 2016 with EUFI kicking.
Installing Intel I211, I217V, I218V and I219V drivers on Windows Server 2016 with EUFI boot
Google for the Intel drivers of your NIC. Mine is a I218V. The instructions will piece of work for a I217V or and i219V besides. But adapt accordingly.
After downloading the most recent Windows x (x64 bit, we'll use them with a server Bone so there is no 32 fleck here) Intel drivers form the Intel site we rename the exe to identify what package it is. Nosotros then extract the content to our piece of work space. A complimentary tool similar 7zip will do the job only fine.
Prepping the .INF file
For the I211 we need to edit the .inf file and for the I217V, 218V and 219V we'll edit the e1d65x64.inf file in annotation pad or your editor of choice. You'll discover information technology in the NDIS65 folder: C:\SysAdmin\PROWinx64\PRO1000\Winx64\NDIS65. The 65 in the folder and file names identifies our OS version (Windows 10 / Windows Server 2016).
But how practice we know what .inf file to edit? We catch the hardware ID'south from the backdrop of our NIC or NICS.
Below you see the Hardware IDs for mu I218V. The I211 has PCI\VEN_8086&DEV_1539&SUBSYS_85F01043&REV_03 and my Iv218V has PCI\VEN_8086&DEV_15A1&SUBSYS_85C41043&REV_05.
Drop the PCI\ from the beginning of the string and everything from the "&" on at the cease. Then for the I211 we'll apply VEN_8086&DEV_1539 and for the I218V we'll utilise VEN_8086&DEV_15A1. We throw these ID strings into some PowerShell we run in our C:\SysAdmin\PROWinx64\PRO1000\Winx64\NDIS65 folder.
Go-ChildItem -Path "C:\SysAdmin\IntelWindows10Drivers21.i\PRO1000\Winx64\NDIS65" `
-recurse | Select-String -blueprint "ven_8086&dev_1539" | group path | select name
Become-ChildItem -Path "C:\SysAdmin\IntelWindows10Drivers21.i\PRO1000\Winx64\NDIS65" `
-recurse | Select-String -design "ven_8086&dev_15A1" | group path | select name
So for my I218V I open op the e1d65x64.inf file in notepad++
I search for [ControlFlags] section and I edit the content of that department by deleting everything in it.
So information technology looks likes
And so I search for section [Intel.NTamd64.10.0.1] and I copy everything in in that location (I don't bother to only copy the entries for my particular NIC or and then.
Copy everything nether that heading
I then search for section [Intel.NTamd64.x.0] and I paste what I only copied from section [Intel.NTamd64.10.0.i] nicely underneath what's already in there.
Save the file. Basically, you're done here.
Installing the commuter
We now need to alter the standard startup setting of Windows Server 2016 temporarily because we will non exist able to install a driver that'southward been tampered with. If you don't lower the security settings, you'll get an error just like this ane:
What I did is run the following in an elevated command prompt:
bcdedit /fix LOADOPTIONS DISABLE_INTEGRITY_CHECKS
Annotation: as I'm using UEFI & secure boot the following won't work as if yous were using an older BIOS without secure boot.
bcdedit /set TESTSIGNING ON
bcdedit /set nointegritychecks OFF
But that's OK. What we need to do is plow it of in another way. That concluding command bcdedit /set nointegritychecks OFF iIs not needed anyhow. So, forget about that 1. As a replacement for bcdedit /set TESTSIGNING ON you can use and avant-garde start choice (requires reboot). You can also disable secure boot in EUFI, start again and then run bcdedit /fix TESTSIGNING ON. I prefer the starting time as fixes itself the adjacent boot and I don't have to turn secure boot on again later on.
Become to setting and select Update & security.
Navigate to Recovery and click Restart Now
It will reboot to the post-obit screen.Click Troubleshoot.
Select and click Avant-garde options.
Click Startup Settings.
We click restart on the next screen
Information technology will restart Advanced boot options. Select to disable driver signature enforcement. Striking ENTER.
When your server has restarted, you'll be able to install the driver y'all tampered with. To do and so, in device manager select your NIC and click Update Driver Software.
Select to Browse my reckoner for driver software
Point to the C:\SysAdmin\PROWinx64\PRO1000\Winx64\NDIS65 folder with your edited .inf files.
You'll get a alert that the publisher of this driver can't be verified. Merely equally you're the 1 doing the tampering here, you'll exist fine.
The result is successful install of the commuter with a functional NIC for your system.
Cool, you're in business!
No please reverse the setting y'all made to the integrity checks to make your system more secure once more. From an elevated command prompt run:
bcdedit /prepare LOADOPTIONS ENABLE_INTEGRITY_CHECKS
At present reboot and you lot're all secure again. That'southward it, yous're done. I had both an I211 and an I218V NIC on my motherboard so I had to do this for both. Happy testing!
What Folder Do I Download Intel Proset Software and Wifi Drivers.
DOWNLOAD HERE
Source: https://blog.workinghardinit.work/2017/06/19/installing-intel-i211-i217v-i218v-i219v-drivers-windows-server-2016-eufi-boot/
Posted by: cassidydaily8blogs.blogspot.com
0 komentar