Printing Errors or Lights & Stuck Print Jobs

I posted about my issue in a reply on this thread:

https://h30434.www3.hp.com/t5/Inkjet-Printing/Officejet-Pro-8610-won-t-install-on-Windows-10-1903/m-...

However, given that this thread is marked as 'solved' (even though it was only worked-around), I'm bringing this up as a new top level thread.

The summary is that installation of the 8620 drivers fail - repeatedly - to find a printer during setup.  They always fail with failing to find a printer - after 5-10 minutes of searching.

This is a brand new install of Windows 10 1903, 100% clean - never had any form of printer drivers on it beforehand - from HP or any other vendor.  I downloaded the latest drivers for the HP OfficeJet 8620 from the HP website (as of July 2, 2019).  So this is definitely not a case of remnants of a messy installation, outdated drivers or something of the sort.

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).  I added the loggung directives after noticing that the HP installer was repeatedly trying to query this key to no avail.  Interestingly, very shortly after I added these - the installation process continued (after previously failing 3 times in a row).  Whether it was coincidental or not - I'm not sure.

In terms of what's in the log - it's pretty much full of those:

20190701222929:0272695401 (000002 ms) [10964] {tid: 0x3688} 2022: (DB) The connection to 192.168.0.114:8080 (00000000030765B0) is not marked for closure
20190701222930:0273696382 (001000 ms) [10964] {tid: 0x3688} 1998: (DB) Current tick count: 20273500
20190701222930:0273697378 (000000 ms) [10964] {tid: 0x3688} 1999: (DB) Current number of connections: 1
20190701222930:0273698190 (000000 ms) [10964] {tid: 0x3688} 2000: (DB) Current number of COM objects: 1
20190701222930:0273699070 (001003 ms) [10964] {tid: 0x3688} 0662: (->) CIONetwork::GetPort
20190701222930:0273699930 (000000 ms) [10964] {tid: 0x3688} (<-) CIONetwork::GetPort (Dur: 862 us)
20190701222930:0273700662 (000000 ms) [10964] {tid: 0x3688} 0654: (->) CIONetwork::GetAddress
20190701222930:0273701370 (000000 ms) [10964] {tid: 0x3688} (<-) CIONetwork::GetAddress (Dur: 711 us)
20190701222930:0273702050 (000002 ms) [10964] {tid: 0x3688} 2022: (DB) The connection to 192.168.0.114:8080 (00000000030765B0) is not marked for closure
20190701222931:0274703072 (001000 ms) [10964] {tid: 0x3688} 1998: (DB) Current tick count: 20274515
20190701222931:0274704308 (000000 ms) [10964] {tid: 0x3688} 1999: (DB) Current number of connections: 1
20190701222931:0274705289 (000000 ms) [10964] {tid: 0x3688} 2000: (DB) Current number of COM objects: 1
20190701222931:0274705954 (001003 ms) [10964] {tid: 0x3688} 0662: (->) CIONetwork::GetPort
20190701222931:0274706662 (000000 ms) [10964] {tid: 0x3688} (<-) CIONetwork::GetPort (Dur: 711 us)
20190701222931:0274707392 (000000 ms) [10964] {tid: 0x3688} 0654: (->) CIONetwork::GetAddress
20190701222931:0274708365 (000000 ms) [10964] {tid: 0x3688} (<-) CIONetwork::GetAddress (Dur: 959 us)

This goes on and on and on - and each 'cycle' of these (two cycles pasted, but there are dozens) takes one second (as is evident from the timestamps - 01-Jul-2019, 22:29:30, and then 01-Jul-2019, 22:29:31, etc.  It seems that something in the network code here isn't playing nicely with Windows 10 1903, is failing repeatedly, and then sleeping for ~1sec before trying again.  On my first three attempts apparently it gave up after trying those for about 5 minutes - and on the 4th attempt somehow it succeeded.

Scanner installation failed even when the printer drivers installed successfully.

Similarly to the poster in the other thread - HP Smart (from the Microsoft Store) appeared to work without a hassle - but I only tested it after the regular drivers successfully installed so I'm not sure whether it's using its own drivers or not.

The same issue *appears* to affect "HP Scan Extended" - which I have installed on another PC which I upgraded to 1903.  It still works - but takes AGES to start up (it was never blazing fast, but it was never that slow).  Enabling logging - the same log pattern appear to repeat themselves for HP Scan Extneded as well.

There's clearly some sort of an incompatibility between the native HP drivers and Windows 10 1903. 

So while the original thread is marked as 'solved' - it's not truly solved, it's worked-around by using a completely different software package (HP Smart).  The official drivers from HP are simply not working well with Windows 10 1903 and should be fixed.

Thanks!

Zeev