You're sitting at your desk, need to save a report as PDF, hit Print, and get slammed with 'Operation could not be completed (error 0x00000709)'. The printer queue shows nothing. The document just disappears. This happens most often when you're using a PDF printer like Adobe PDF, PDFCreator, or Bullzip on a network share or a redirected printer via Remote Desktop. I've seen it crop up after a Windows update (specifically KB5028166 on Windows 10 22H2) or after someone changes printer permissions on the server.
What's actually causing this
The error 0x00000709 is Windows's way of saying 'I can't find the printer driver or I don't have permission to talk to it'. When you print to PDF on a network, the spooler needs to write a temporary file to the user's temp folder. If that folder is on a network drive or if the permissions got shuffled, the spooler chokes. Another common trigger: the printer driver on the client machine doesn't match what the server expects. I had a client last month whose entire print queue died because someone installed a 64-bit driver on a 32-bit server and vice versa.
Fix 0x00000709 step by step
Step 1: Reset the print spooler
This clears any stuck jobs and bad temp files. Open an admin Command Prompt or PowerShell and run:
net stop spooler
net start spoolerDon't just restart the service from services.msc — the cmd method is faster and avoids the 'access denied' dance if permissions are weird.
Step 2: Check the printer's 'Access this computer from the network' right
This is the one that trips up most people. On the server hosting the shared printer, open secpol.msc → Local Policies → User Rights Assignment. Find Access this computer from the network. Make sure the user or group that's trying to print is in that list. I've seen this get wiped after a security update. If the user isn't there, add them. Apply, then run gpupdate /force on the server.
Step 3: Reinstall the PDF printer driver
On the client machine, remove the PDF printer completely. Go to Settings → Bluetooth & devices → Printers & scanners. Find the PDF printer, click Remove. Then download the latest driver from the manufacturer's site (not Windows Update — it's often outdated). Install it fresh. For Adobe PDF, make sure you're using the 'Adobe PDF' printer, not 'Microsoft Print to PDF' — they're not the same thing and the Microsoft one can flake out on network shares.
Step 4: Clear the driver cache
If step 3 didn't cut it, the spooler's driver cache is probably corrupted. Stop the spooler again. Delete everything in C:\Windows\System32\spool\PRINTERS. Don't worry about the files — they're just orphaned temp jobs. Then restart the spooler. This alone fixed the issue for a client whose PDF printer was hanging after a failed update.
Step 5: Verify the temp folder path
PDF printers write temp files to %TEMP%. If your temp folder is on a network drive (some admins set this up for roaming profiles), the spooler can't write there because of permissions. Open a Command Prompt and type:
echo %TEMP%If it starts with a UNC path (\\server\share), change it. Go to System Properties → Advanced → Environment Variables. Set TEMP and TMP to C:\Windows\Temp or C:\Users\<yourname>\AppData\Local\Temp. Log off and back on.
If it still fails after all that
You've got a deeper issue. Check the Event Viewer under Applications and Services Logs → Microsoft → Windows → PrintService. Look for error 808 or 846. Those point to a driver mismatch between 32-bit and 64-bit client drivers on the print server. On the server, open Print Management (printmanagement.msc), find the shared printer, right-click → Properties → Sharing tab → Additional Drivers. Make sure both x86 and x64 drivers are installed. If one's missing, add it from the manufacturer's driver pack. I've seen this happen after a new PC with a 64-bit OS tries to use a printer that only has 32-bit drivers installed on the server.
One last thing: if you're on Remote Desktop, the PDF printer might not be 'redirected' by default. Check the RDP session settings → Local Resources → Printers. Make sure 'Printers' is checked. I've lost count of how many times I've fixed this just by ticking that box.