Hi Greg! Thanks so much for the reply! I talked to my friend again, so I have some more info.
- Printer is on and working, it is a wireless printer. I was able to confirm that it was on the same network as the laptop I remoted into.
- I uninstalled everything printer related that I could see. I should have taken better notes, but it was several HP related services.
- I forgot about this step the first time through, I came back to this later.
- I deleted the printer and its associated fax machine, then restarted the PC.
- I downloaded the Full Feature Software and Drivers from HP's website (v40.13). I didn't check for new firmware here, but I did later.
- I ran the printer setup from HP and it did complete, which is new, the last time I tried it got stuck loading for 10+ mins.
After this, I was able to pull up the printers web management portal with it's IP address, which is something I couldn't do last time. Here I checked the firmware and it was already up to date.
Windows also reported that it was able to connect to the printer, which is progress from my original post.
However, after trying to print a test document, I got a new error.
Print Queue
So here I realized that I had forgot step 3. Option 1 did not work, Windows says "printmanagement.msc not found". Option 2 gave me some more interesting results, I found a bunch of old drivers from different model printers and removed those. However I was not able to remove the printer drivers for the 5742 with the following error:
I checked again after removing the old drivers and got the same error I did last time.
I checked the printer's web interface to try to look at the error log, and it did have an event log, but it wasn't anything interesting, just one message with no timestamp about a network connectivity error.
Normally the way I uninstall printer drivers is through Device Manager. I could try going that route again, but my hopes are not super high that I would get a different result.
Any thoughts? My best bet would be to try to get more visibility into exactly what kind of error the printer experienced, but I haven't had any luck finding out from the printer or from the internet.
Thanks again so much for your time!