Fix 0XC00000D1 Printer Redirector Paused Error

Cause 1: Redirector Cache Stuck — Most Common Fix

When you see STATUS_REDIRECTOR_PAUSED (0XC00000D1), it almost always means the redirector component—the part of Windows that sends print jobs or disk access across the network—got hung up. This happens a lot on Windows 10 and 11 machines after a sleep/resume cycle or when a network printer goes offline mid-job. The redirector caches recent connections, and sometimes that cache gets corrupted or stuck.

The quickest fix is to flush the redirector cache directly using the net use command. Here's what to do:

Press Windows Key + R, type cmd, and press Ctrl+Shift+Enter to run Command Prompt as Administrator. You'll see a User Account Control prompt—click Yes.
In the black window, type this exactly and press Enter:
```
net use * /delete
```
After you press Enter, you'll see a list of all network drives and printers being disconnected. It'll ask for confirmation for each one. Type Y and press Enter for each prompt, or just type Y once and it'll handle the rest.
Now type this command and press Enter to clear the print queue cache too:
```
net stop spooler && net start spooler
```
You'll see a message that the Print Spooler service is stopping, then starting again. Wait for the "The Print Spooler service was started successfully" message.
Close Command Prompt and try printing again. Your printer should work now.

This worked for me nine times out of ten when I was on the help desk. If it didn't, move to the next cause.

Cause 2: Workstation Service Needs Restart — Quick Second Fix

The Workstation service (named LanmanWorkstation) is what actually runs the redirector. If flushing the cache didn't help, this service likely needs a full restart. Sometimes it gets stuck in a paused state.

Open an administrator Command Prompt again (same as above: Win+R, cmd, Ctrl+Shift+Enter).
Run these two commands one at a time. Let each finish before typing the next:
```
net stop workstation
```
```
net start workstation
```
When you stop the Workstation service, you'll see a warning that some network connections will be lost. That's fine—they'll reconnect when you start it again. After starting it, you should see "The Workstation service was started successfully."
If you get an error about dependencies, you can restart the service the safe way using Service Manager instead. Do this:
a. Press Windows Key + R, type services.msc, press Enter.
b. Scroll down to Workstation. Right-click it and choose Restart. If "Restart" is grayed out, click Stop, wait a few seconds, then click Start.
You'll see the status change from "Running" to "Stopped" and back to "Running" again. That's normal.
Close Services window and try your print job again.

I've seen this fix stubborn cases that survived reboots. The redirector service remembers its paused state sometimes, and a manual restart clears that.

Cause 3: SMB Redirector Conflicts (Less Common, but Real)

If you're still stuck, the issue might be in the SMB (Server Message Block) redirector itself. This is more common on Windows 10/11 systems that connect to older network printers or shared drives on Windows 7 or Server 2008 R2 boxes. The SMB redirector can get paused when it can't negotiate a proper protocol version.

Here's how to check and fix it:

Open Control Panel (type control in the Start menu).
Click Programs > Turn Windows features on or off. If you don't see "Programs," switch the view to Large icons first.
Scroll down to SMB 1.0/CIFS File Sharing Support. Expand it by clicking the +.
Make sure SMB 1.0/CIFS Client is checked. If it's not, check the box. If it's already checked, uncheck it and let Windows apply the change, then restart and come back to check it again.
Windows will prompt you to restart. Do it. After the restart, the SMB client will be cleanly reinstalled.
After the restart, test your printer again.

This is the nuclear option—only use it if the first two fixes didn't work. SMB 1.0 is old and less secure, but some legacy devices need it. If you uncheck and recheck it, you're resetting the binding. That usually clears the paused state.

Quick-Reference Summary Table

Cause	Fix	Expected Outcome
Redirector cache stuck	Run `net use * /delete` then restart Print Spooler	All network connections cleared; printer works immediately
Workstation service paused	Restart Workstation service via `net stop/start workstation` or Services.msc	Service returns to "Running" state; print job goes through
SMB redirector conflict	Toggle SMB 1.0 Client in Windows Features off/on (or on/off/on)	SMB redirector resets; printer connects after reboot

That's it. In nearly every case, one of those three steps kills the 0XC00000D1 error. I'd start with Cause 1, then Cause 2, then Cause 3. If you've tried all three and it still fails, you're likely dealing with a corrupted OS file or a failing NIC driver—run sfc /scannow from an admin command prompt to check for system file issues.