Driverpack Solution Automatic Installation Of Drivers

[Nicol Allphin]

TheLinux kernel contains a set of well-maintained open source drivers for almost everything1, but it does not contain proprietary drivers which are closed source such as some Wi-Fi drivers, NIC drivers, and GPU drivers. Ubuntu has a built-in ubuntu-drivers program that can decide automatically which proprietary graphics driver to install, and streamlines the installation of Nvidia drivers. Open the terminal and type:

The install option of ubuntu-drivers installs drivers that are appropriate for automatic installation including their dependencies. In Ubuntu 20.04 and later running sudo apt upgrade not only upgrades the versions of the proprietary graphics drivers that were installed by sudo ubuntu-drivers install. Sometimes sudo apt upgrade even upgrades the proprietary graphics driver packages to more recent packages, in which case sudo apt autoremove removes the older packages which were replaced by the newer ones. For most users there's no reason to guess about which proprietary graphics driver to install, because if your system deserves a graphics driver upgrade it will get one.

The devices option of ubuntu-drivers lists proprietary drivers that are compatible with your computer's GPU. If your computer has an Intel processor and it doesn't have a discrete graphics processor, the command ubuntu-drivers devices will not return results that show that a proprietary graphics card driver is available to be installed because the Intel graphics driver is built-in in Ubuntu. Furthermore it is not necessary to uninstall any of the built-in graphics drivers because if a proprietary graphics driver is installed, Ubuntu will select it and use it automatically with the built-in graphics drivers remaining installed for possible use if Ubuntu has a problem running the proprietary graphics driver(s). If there already is a Nvidia proprietary graphics driver installed in Ubuntu you will need to uninstall it before installing a replacement Nvidia proprietary graphics driver.

If you visit the official AMD or NVIDIA websites you will often see that the latest version of the proprietary graphics driver for your GPU is a little bit more up-to-date than the version of the same graphics driver that is available from the default Ubuntu repositories. Don't worry about this, because if the difference between version numbers of the two proprietary graphics drivers is small, then you will get similar performance by using either of the two drivers. If you install a graphics driver from the default Ubuntu repositories, you will also get automatic updates for that driver which are sometimes linked to kernel updates.

So, I had to install a new Power Supply for my PC a couple days ago because my PC wouldn't start. After I had life again and thought all was good, I immediately noticed I was unable to connect to my wired internet.

I went to device manager and noticed my ethernet device wasn't even listed under network adapters but now under other devices as "ethernet controller". When I clicked on it, I was met with the following device status: -The drivers for this device are not installed. (Code 28) -There are no compatible drivers for this device. -To find a driver for this device, click Update Driver.

I tried troubleshooting multiple times through windows but when I followed their steps and restarted my PC, still nothing changed. Then, I went to Intel forums, videos, and websites supporting my issue and went through various guided steps to try and solve this.

After installing the latest version of Intel Ethernet Adapter Complete Driver Pack and many hoops and bounds later, I went back into device manager and noticed my ethernet device was now showing under network adapters as "Intel(R) Ethernet Controller (2) I225-V".

In device manager, I attempted to automatically install the driver through windows and it would not work being unable to find a compatible driver. I also tried manually installing it and choosing a driver and was still unsuccessful.

After enabling/disabling my ethernet device, trying the steps over and over again, trying to install an older version of the driver, updating my BIOS, made sure my ethernet cables were stable and good, and going down tons of rabbit holes, I end up where I started with the same device statuses.

2. I don't know what caused my last power supply unit to fail. I was able to power on and operate my PC the night before like any typical night, but the next day it wouldn't power on at all after trying a different power cord, outlet, etc.

When I go into device manager and attempt updating the driver with the file I extracted from the Intel Ethernet Adapter Complete Driver Pack zip file I downloaded, I am met with this screen (image applies to both searching automatically for drivers, and browsing my PC files for driver.

I also made the discovery that when I click on "Let me pick from a list of available drivers on my computer", and choose any of the listed Intel driver devices to try and install, I am met with the same (Code 10) this device cannot start. Additionally, now my device name of "ethernet controller" moves from the other devices tab to under the network adapter tab and matches the name of the driver device tried installing prior as you can see in this image:

So I went to your link and downloaded and extracted the zip file of "Intel Network Drivers" version 26.2.0.1 under the subcategory "LAN Drivers". I auto ran the app and attempted to install it was met with this screen:

Since you are using MSI product, with embedded NIC, contact MSI support for further assistance. They may be able to provide additional troubleshooting steps or even replace the motherboard if it is found to be defective.

Please be informed that we will now close this request since we haven't received any response from our previous follow up. Just feel free to post a new question if you may have any other inquiry in the future as this thread will no longer be monitored.

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.

LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.

I will be publishing four blog posts about taking Intune automation to the next level and this is the second part. With short hints I believe I will make Intune admins life easier around Windows management. I have ten years of Configuration Manager (SCCM) and Group Policy experience and in beginning of 2020 I took first steps to Intune with idea to transfer my Windows 10 infrastructure to the cloud. The idea was at least to keep the same level of automation I had before. Soon I realized that Intune built-in capabilities can't handle everything you used to do before, so .... start scripting.... again ;)

Intune doesn't have any driver packaging method, it only can allow drivers being updated from Microsoft Catalog but that does not cover Windows Autopilot phase. Idea of Autopilot is, that device being enrolled in Intune already has drivers with Windows OEM installation being done by its vendor. But in real life, organizations are re-installing existing PC devices with clean Windows 10/11 media and want them to be enrolled as well. Microsoft has presented its future driver management solution in Intune first time in Ignite 2020 but so far there is nothing there yet.

You can cover this scenario by using Powershell to enforce driver installations right away during Windows Autopilot. You can also re-use this script if you want to update drivers to on-field computers at once. Relying only on Windows Update for Business allowing updating drivers will not install non-critical drivers. I saw this behavior first time in Windows 10 build 2004 where half of my drivers were not installed because they were non-critical. My script overrides this behavior and enforces to install/update all drivers which are available from Microsoft Catalog.

- For Autopilot, I recommend to wrap this into Win32 app and distribute to All Devices (Be aware that if you already have existing devices, this will run to all on-field computers also, so test this first!). - Later if you want again to run this driver update for all computers, delete detection method file with other script or manuall one-by-one.

Taking advantage of the Visual Studio development environment, the WDK provides a test feature that enables you to build, deploy, and debug a driver on a test computer. To successfully deploy a driver to a test system using the WDK, you must first set up and configure a test computer. You can set up and configure multiple computers if you want to test your driver under different testing scenarios.

From the property pages for your driver project, you have additional control over how you want your driver deployed for testing. You can choose to deploy the driver automatically whenever you build the driver solution in each configuration.

When you enable deployment for your driver package project, the driver is automatically deployed to the test computer you have selected when you build your solution. You can use the Deployment property page to configure options for driver installation and deployment. See Deployment Properties for Driver Package Projects.

When you enable deployment on a test computer, you can also automatically enable and configure Driver Verifier, KMDF Verifier, or UMDF Verifier on the test computer to enhance the effectiveness of testing. To set these options for the driver package project, select Configuration Properties, select Driver Install, and then select the following property pages.

3a8082e126