Windows

Printer shows offline after a Windows 11 update

A network printer stuck 'offline' on Windows 11 after an update? The real causes — SNMP status polling, a changed printer IP, a spooler glitch — and the fixes: uncheck Use Printer Offline, restart the spooler, disable SNMP on the port, or re-add by IP. Plus what the 2026 print-driver changes mean.

Evidence from the screen

Reference images and diagrams. Click any image to view full resolution.

Diagram of a reachable printer showing offline on Windows 11: first ping its IP to confirm it's a Windows-side issue, then match cause to fix — SNMP status polling (uncheck SNMP Status Enabled on the TCP/IP port), a changed DHCP IP (set a static IP/reservation and re-point or re-add the port by IP), or a spooler/queue glitch (uncheck Use Printer Offline, clear the queue, restart the Print Spooler) — plus the KB5083769 Universal Print regression (remove and re-add the printer) and the 2026 move to the IPP inbox driver. — Original concept diagram (not vendor copyright). A reachable printer that shows offline is almost always SNMP status, a changed IP, or the spooler — match the cause to the fix rather than reinstalling blindly.

Problem summary

I'm here because my network printer shows 'offline' on Windows 11 even though it's powered on and on the network — often right after an update. The usual culprits aren't the printer being broken: SNMP status polling marks a reachable printer offline when it doesn't answer as expected, the printer's IP changed (DHCP) so the port points nowhere, or the print spooler glitched. The fixes match: uncheck 'Use Printer Offline', restart the Print Spooler, disable SNMP on the printer's TCP/IP port, or set a static IP / re-add the printer by IP. There's also a real 2026 backdrop — Windows is moving to IPP class-driver printing and retiring legacy third-party drivers — which this page puts in context. This is the Windows-update angle on the device-agnostic printer says offline but is connected and printer not found on the network.

Operator snapshotEvidence first

First proof

Confirm the printer is powered on, not in error/sleep, and on the same network (ping its IP).

Screen to open

net stop spooler then net start spooler

Expected signal

The printer is reachable on the network.

Stop boundary

Switching a misbehaving old vendor driver to the Windows inbox IPP driver is now the better path.

Layer path

1A reachable printer that shows 'offline' is usually a status-reporting or addressing problem, not a dead printer. The common causes: SNMP status polling on the Standard TCP/IP port marks the printer offline when it doesn't answer as expected, the printer's IP changed (DHCP) so the port points at nothing, or the print spooler glitched. Each has a targeted fix.

2The fixes map to the causes: clear 'Use Printer Offline' and restart the spooler for transient states; disable SNMP on the port to stop false-offline reporting; and set a static IP / DHCP reservation (then re-point or re-add the port by IP) so the address stops moving. Removing and re-adding the printer by IP is the reset when the port itself is broken.

3There's a 2026 backdrop worth knowing but not fearing: Windows is moving to IPP class-driver printing and winding down legacy third-party drivers (no new drivers via Windows Update since Jan 2026; IPP-driver preference from July 2026). For most home printers this means fewer drivers to manage; a specific KB5083769 Universal Print regression (Windows-10-installed printers breaking on Windows 11) is fixed by removing and re-adding the printer.

Runbook

Step-by-step runbook

Start here. Do each check in order, compare it to the expected result, and stop when the evidence explains the failure or the safe stop point applies.

Confirm reachability and clear the obvious flags

Check: Ping the printer's IP, then in its queue clear 'Use Printer Offline' and Cancel all stuck jobs.

Expected result: The printer is reachable and the manual offline flag/jam is gone.

If not: If it's unreachable, fix connectivity/IP first.

Restart the spooler

Check: Run net stop spooler then net start spooler (or Services → Print Spooler → Restart).

Expected result: Stale status clears and the printer shows ready.

If not: If it goes offline again, move to SNMP and IP.

Stop false-offline reporting (SNMP)

Check: Printer properties → Ports → Configure Port → uncheck 'SNMP Status Enabled'.

Expected result: Windows stops marking a reachable printer offline on a failed SNMP poll.

If not: If it still drifts offline after reboots, the IP is changing — fix the address.

Pin the address

Check: Give the printer a static IP or DHCP reservation, then edit the port to that IP or add a new Standard TCP/IP port by IP (re-add the printer if the port is corrupt).

Expected result: The printer keeps a fixed address and stays online across reboots.

If not: If it broke right after an update with a config error, remove and re-add the printer (the KB5083769 Universal Print case).

Run the troubleshooter / re-add as a last step

Check: Run the printer troubleshooter (Get Help). If it still won't come online, remove the printer and add it fresh by IP.

Expected result: A clean re-add clears a corrupt printer/port definition.

