Fix ERROR_PRINT_CANCELLED (0X0000003F) on Windows 10/11

I know how frustrating it is when you hit Print, wait, and then get slapped with ERROR_PRINT_CANCELLED (0X0000003F) – the message says your file was deleted. It isn't. The print spooler just got confused. Here's how to fix it, and I'll explain why it works after.

The Fix: Clear the Print Queue and Restart the Spooler

1. Open Services. Press Windows Key + R, type services.msc, and hit Enter. You'll see a list of all Windows services.
2. Stop the Print Spooler. Scroll down to Print Spooler. Right-click it and select Stop. Wait a few seconds – the Status column should go blank.
3. Open the spool folder. Press Windows Key + R again, type C:\Windows\System32\spool\PRINTERS, and hit Enter. This folder holds every pending print job. Windows might ask for permission – click Yes.
4. Delete everything inside. Press Ctrl + A to select all files, then press Delete. You'll see .SHD and .SPL files – those are your stuck print jobs. Empty the Recycle Bin afterward.
5. Start the Print Spooler again. Go back to the Services window, right-click Print Spooler, and select Start. The Status should change to Running.
6. Try printing again. Open any document, print a test page. The error should be gone.

After you do this, you should see the print queue empty in Devices and Printers. If you check the queue before step 5, it'll still show cancelled jobs – that's normal. Once the spooler restarts, the old jobs are gone.

Why This Works

Windows keeps print jobs as temporary files in that PRINTERS folder. When a job gets cancelled – maybe you clicked Cancel in the queue, or a driver timed out – the spooler marks it as deleted. But sometimes the file stays behind. The spooler sees that leftover file and thinks, "This job was cancelled, so I'm not printing it." Then every new job you add gets the same 0X0000003F error because the spooler can't start fresh.

By stopping the spooler, deleting those orphaned files, and restarting, you force the spooler to rebuild its state from scratch. No leftover garbage, no error.

Less Common Variations

Variation 1: The Spooler Won't Start

If after step 5 the spooler starts then stops immediately, or you get an error like "The print spooler service failed to start", you might have a corrupt spooler registry key. The fix is to delete the registry entry for the old printer and re-add it.

1. Press Windows Key + R, type regedit, hit Enter.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers
3. Right-click your printer model name, select Delete.
4. Close regedit, restart your PC.
5. Open Devices and Printers, Add Printer, let Windows detect it again.

I've seen this happen most often with HP LaserJet and Canon MF series printers after a failed firmware update. Deleting the registry entry and re-adding the printer fixes it every time.

Variation 2: The Error Shows Only for Network Printers

If the error only happens on a shared printer from another PC, the problem is likely on the host PC. Run the same fix (Stop spooler, delete files, restart) on the computer that actually shares the printer. The client machines just forward jobs – the server spooler is the one that got confused.

One real scenario: an office with a Brother HL-L2370DW shared from a Windows 10 PC. Users on Windows 11 got 0X0000003F randomly. The host PC had a huge backlog of old print jobs from a failed batch print. Clearing the host's PRINTERS folder fixed it for everyone.

Variation 3: The Error Returns After Every Print

This points to a corrupt printer driver. The driver is crashing or sending malformed data, and Windows interprets it as a cancelled job. Uninstall the printer completely and install a fresh driver from the manufacturer's website.

1. Open Devices and Printers.
2. Right-click your printer, select Remove Device.
3. Open Control Panel > Programs and Features.
4. Uninstall any printer-related software (like HP Smart or Canon IJ Network).
5. Restart your PC.
6. Download the latest driver from the manufacturer's site – not from Windows Update.
7. Run the installer, follow the prompts.

Skip the driver Windows offers automatically – it's often stripped down and missing core files. The real driver from HP or Canon includes the full spooler support. I've seen this fix an issue where the error popped every time someone tried to print a PDF from Adobe Reader.

Prevention

Two things will keep this from coming back.

First, don't spam Cancel. When a print job hangs, give it 10-15 seconds before cancelling. Rapid cancelling creates orphaned files. If a job seems stuck, restart the spooler instead of hitting Cancel ten times.

Second, update your printer driver once a quarter. Manufacturers fix bugs that cause spooler errors. Check for updates every three months. I set a calendar reminder – takes two minutes.

Third, avoid using the printer while it's processing a job. Turning the printer off or pulling the network cable mid-print can leave incomplete SPL files. Always wait for the job to finish or cancel it from the queue before powering down.

That's it. The fix is quick, the prevention is easier than you think. You won't see 0X0000003F again if you follow these steps.