Printer Stuck on "Offline" — Fixes That Actually Work

1. The SNMP Trap — Your Printer Is Actually Online but Windows Thinks It's Not

What's actually happening here is that Windows 10 and 11 have a bug in their SNMP (Simple Network Management Protocol) handling for network printers. When the printer sends a standard SNMP response that Windows doesn't like, the system marks the printer as offline — even though the printer's web interface shows it's connected and ready to print.

I see this constantly with HP OfficeJet Pros and Brother Laser printers on Windows 10 22H2 and Windows 11 23H2. The trigger is often a firmware update on the printer side that changes how it reports status. Windows then decides the printer is 'not responding' and flips the status to offline.

The Fix — Disable SNMP Status Monitoring

1. Open Printers & Scanners in Settings (or Control Panel > Devices and Printers if you're still on that).
2. Right-click your printer and select Printer Properties.
3. Go to the Ports tab.
4. Click Configure Port next to the port that has a checkmark next to your printer's name.
5. In the dialog that opens uncheck SNMP Status Enabled.
6. Click OK, then Apply, then OK. Print a test page.

The reason step 5 works is that Windows uses SNMP to poll the printer every few seconds. When the printer's SNMP response is malformed or slow, Windows assumes the printer is offline. Disabling SNMP monitoring means Windows only checks if the TCP connection is alive — and that almost never fails if the printer is actually on the network.

If you can't modify the port settings (grayed out), you need admin rights on that machine. Run control printers from an admin command prompt.

2. The IP Address Changed — Your Port Points to Nowhere

This is the second most common cause. Your printer had a static IP or was assigned one by DHCP, but something changed — router reboot, printer turned off for a while, or another device grabbed that IP. Windows is still trying to talk to the old IP, and the printer is now at a different one.

You'll notice this when you can ping the printer's IP from a command prompt but get no response, or when the printer's display shows a different IP than what's in the port configuration.

The Fix — Update the Port IP Address

1. Same path: Printer Properties > Ports tab > Configure Port.
2. Write down the IP address shown there.
3. Find your printer's actual IP:
   • Print a network configuration page from the printer's menu (look under Network Settings or Information).
   • Or check the printer's web interface by browsing to its IP from a browser.
4. If the IPs don't match, change the port IP to the correct one.
5. If the printer uses DHCP and you want to prevent this from happening again, assign a static IP from your router's DHCP reservation table, or use the printer's web interface to set a static IP outside your DHCP range (like 192.168.1.200).

Skip trying to 'Add a new port' unless you're comfortable with networking. The existing port is fine — just update the address. Adding a new port often creates a duplicate entry that confuses Windows.

3. Print Spooler Corruption — Everything Looks Fine but Nothing Prints

This one's trickier. The printer shows as 'Ready' or 'Online', you can ping it, the port is correct, SNMP is off — but jobs just sit in the queue with 'Error - Printing'. The cause is almost always a corrupted spooler file left over from a previous failed print job.

What's actually happening is that the spooler service (spoolsv.exe) loads a print job into memory, processes it, and sends it to the driver. If the driver crashes or the job is malformed (common with PDFs from Adobe Reader), the spooler holds onto a corrupted cache file. Every subsequent job hits that corrupted file and fails.

The Fix — Clear the Spooler Cache

1. Open Services.msc (Win+R, type services.msc).
2. Find Print Spooler, right-click and Stop. Leave the window open.
3. Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS.
4. Delete every file in that folder. You'll need admin approval.
5. Go back to Services.msc and Start Print Spooler again.

This clears all pending jobs and removes the corrupted cache. The spooler rebuilds the cache from scratch on the next print job. If you keep seeing corruption, the issue is likely a bad driver — update your printer driver from the manufacturer's site, not Windows Update.

One more thing: if the folder PRINTERS doesn't exist, you're looking at a 32-bit spooler on a 64-bit system. Check C:\Windows\SysWOW64\spool\PRINTERS instead.

Quick-Reference Summary Table

Try these in order. Nine times out of ten, it's the SNMP thing. Don't waste time reinstalling drivers or resetting the printer unless you've checked all three.