If not: If a whole class of printing broke after an update, check release-health and the print-driver guidance.

Safe stop: Switching a misbehaving old vendor driver to the Windows inbox IPP driver is now the better path.

Decision tree

If: 'Use Printer Offline' is checked or jobs are stuck.

Then: A manual offline flag / jammed queue.

Action: Uncheck 'Use Printer Offline', Cancel all jobs, restart the spooler.

If: Printer flips to offline intermittently though it's reachable.

Then: SNMP status polling marking it offline.

Action: Printer properties → Ports → Configure Port → uncheck 'SNMP Status Enabled'.

If: Offline after a reboot / on a schedule.

Then: The printer's DHCP IP changed; the port is stale.

Action: Set a static IP or DHCP reservation; edit the port to the new IP or add a new Standard TCP/IP port by IP.

If: Offline right after a Windows update, with a config error / greyed Print.

Then: The KB5083769 Universal Print regression (printer first installed on Windows 10).

Action: Remove the printer and re-add it via Settings → Printers & scanners.

If: Spooler keeps crashing or the port is corrupt.

Then: Spooler/port corruption.

Action: Clear the queue, restart the spooler, then remove and re-add the printer by IP.

Evidence

Evidence table

Symptom	Evidence to collect	Likely layer	Next action
Printer shows Offline but you can ping it.	Whether 'Use Printer Offline' is set; SNMP status on the port.	Status-reporting (manual flag or SNMP).	Uncheck Use Printer Offline; disable SNMP on the port.
Goes offline after every reboot.	Whether the printer's IP changed; the port's configured IP.	DHCP IP drift.	Set static IP/reservation; re-point or re-add the port by IP.
Offline with a config error / greyed Print after an update.	Whether the printer was first installed on Windows 10; the error code (0x80004005).	KB5083769 Universal Print regression.	Remove and re-add the printer.
Jobs stick, status won't refresh.	Print Spooler service state; queue contents.	Spooler glitch.	Cancel jobs, restart the spooler; re-add the printer if it recurs.

Reference

Commands and settings paths

Restart the Print Spooler

net stop spooler then net start spooler

Where: Elevated Command Prompt (or Services → Print Spooler → Restart)

Expected: Restarts the print subsystem, clearing a stale offline status and a jammed queue.

Failure means: If it goes offline again immediately, the cause is SNMP/IP or a corrupt port, not just the spooler.

Safe next step: Test a print; if it recurs, move to SNMP/IP fixes.

Disable SNMP status on the printer's port

