HP Printer 79 Service Error: Find What Is Crashing the Printer

HP defines 79 Error / 79 Service Error as an internal firmware error in current support guidance. Do not jump straight to a factory reset. First see whether the printer can reach Ready with external job-delivery paths isolated—not just Ethernet/USB, but wireless or other active print paths where applicable. That test separates a persistent device-side failure from many externally triggered job, file, driver or connection paths.

HP LaserJet · Error 79Firmware · Network · Print jobLast reviewed Sep 27, 2026
🎯 This guide matches when:
The display says “79 Error”, “79 Service Error” or “Turn off then on”.The printer restarts, freezes, or returns to Error 79 after a job or connection is restored.You want to identify the trigger before resets, firmware changes or service.
30-second diagnostic split
79 clears after one restartPreserve what happened immediately before it; an intermittent file, job or connection trigger remains possible.
79 returns with LAN/USB connectedBoot isolated before changing drivers or printer settings.
Printer reaches Ready while isolatedHold old queues, reconnect one path, and test one simple job.
79 remains while isolatedCheck model-specific firmware/support guidance; the evidence now points away from a normal queued network job.
⚡ Quick Fix — restart once, then isolate if Error 79 returns

Turn the printer off, wait at least 30 seconds, then turn it on. If Error 79 returns, power it off again and isolate external data/job-delivery paths before the next boot. Disconnect Ethernet/USB and, where the model/configuration permits, ensure Wi-Fi or other active print paths cannot immediately restore traffic. HP's current Error 79 procedure uses connection isolation before firmware checking; the goal is a genuinely quiet boot, not merely an unplugged Ethernet cable.

Verify: Record whether the printer reaches Ready with external data connections removed.

Diagnose by when Error 79 returns

The useful question is not merely “is the firmware old?” It is what has to be present for the firmware error to recur? A printer that stays Ready while isolated gives different evidence from one that shows 79 before any external connection or job is restored.

1
79 before LAN/USB is restored?
Continue with model-specific firmware and service diagnostics; do not blame the PC queue yet.
2
79 only after a connection is restored?
Hold queued jobs first, then reconnect only that path.
3
79 only with one document or workflow?
Preserve that file/application/driver combination and compare it with a simple known-good job.

Verify: You can state exactly which stage reproduces the error: isolated boot, connection restore, or a specific job/workflow.

Fix path #1 — if the printer reaches Ready while isolated

Do not immediately reconnect every path and release the whole queue. Hold pending jobs on relevant clients and print servers first, and account for other producers such as mobile/cloud printing or managed print workflows where applicable. Restore one path, confirm the printer remains Ready before any queued job is delivered, then send one controlled simple test page.

HP's guidance says intermittent Error 79 should be isolated to something specific in the environment, such as a particular file or connection type. This controlled reconnect makes that advice testable instead of guessing.

Verify: The printer stays Ready after one path is restored with upstream queues held, then completes one controlled simple test job. If Error 79 returns before your controlled job, investigate hidden/restored upstream traffic or that connection path rather than blaming the test document.

Fix path #2 — if one file or print workflow triggers 79

If simple jobs work but one PDF, application output, scan/network workflow or driver path repeatedly triggers Error 79, stop treating the printer as universally broken. Preserve the reproducible trigger, then test a different supported output path or driver without changing several variables at once.

Recent HP community cases still show Error 79 tied to particular workflows, including specific PDF printing and network scan behavior. Those reports are useful as examples of why reproduction matters, but they do not prove that every Error 79 has the same cause.

Verify: The suspect workflow reproduces the error while a known-simple job does not.

Fix path #3 — check the exact model's current firmware

If the printer returns to Ready, check the installed firmware version and the current HP-supported update method for the exact model. Use only firmware intended for that model. If Error 79 prevents the printer from reaching the state required by the normal update procedure, do not force that workflow; check whether HP provides a model-specific recovery/update path or whether service escalation is required.

Firmware safety: record the existing version, use the exact model's supported method, keep power stable, and do not interrupt an update. A crash-looping printer is not automatically a candidate for the normal Ready-state update procedure.

Verify: After a supported update, repeat the same controlled test that previously reproduced Error 79.

What about DIMMs and older HP models?

Some older HP documentation distinguishes 79 Service Error from the generic 79 Error and associates it with incompatible DIMM/memory hardware. Do not remove memory based on that older model-specific guidance unless your printer actually has serviceable DIMMs and its own HP documentation calls for that step.

Verify: Before touching memory, confirm the exact model and its model-specific service documentation.

What not to do first

Do not factory-reset before testing whether Error 79 survives an isolated boot.Do not reconnect the network while a known bad queue is still waiting to resend.Do not change firmware, driver, network settings and print queue simultaneously—you lose the evidence.Do not assume every 79 or 79.xx variant has the same hardware cause across HP generations.Do not install firmware intended for another printer model or interrupt a firmware update.Do not call the printer isolated while Wi-Fi, cloud/mobile printing, a print server or another job-delivery path can still reach it.Do not reconnect a path before holding upstream queues; an old job can be redelivered immediately and look like a persistent device failure.Do not force a normal firmware-update workflow when the printer cannot reach the state that procedure requires; use only model-specific recovery/service guidance.Do not keep diagnosing Error 79 if the display changes to a different exact service/error code.

Still getting HP Error 79?

If 79 persists while LAN/USB are disconnected, or it returns after HP's model-specific firmware path, collect evidence before escalating rather than cycling through destructive resets.

Capture before escalation:exact printer modelcomplete Error 79 text/suffixwhether it reaches Ready while isolatedinstalled firmware versionconnection that triggers recurrencefile/application/driver or scan workflow if reproduciblewhether the error began after firmware, driver or network changeswhether Ethernet, USB, Wi-Fi and other applicable job-delivery paths were actually isolatedwhether client/print-server/cloud/mobile queues were held before reconnectingwhether Error 79 returns before or only after the controlled test jobthe exact HP-supported firmware/recovery method available for that modelthe first different error code if the failure changes

Official / primary references

Still stuck? Ask the community

Share the exact model, complete Error 79 text, firmware version, isolated-boot result and the connection or job that reproduces it.

Keep it safe: do not post serial numbers, credentials, private documents, print-job contents or internal network addresses.
Powered by GitHub DiscussionsSign in with GitHub to comment. Reading comments does not require sign-in.

Loading community discussion…