IT technician helping fix printer queue stuck on Rendering

Joe B.

Reviewed for technical accuracy

Specialities: Windows 10/11 printers, print spooler errors, jobs stuck on “Rendering”, WSD vs Standard TCP/IP ports, network printer drivers

Printer queue stuck on “Rendering” — WSD port issues, spooler, and TCP/IP fixes

Technician avatar Technician
Hi! We can definitely deal with a printer queue that says “Rendering” forever in Windows.

To avoid breaking more jobs or reinstalling everything blindly, I need a quick picture of your setup:
• Windows version (Windows 10, Windows 11, or a Windows Server print server)?
• Printer model and how it’s connected — USB, Ethernet, or Wi-Fi network printer?
• In Devices and Printers or Printers & Scanners, does the printer use a WSD port or a Standard TCP/IP port?
• Do all documents get stuck on “Rendering” in the print queue, or just one application (Word, browser, PDFs)?

Once we know this, I’ll walk you through clearing the stuck print jobs, restarting the Print Spooler service, and then doing the important part: swapping the printer from WSD to a stable TCP/IP port so “Rendering” doesn’t hang forever again.
Customer
It’s a small office. Windows 11 PCs, HP network laser printer on Ethernet. In the Windows printer queue, every job shows “Spooling” and then just sits on “Rendering” forever. Nothing prints until we cancel it. Test page from the printer’s own menu works fine, so it’s clearly a Windows / print queue thing, not a hardware failure.
Technician avatar Technician
That’s a textbook case of the Windows print spooler getting stuck on “Rendering” for a network printer.

What usually happens when the printer queue says “Rendering” forever:
• The printer was auto-installed on a WSD port (Web Services for Devices). Those WSD ports can be flaky and lose track of the printer, especially on busy or changing networks.
• The Print Spooler service has old, half-processed jobs. New print jobs stay in the Rendering state behind a corrupt one and never actually hit the printer.
• The driver type (for example, a generic “Class Driver”) doesn’t play nicely with WSD, so the job never fully renders.

The quick win is: (1) completely clear the stuck print queue, then (2) stop using WSD for this printer and re-create it on a Standard TCP/IP port using the printer’s IP address. That’s usually what makes “Rendering” go away for good.
Customer
I just checked Devices and Printers. Under Printer Properties → Ports, it shows something like WSD-… selected, not a TCP/IP port. There are also a couple of “Copy 1/Copy 2” printers for the same machine. All of them show the same behaviour — job stuck on “Rendering” in the printer queue until we cancel it.
Technician avatar Technician
Perfect, thanks — we’ll treat this as a WSD port plus spooler problem.

Step 1 — Clear any jobs stuck on “Rendering” and reset the Print Spooler
Do this on one affected PC first:
1) In the printer queue window, cancel every job that’s stuck on “Printing” or “Rendering”. If something refuses to cancel, that’s fine — we’ll nuke it via the spooler.
2) Press Win + R, type services.msc, press Enter.
3) In the Services list, find Print Spooler, right-click → Stop.
4) Press Win + R again, paste:
  %WINDIR%\System32\spool\PRINTERS
  and delete all files in that folder (these are the stuck jobs).
5) Go back to Services, right-click Print Spooler → Start.

Now your print queue should be empty and the spooler reset. Send a small one-page test job from Notepad and see if it still gets stuck on “Rendering”.
Customer
I followed that and the queue is empty again. The first test page from Notepad actually printed, but the next document from Word is back to “Spooling” → “Rendering” and then just sits there. So clearing the print spooler temporarily helped, but the Rendering status keeps coming back.
Technician avatar Technician
That’s exactly what we expect when the port type is the root cause — the spooler reset gives you one or two good jobs, then the WSD printer port starts acting up again and jobs sit on “Rendering” forever.

Next step is the important one.
Step 2 — Grab the printer’s IP address
• On the printer’s front panel, print a Network Configuration or Settings page, or view its IP via the menu (often under Network → TCP/IP). It should look like 192.168.x.x.
• Alternatively, open a browser on your PC and try that IP in the address bar — if you see the printer’s web page, you’ve got the right address.

Step 3 — Check and prepare to swap WSD → TCP/IP
• On your PC, go to Settings → Bluetooth & devices → Printers & scanners (or Control Panel → Devices and Printers).
• Click your problem printer → Printer properties → Ports tab.
• Confirm the current port is something like WSD-… — that’s the one we want to move away from.