Printer properties → Ports → (the printer's port) → Configure Port → uncheck 'SNMP Status Enabled'

Where: Settings → Printers & scanners → Printer properties (or Control Panel printers)

Expected: Stops Windows from marking a working printer offline when SNMP polling doesn't get the expected reply.

Failure means: If it still goes offline, the IP likely changed — fix the address next.

Safe next step: Apply, then test; combine with a static IP for a durable fix.

Re-point or re-add the printer by IP

Set a static IP/DHCP reservation, then Printer properties → Ports → edit the Standard TCP/IP port to the IP, or Add device → add by IP

Where: On the PC and the router/printer

Expected: Gives the printer a fixed address and points Windows at it, ending the 'offline after reboot' pattern.

Failure means: If the port is corrupt, remove the printer and add a fresh Standard TCP/IP port by IP.

Safe next step: Verify with a test page after re-pointing.

Hardware boundary

Hardware and platform boundary

Change only when

Set a DHCP reservation on the router (or a static IP on the printer) so the address never moves — the durable fix for 'offline after reboot'.
Prefer a Mopria-certified / IPP printer for a new purchase so it uses the Windows inbox class driver and needs no third-party driver.

Evidence that matters

A fixed printer IP (static or DHCP reservation) matching the Windows port.
SNMP status disabled on the port if the printer reports offline falsely.
The Windows inbox IPP driver, or a current vendor driver if the printer needs one.

Evidence that does not matter

Vendor 'all-in-one suite' bloatware — the inbox driver plus the printer's web page usually suffice.
Buying a new printer to fix 'offline' — it's almost always status/IP/spooler, not the hardware.

Avoid

Leaving the printer on DHCP so its IP keeps changing.
Re-installing the printer repeatedly without fixing the SNMP/IP root cause.
Assuming 'offline' means the printer is broken.
Clinging to a legacy third-party driver when the inbox IPP driver works better post-2026.

Related tool/checklist

Use the linked tool when you need a guided plan from your exact symptoms instead of a static checklist.

Device setup troubleshooter

Last reviewed

2026-06-02 · Reviewed by HomeTechOps. Reviewed against Microsoft's troubleshooting-offline-printer page, the 'New printer status is Offline' registry KB, the Standard TCP/IP port (SNMP) doc, the third-party printer-driver end-of-servicing plan, and the Universal Print known-issues page; targets the real causes (SNMP polling, DHCP IP drift, spooler), pins the printer's address as the durable fix, and frames the 2026 IPP/driver transition and the KB5083769 Universal Print regression accurately rather than as a generic 'v4 driver bug'.

Sources/assumptions

Assumes Windows 11 24H2/25H2 with a network (TCP/IP) printer; the offline-troubleshooting steps, SNMP-on-the-port mechanism, spooler restart, and re-add-by-IP path follow Microsoft Support and Microsoft Learn current to mid-2026.
The 2026 print-driver changes (no new third-party drivers to Windows Update from Jan 15 2026; IPP class-driver ranking preference from July 1 2026; updates ending July 1 2027) follow Microsoft's end-of-servicing plan; the July 2026 date is upcoming, not yet in effect as of this review.
The existing KB5083769 Universal Print regression (printers first installed on Windows 10 breaking on Windows 11, error 0x80004005) is a specific documented case, fixed by removing and re-adding the printer — distinct from the generic 'offline' cause.

Source-backed checks

HomeTechOps turns official docs and conservative safety rules into a shorter runbook. These links are the source trail for the page direction.

Microsoft Support: Troubleshooting offline printer problems in WindowsUsed as the canonical consumer page for a printer stuck offline: troubleshooter, power-cycle, clear queue, restart spooler, remove/re-add.Microsoft Learn: New printer status is Offline after deleting a print queueUsed for the PrinterOnLine=0 registry remnant cause and the 'Use Printer Offline' fix.Microsoft Learn: The standard port monitor for TCP/IPUsed for the SNMP status-polling mechanism (port 9100) that marks a reachable printer offline — the reason to disable SNMP on the TCP/IP port or re-point it by IP.Microsoft Learn: End of servicing plan for third-party printer drivers on WindowsUsed for the printer-driver deprecation timeline (Jan 15 2026 no new drivers to Windows Update; July 1 2026 driver ranking prefers the IPP inbox class driver; July 1 2027 updates stop).Microsoft Learn: Universal Print known issuesUsed for the KB5083769+ regression where printers first installed on Windows 10 break on Windows 11 (0x80004005 config error), fixed by removing and re-adding the printer.

Diagnostic rule

1. Check the simplest signal first.
2. Change one thing at a time.
3. Avoid unsafe electrical or data-loss steps.
4. Stop when the evidence says the risk moved.

FAQ

What's the quickest fix for 'offline'?

Make sure the printer is on and on the same network, then in Settings → Bluetooth & devices → Printers & scanners open the printer's print queue and clear 'Use Printer Offline' if it's checked, and Cancel all stuck jobs. Then restart the Print Spooler: in an elevated Command Prompt run `net stop spooler` then `net start spooler` (or Services → Print Spooler → Restart). That clears the most common transient offline state.

Why does a working printer keep going offline?

Often SNMP status polling. Windows' Standard TCP/IP port uses SNMP to read the printer's status, and if the printer doesn't answer as expected the port reports it offline even though it prints fine. Fix: Printer properties → Ports → Configure Port → uncheck 'SNMP Status Enabled.' The other common cause is the printer's IP changed (DHCP) so the port points at nothing — see the next answer.

The printer's IP changed — how do I make it stick?

Give the printer a static IP (on the printer) or a DHCP reservation (on your router) so it stops moving, then point Windows at it: Printer properties → Ports → either edit the Standard TCP/IP port to the new IP, or add a new port by IP and select it. If the port is broken, remove and re-add the printer by IP. A fixed address is what stops the 'offline after every reboot' pattern.

It broke right after an update — is that the Universal Print bug?

Possibly. A documented regression affects printers first installed on Windows 10 then used on Windows 11 after KB5083769: you get a configuration error (0x80004005) and the Print button greys out. The fix is to remove the printer and re-add it via Settings → Printers & scanners. That's a specific case — most 'offline' problems are the SNMP/IP/spooler causes above, not this one.

Do the 2026 printer-driver changes affect me?

Eventually, gently. Microsoft is moving to IPP class-driver printing (no third-party driver needed for Mopria-class printers) and winding down legacy drivers: since Jan 15 2026 no new third-party printer drivers ship via Windows Update, from July 1 2026 Windows prefers the inbox IPP driver, and third-party driver updates end July 1 2027. For most home printers this means fewer drivers to manage, not a sudden break — but if an old vendor driver misbehaves, switching to the Windows inbox driver is now the better path.