HP customer claims firmware update shoved printer off support cliff
Briefly

HP customer claims firmware update shoved printer off support cliff
An OfficeJet 4650 printer in Quebec reportedly stopped working after a firmware update, then began repeatedly throwing server connection errors and refusing to reconnect. Internal records obtained through a PIPEDA access request reportedly include an alert about Gen1 printers losing connection to Web Services. Notes attributed the failure to a server update affecting connectivity to HP Instant Ink and indicated the printers were likely at end of service life. Another owner reported an update left an OfficeJet 4650 unable to connect over Wi-Fi, Bluetooth, USB, or even a local network, with factory resets not restoring functionality. The Quebec customer described weeks of support interactions, cases being closed, promised callbacks not arriving, and eventual acknowledgment that the issue was linked to HP servers and already known internally.
"An internal alert titled "Gen1 printers losing connection to Web Services," along with notes attributing the failure to "a server update affecting connectivity to HP Instant Ink" combined with the printer being "likely at end of service life.""
"The customer says the OfficeJet 4650 stopped working halfway through printing a book manuscript following a firmware update, after which the printer began repeatedly throwing server connection errors and refused to properly reconnect."
"In a Reddit thread discussing the issue, another OfficeJet 4650 owner said a printer update left the device unable to connect over Wi-Fi, Bluetooth, USB, or even a local network. Factory resets reportedly did nothing, and the user said they eventually gave up and went to a library to print their documents."
"The user describes weeks of repeated calls to HP support staff, cases mysteriously closed, promised callbacks from escalation teams that never arrived, and repeated attempts to blame local connectivity issues. Eventually, according to the customer, HP supervisors acknowledged the issue was linked to HP servers and was already known internal"
Read at www.theregister.com
Unable to calculate read time
[
|
]