Next we’ll add a Standard TCP/IP port using that IP address and point your printer at it, which usually fixes the permanent “Rendering” status.
Customer
The printer’s config page shows IP 192.168.1.45 and I can open it in a browser. In Printer Properties → Ports, it’s definitely using a WSD port. How exactly do I switch it to a Standard TCP/IP port without reinstalling everything from scratch?
Technician avatar Technician
Great, that’s exactly what we need.

Step 4 — Add a Standard TCP/IP port and move the printer to it
On that same PC:
1) In Printer properties → Ports, click Add Port….
2) Choose Standard TCP/IP Port → click New Port….
3) In the wizard, enter the printer’s IP (192.168.1.45) as both the Hostname or IP address and port name (it’ll fill in automatically). Click Next and finish the wizard.
4) Back in the Ports list, tick the new Standard TCP/IP port you just created and untick the WSD port.
5) Click Apply, then on the General tab click Print Test Page.

Watch the printer queue as you send that test page. If WSD was the problem, the job should flash through “Spooling/Rendering” very quickly instead of sitting there forever, and the test page should come out almost immediately.
Customer
I added the Standard TCP/IP port, checked it, and printed a test page. This time the job showed “Spooling” for a second, “Printing”, and then disappeared from the queue. The page came out right away. So changing from WSD to TCP/IP fixed it on this PC. We have a few other Windows 11 machines pointing to the same printer via WSD though.
Technician avatar Technician
Nice — that confirms WSD was the main reason your printer queue was stuck on “Rendering”.

Step 5 — Apply the WSD → TCP/IP change everywhere
Small office / peer-to-peer:
• On each PC that prints to this device, repeat the Ports → Add → Standard TCP/IP steps and tick the new TCP/IP port.
• You can also remove duplicate WSD-based “Copy 1/Copy 2” printers to avoid confusion, leaving just the one that uses the TCP/IP port.

If you ever use a print server:
• Make sure the printer on the server uses a Standard TCP/IP port, then share that printer to the clients. They will send jobs to the server, and you’ll only manage ports in one place.

Optional hardening:
• In some printer web interfaces you can disable WSD/WS-Discovery, so Windows stops auto-adding flaky WSD instances that later get stuck on “Rendering”. That leaves the stable TCP/IP port path as the only option.
Customer
Makes sense. On the first PC, TCP/IP plus clearing the queue stopped the “Rendering” problem. If, after switching all of them, someone still gets jobs stuck on Rendering or “Printing” status, would that be more of a driver or spooler problem?
Technician avatar Technician
Good thinking. Once you’re off WSD, persistent “Rendering” or “Printing” stuck in the queue usually points to the driver or a flaky spooler on that specific PC.

Step 6 — Update or change the printer driver
• Download the latest PCL or PS driver for your exact printer model from the manufacturer (avoid old “Class Driver” entries when possible).
• In Printer Properties → Advanced, click New Driver… and point it to the new package.
• Keep “Spool print documents” enabled, but you can untick “Enable Advanced Printing Features” if you see weird job behaviour.

Step 7 — Keep the spooler healthy
• If one machine keeps getting stuck jobs, run the same spooler stop → clear PRINTERS folder → start spooler routine there.
• Avoid pausing the printer queue and letting lots of large jobs build up; that’s when odd “Rendering” issues show up most often.

After a clean driver + TCP/IP port + healthy spooler, a printer queue stuck on Rendering is pretty rare.
Customer
I updated the driver on the main PC and that one is now solid. I’ll roll out the TCP/IP port and driver changes to the rest. For future printers, should we avoid WSD completely so we don’t get “Rendering” loops like this again?
Technician avatar Technician
For most offices: yes, avoiding WSD saves a lot of headaches.

Best practices so the printer queue doesn’t get stuck on “Rendering” again
• When adding a network printer, choose “Add a printer using a TCP/IP address or hostname” instead of letting Windows auto-discover it via WSD.
• Give printers a fixed IP address in your router or on the device itself so TCP/IP ports don’t break when the IP changes.
• Use vendor drivers that are known to work well with your OS, and keep them updated.
• If a queue starts acting weird, don’t keep printing into it — check the port type, clear the spooler, and test before users stack up jobs that all say “Rendering”.

And if you ever get a queue that simply refuses to behave, we can remote-walk through event logs, drivers, and port settings in real time — just open a chat with an expert.
Customer
That explains it really well. On the first PC, clearing the spooler and switching from WSD to a Standard TCP/IP port completely fixed the “Rendering” issue. I’ll copy these steps to the rest of the machines. Thanks for the detailed help!
Technician avatar Technician
Anytime! Quick recap: when the printer queue says “Rendering” forever, first clear the stuck jobs and reset the Print Spooler, then stop using the flaky WSD port. Re-add the printer on a Standard TCP/IP port with a fixed IP and, if needed, update the driver. That combo usually makes jobs fly straight through “Spooling/Rendering” and out of the printer instead of sitting forever in the queue. If you’d like someone to double-check the spooler, ports, and drivers on your network, just start a chat with an expert.

