This will produce a list that will show you the locations of the drivers and dependant files under the following properties: Path Replace name of printer and remove the angle brackets, if the name has a space in it please put in double quotes - "name of printer". Get-printerdriver $printer.drivername | select * Now to use the printer name to get the driver locations: $Printer = get-printer | Select * This will list the names of the printer and the corresponding driver. Identify the name of the printer by using this cmdlet: get-printer I would personally suggest trying to use powershell: For those who many not have a working pc to harvest the driver from in order to get their laserjet5 working on Windows 10, I provide them here.
#Hp laserjet 4050 driver legacy install#
Using CraftyB's answer, I took the entire folder indicated in the "InfPath" results of his 2nd block of code and browsed there at the "Have Disk" prompt during install and it worked. Also perhaps worth noting is this is purely a network printer on my home network. I don't think this is a "default driver" as some have suspected. Here is the output from his PowershellOutput instructions. Update 3 December 2018: So far, the furthest progress I've made has been with CraftyB's answer. HP in cahoots with MS dropped this from the default printer install list sometime in the last 6 months (See most recent comments noting this disappearance): How can I identify which driver I'm using out of the hundreds present in the repository folder (“C:\Windows\System32\DriverStore\FileRepository”.)? I do not want to have to buy software to do this and the target machine is Windows 10 Home (cannot import using printermanagement). I would like to harvest the driver from the units that are already working and put it on the other windows 10 64bit that doesn't and can't get it. Hp no longer supports this old printer (laserjet 5) and so it has recently been removed from the default install list or windows update. Other windows 10 units have the printer installed already (for a long time).
0 kommentar(er)
