-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Printers
- Printer Setup, Software & Drivers
- Who Me Too'd this topic
Create an account on the HP Community to personalize your profile and ask a question
10-22-2019 03:18 PM
I have spent 5 hours (not an exaggeration as it was actually more) trying to get my HP printers online including having a person at HP take over my PC and try to fix the issue. After he consulted twice with a supervisor, he said he doesn't know how to fix it. Both printers - HP 3050 Deskjet and HP envy 6255 - have worked wirelessly on my wifi until this morning when both threw "offline" errors. They are connected to my wifi as are all of my devices so the wifi and internet aren't the issue. They both quit working with AlL of my devices - desktop Dell with Windows 10, Dell laptop with Windows 10, Kindle Fire and my iPhone 6s - so I know the OS isn't the issue. I have rebooted everything - the modem, the router, the PC and the printers - to no avail. Our PCs cannot "find" either printer. After some tweeking, I managed to get the 3050 connected, but nothing prints to the 3050; they print to the 6255. I have downloaded the 6255 drivers, the firmware and the software for the HP Envy 6255, but the files don't install. When I look at the device manager, Printer, I see: HP 3050 and "unknown device." I am quite frustrated because it is clear that the issue has to be the drivers for these printers. I am ready to go out and buy a printer that will not be an HP. This is not the first time my printers unexpectedly went offline, but it's the first time I have not been able to fix them.