lasashost.blogg.se

1. Install hp officejet pro 8610 printer driver install#
2. Install hp officejet pro 8610 printer driver drivers#

Whether it was coincidental or not - I'm not sure. Interestingly, very shortly after I added these - the installation process continued (after previously failing 3 times in a row). I added the loggung directives after noticing that the HP installer was repeatedly trying to query this key to no avail. I did manage to finally get it to work at the 4th attempt - and only after I added HP logging directives to the registry (HKEY_CURRENT_USER\Software\HP\NG\Logging). So this is definitely not a case of remnants of a messy installation or something of the sort.

Install hp officejet pro 8610 printer driver drivers#

I downloaded the latest drivers for the HP OfficeJet 8620 about an hour ago from the HP website.

Install hp officejet pro 8610 printer driver install#

This is a brand new install of Windows 10 1903, 100% clean - never had any form of printer drivers on it beforehand. I'd like to add that I'm seeing the exact same behavior that PSUHammer is reporting on a very similar printer - an HP OfficeJet 8620. Reset printer network settings to default.Clean install of drivers (uninstall, reboot, reinstall).Why does this driver not want to install all of a sudden? I printed the "Wireless Network Test" page from the printer LCD and all network checks passed. The printer has a solid blue connection light on the LCD panel and the IP address and gateway info are all accurate. But, the driver install fails saying "Unsuccessful Network Installation" I get to a screen where it scans the wireless network for the printer and finds it. So, it downloads latest driver and starts to install. SO, I fire up the HP Print and Scan doctor app (5.2.1) and it is showing that the printer is "not installed" which is weird. Well, the 8610 is showing up in device manager and I can even print to it. All of a sudden, I had issues trying to scan as the Microsoft Scan app says I have no scanner installed. I just started having this issue which MAY correspond with updating windows 10 to 1903 although I can not confirm it is related.