Quick answer: the accepted fix

Accepted fix when the printer queue says “Rendering” forever: cancel all jobs, stop the Print Spooler, delete files in the %WINDIR%\System32\spool\PRINTERS folder, and start the spooler again to clear the queue. Then move the printer off a WSD port and onto a Standard TCP/IP port using the printer’s IP address, and if needed update the driver. Once the printer uses a stable TCP/IP port, jobs should no longer get stuck on “Rendering”.

Why Windows printer queues get stuck on “Rendering”

Most cases where the Windows printer queue is stuck on “Rendering” come down to three things: a flaky WSD printer port, a clogged Print Spooler, or a driver that doesn’t like how the job is being rendered. WSD ports rely on service discovery, so if the printer or network changes, Windows may keep accepting jobs but never complete the “Rendering” step. Old jobs left in the spooler can also block the queue so new documents never move past “Rendering”.

By contrast, a Standard TCP/IP port talks directly to the printer’s IP address. Once you give the printer a stable IP and configure a TCP/IP port, the spooler has a much simpler path: render → send over TCP/IP → done. That’s why swapping WSD → TCP/IP, plus clearing the spooler, fixes so many “Rendering” and “Printing” stuck issues in office networks.

How to test if WSD → TCP/IP actually fixed “Rendering”

After changing the printer from a WSD port to a Standard TCP/IP port, run a few controlled tests. First, send a one-page test from Notepad and watch the printer queue: the job should appear, show “Spooling” for a second, briefly flash “Printing”, and then disappear as the page comes out. There should be no long pause on “Rendering”.

Next, try a couple of different apps — a PDF, a Word document, maybe a web page — and check whether any of them leave jobs stuck on “Rendering” or “Printing”. If all of them pass through cleanly on the TCP/IP port, the WSD port was the problem. If one PC still has jobs hanging in the queue while others are fine, focus on that machine’s driver and spooler service instead of the network printer itself.

Printer queue says “Rendering” — quick troubleshooting tips

Clear the spooler, ditch WSD, and move to a Standard TCP/IP port for long-term stability.

Fast path: cancel stuck jobs, stop the Print Spooler service, delete any files in the spool\PRINTERS folder, and start the spooler again. Then open Printer Properties, check the Ports tab, and swap from a WSD port to a Standard TCP/IP port using the printer’s IP address. Finally, update to a current vendor driver if you’re still using a generic “Class Driver”. That combination stops most queues from sitting on “Rendering” forever and gets documents printing again.

Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your printer model, Windows version, and network setup, please consult a verified expert on Whizz-Tech before making changes.

Getting Started Is Easy

Ask for help, 24/7

Members get round-the-clock access to IT Experts for printer queue stuck on Rendering problems, print spooler errors, WSD vs TCP/IP port setup, and more.

Expert will respond in minutes

We match you with a technician who understands WSD printer ports, Standard TCP/IP ports, and stubborn jobs stuck on “Rendering” so you don’t have to guess.

Save time & money

Skip trial-and-error reinstallations. Fixing printer queue Rendering issues online can get your users printing again without onsite support costs.

FAQ

Why does my printer queue say “Rendering” forever in Windows?

This usually means Windows is having trouble finishing the job in the Print Spooler or sending it over the configured port. A flaky WSD printer port, corrupt jobs left in the spool folder, or an outdated driver can all cause documents to stay on “Rendering” and never actually print.

Is WSD or Standard TCP/IP better for network printers?

WSD ports are convenient for auto-discovery but often less reliable for business use. A Standard TCP/IP port that points directly to the printer’s fixed IP address is usually more stable and greatly reduces “Rendering” and “Printing” stuck problems in Windows printer queues.

How do I clear a print job stuck in the queue?

Cancel the job in the printer queue, then open services.msc, stop the Print Spooler, delete all files in %WINDIR%\System32\spool\PRINTERS, and start the Print Spooler again. This fully clears the queue so new jobs no longer sit behind a stuck one.

When should I reinstall or change the printer driver?

If you’ve already moved from WSD to a Standard TCP/IP port and cleared the spooler but jobs still get stuck on “Rendering”, it’s time to update or change the driver. Install the latest recommended driver from the printer manufacturer and avoid generic “Class Driver” entries when possible.

Sources

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant
5 Tech Support Specialists are online right now.