Windows 10 Driver Install
Karmen Mcarthun
If you are unfamiliar with the device and driver installation process, we recommend that you start by reviewing Roadmap for Device and Driver Installation. You may also want to read Overview of Device and Driver Installation for a high-level overview of this process and its components.
To target Windows 8.1, Windows 8, and Windows 7, install an older WDK and an older version of Visual Studio either on the same machine or on a separate machine. For links to older kits, see Other WDK downloads.
Join the Windows Insider Program to get WDK Insider Preview builds. For installation instructions for the Windows Insider Preview builds, see Installing preview versions of the Windows Driver Kit (WDK).
The WDK NuGet package consists of essential libraries, headers, DLL, tools, and metadata used for building Windows drivers that can be shared and supported by modern CI/CD pipelines. Users can access and consume the NuGet packages directly from nuget.org within Visual Studio. Using NuGet with the WDK provides a convenient solution for WDK acquisition and updates. It manages dependencies such as the SDK, to help keep the driver development tool chain up to date. For more information, see Install the latest WDK using NuGet - Step by Step.
Starting with WDK version 10.0.26100.1, the WDK now supports development, testing and deployment of drivers on ARM64 machines. The WDK/EWDK can be installed and run natively on ARM64 hardware, in addition to the previously supported emulation of x86 KMDF/UMDF2 drivers on ARM64 hardware. There is also support for debugging and deployment of drivers to an ARM64 target machine from both ARM64 and x64 host machines. The process of installing WDK/EWDK on ARM64 machines will automatically identify and install all the necessary dependencies including build tools, binaries, and libraries.
The provided links for the SDK and the WDK have matching build numbers, which is always required for the kits to work together. If you decide to install your own SDK/WDK pair, perhaps for a different Windows version, ensure that the build numbers match. For more details, see Kit versioning.
As an alternative to downloading Visual Studio, the SDK, and the WDK, you can download the EWDK, which is a standalone, self-contained command-line environment for building drivers. It includes Visual Studio Build Tools, the SDK, and the WDK.
You can optionally use the Visual Studio interface with the build tools provided in the EWDK. To do this, ensure that the Visual Studio major version matches the version of the Visual Studio Build Tools in the EWDK. For example, Visual Studio 2022 works with the EWDK that contain VS17.X build tools. For a list of Visual Studio 2022 version numbers, see Visual Studio 2022 Releases.
To build a driver, the build number of your SDK installation must match the build number of your WDK installation. The QFE values does not need to match unless your driver uses functionality that is only available in the headers included with a later QFE.
A quick way to see the full build string for locally installed kits is to go to Windows settings (Win+I), navigate to Apps, then Installed apps, and in the Search box type kit. The full build string appears to the right of the kit name. If you navigate to C:\Program Files (x86)\Windows Kits\10\Include, note that the QFE shown there is hardcoded to .0, so this is not a reliable way to check your QFE identifier. Also note that when you install a kit, the new installation replaces any previously existing installation of the same build number. When you install Visual Studio with the Desktop development with C++ workload, if the installation payload includes the Windows SDK, the right-hand Summary pane also shows a hardcoded .0 for QFE.
I have a few handheld radios that I need to update the frequencies and when I connect to the USB, it fails to connect. In device manager and Ports it says - "Please install corresponding PL2303 driver to support Windows 11 and further OS"
Hello! You've posted your question in the Tech Community Discussion space, which is intended for discussion around the Tech Community website itself, not product questions. I'm moving your question to the Windows 11 space - please post Windows 11 questions here in the future.
Windows 11 update loaded Prolific PL2303 driver 3.8.40.0 and when I go to device manager it says "Please install corresponding PL2303 driver to support Windows 11 and further OS" This driver does not even attempt to communicate with my X10 CM11 hooked to my serial port. I had to go to Prolific website and load their current driver 3.6.81.357. (uninstall driver first) Serial to X10 device now working fine. Don't install Windows update for Prolific or it will change it back.
I want to do clean windows installation on my laptop and install all drivers from laptop manufacturer site. The problem is when I install windows with internet connection windows automatically install all OEM drivers right after the first boot up.
My question is: Is it fine to just download and install laptop manufacturer drivers on top of OEM drivers installed by windows? Or should I install windows offline and right after the first boot up install manufacturer drivers from USB and then connect to the internet?
You can always download drivers from the manufacturer's websiteand install them over the Windows drivers. However, if the driversin Windows are more recent, Windows will reinstall its own driverson the next boot, thus replacing the ones you just installed.
Also, it is possible that Drivers appear on the Manufacturer's website before being in the Manufacturer's Driver Update App and possibly before being in the Windows Update Catalogue. There is nothing you can do about this, so probably just wait for Windows to offer the update.
I don't know why your question has received so many down votes. Specifically when building workstations for creative applications like Premiere Pro or Avid Media Composer we are advised to NOT allow windows to install these devices automatically. We are always encouraged to do the above and install the manufacturer drivers instead.
I am planning to write a basic windows registry filter in C. The purpose of the filter is to hook all (user and kernel privileged) registry calls so that I can use them in my program. I am basically copying regmon/process monitor by Mark Rusinovich but more basic.
As for just installing a kernel mode driver, you may use the Service Controller (sc.exe). Use sc create [service name] binPath= [path to your .sys file] type= kernel to create a kernel-mode service and sc start [service name] to start it. Don't forget to sc stop and sc delete it before making changes to the driver.
Basically drivers are considered as Services as such you can utilize the Service COntrol manager Using the aforementioned APIs what you basically achieve is the appropriate entries in the registry under the Services key. For a sample of how to achieve this check this article, scroll to the bottom to the section named "Dynamically Loading and Unloading the Driver". Furthermore if you want to achieve easy debugging/development and are using VS2k10 I'd suggest you use the free VisualDDK I believe this should be enough to get you going.
So, naturally, I tried uninstalling the driver. But, then, I cannot install the new driver without restarting my computer. And when I restart my computer, the default driver is already halfway through installation by the time I get back to the Device Manager dialog, putting me back to square one.
Is there a way to get around the "The best driver software for your device is already installed [...] Windows has determined the driver software for your device is up to date" prompt and force installation of an older driver?
With enough persistence you can even install a completely wrong driver into a driver slot, very rarely you could even cause a no-boot situation. Hopefully you know what it is and what belongs there for sure before forcing it in.
I have attempted driver installation in three ways. First, from the Quartus installer. Second, using the Windows manual driver install process starting from the Control Panel. Third, using the program DPinst.exe. I ran that program with its /c option and it reported errors in a cmd window.
The time invested in this on our part is running to days now. Two different engineers have attempted driver installation from fresh 20.1.1 downloaded Quartus Lite and also Quartus Programmer software onto machines that ran Quartus prior to being re-imaged with Windows 10. We are running Windows 10 ver 10.0.18363.1377.
@JohnT_Intel Has this reached a critical enough level sufficient for someone at Intel to replicate our attempts on a freshly imaged or new Windows 10 PC? Am I missing some necessary step -- I am Admin privileged on my machine, run the installer as Admin, have a USB Blaster connected ?? We are also working with senior Arrow FAE Andy Lee.
I would recommend you to use the Quaruts Programmer 20.4 which is the latest version with the latest driver or you can disable the driver signature as the step below. The reason that you will failed to install is because the driver signature of the Quartus 20.1 has already expired.
5 - If your boot drive is BitLocker encrypted, you'll need to enter the recovery key (press return, enter the key in the text box then hit return again - it took me three goes to realize I had to hit return before I could enter they key !)
When you said the driver applies to both USB Blaster and Blaster II -- the drivers have different driver directories in Quartus installation c: drive areas. EG ../drivers/usb-blaster and ../drivers/usb-blaster-ii.
For the manual Windows work-around, are you saying to copy the downloaded usb-blaster-ii driver files also to C:\intelFPGA_lite\19.1\quartus\drivers\usb-blaster? And rename them usb-blaster.cat and .inf?
Sorry for the confusion, what I mean is that the issue is similar between USB-Blaster and USB-Blaster II except that the directory location is different. So you can use the similar step to disable the driver signature then only install the usb-blaster driver.
93ddb68554