Discovering drivers online for old equipment can extend from difficult to unimaginable if the rigging is obsolete by 10 years, was never broadly coursed in any case, and never again gets support from the producer. Such was the circumstance for a Rosewill-marked PCI remote system connector that we as of late installed on Windows 10 without an original installation disc or traditional installer.
The device, a “Ralink RT61 Turbo,” was acquired in 2009 and still performs all around ok in spite of not having programming updates since Windows Vista/7 and not being consequently perceived by more up to date forms of the working framework. Not having an Internet connection on another OS can be especially irritating because you can’t get online to look for the drivers.
In the wake of attempting to install the card on Windows 10 with numerous files from around the web (downloaded somewhere else), we found that you can send out drivers for outsider devices from one copy of Windows to another – extraordinary news seeing that we had a past case of Windows on another drive where the Wi-Fi card was installed and utilitarian.
Create and Save a List of Devices/Drivers
If you have to identify a specific bit of equipment or the area of a driver file, the most straightforward method might be from Windows’ “System Information” application, which can be propelled via looking Start or Run for msinfo32.exe.
The utility opens a window that rundowns framework data including all devices, their drivers (with a full driveway for the area of everyone so they’re anything but difficult to discover) among different subtleties, and this data can be spared to a book file by going to File > Export (no real drivers are traded).
Create a List of drivers in the Command Prompt
You can likewise produce a rundown of drivers by entering any of these lines into a Command Prompt (barring the notes subsequently). A portion of the commands in this article may require executive benefits and a raised Command Prompt can be opened by right-clicking cmd.exe > Run as Admin.
While entering any of these commands should deliver a rundown of drivers, everyone yields different data and organizing.
- dism.exe/Online/Get-Drivers (produces a rundown of outsider drivers)
- dism.exe/Online/Get-Drivers/All (produces a rundown of all drivers in the Driver Store)
- driverquery (incorporates essential data)
- driverquery/FO list/v (incorporates more data)
Additionally, note that you can copy one of those lines and afterward right-click anyplace in your Command Prompt window to glue the content. If that isn’t working, right-click the Command Prompt’s title bar (the Windows bar on top), go to Properties and empower “QuickEdit Mode.”
Save that list of drivers as a text file
By adding another string of content as far as possible of those commands, the yield can be spared to another content file in an area based on your personal preference by changing registry way in the command that you enter. If you need the file spared to your desktop, still make certain to change the username from TechSpot to your own:
- pnputil.exe/e > C:\Users\HP\Desktop\driverlist.txt
- dism.exe/Online/Get-Drivers > C:\Users\HP\Desktop\driverlist.txt
- dism.exe/Online/Get-Drivers/All > C:\Users\HP\Desktop\driverlist.txt
- driveryquery > C:\Users\HP\Desktop\driverlist.txt
- driverquery/FO list/v > C:\Users\HP\Desktop\driverlist.txt
Export All Driver Files to a Backup Folder
For drivers to be installed on Windows, they should be situated in the working framework’s “DriverStore” folder (C:\Windows\System32\DriverStore\FileRepository), which contains all driver INFs and their related files. This is the place we’ll be recovering the drivers from.
Before beginning, note that you might have the option to avoid the issue of sending out and bringing in the drivers. From the Device Manager on the copy of Windows which needs the driver, if you can explore to the driver store folder of another Windows installation where the driver is found, then the Device Manager ought to have the option to look that goal for good driver files. Right-click the device, go to “Update Driver,” then pursue the prompts until you can peruse to DriverStore on the different OS (or any place your drivers are).
Likewise, sending out the driver files from Windows to exclude extra programming that would regularly be packaged with a driver bundle, for example, a utility that goes with the driver. Be that as it may, as a rule, Windows gives the given usefulness locally somewhat (an interface for connecting to remote systems for example). All things considered, you might have the option to copy the program files legitimately from one occurrence of Windows to another, or locate the utility as a different download from the driver, or a comparable bundle with a similar utility.
Export/backup Windows drivers by means of Command Prompt
Running both of the Command Prompt or PowerShell tasks beneath will separate the entirety of the drivers in System32\DriverStore from your dynamic Windows installation and spare them to another folder (we physically made a folder in our desktop called “driverbackup”), from which you can import/install them to another occasion of Windows.
Enter this command to start sending out the entirety of your driver files to that new folder:
dism/online/send out driver/destination:C:\Users\HP\Desktop\driverbackup
Export/Back-up Windows drivers by means of PowerShell
On the other hand, you can play out a similar activity by entering this command into a raised PowerShell.
Export WindowsDriver – Online – Destination C:\Users\TechSpot\Desktop\driverbackup
“- Online” assigns that the files are being traded from the presently dynamic working framework. Be that as it may, you can send out drivers from a disconnected picture with a different command:
Export WindowsDriver - Path C:\offline-picture - Destination C:\Users\HP\Desktop\driverbackup
If these commands aren’t working, you may need to install the most recent adaptations of Microsoft’s ADK or potentially .NET Framework.
Step by step instructions to Install Exported Windows Drivers
There are a couple of choices for bringing in the driver to another installation of Windows, including one that just includes a couple of snaps from the GUI of File Explorer:
- Boot into the copy of Windows where you need to install the exported drivers
- Explore to the back-up folder and discover the folder for the driver that you need to be added to Windows
- Right-click the INF file and pick Install.
You may likewise have the option to have Windows Device Manager consequently look for a driver in the sent out folder by right-tapping the device, going to “Update driver” and following the prompts for “Physically install a driver” until you can peruse to your drivers. This didn’t work for our Wi-Fi connector, yet the past method did (physically installing legitimately from the INF file).