Printing from Office fails, prints blank, or goes to the wrong printer
Office will not print, prints an empty page, or sends the job somewhere unexpected. Whether other applications can print is the question that splits this in half, and it takes ten seconds to answer.
What you see
"Word cannot print. There is no printer installed" on a machine with printers, pages that come out blank, or jobs arriving at a printer nobody chose. Notepad may print perfectly from the same machine.
What is actually wrong
Office asks Windows for the default printer at startup and again at print time, so anything wrong with the default — including Windows silently changing it — surfaces here first. Beyond that: a stuck spooler queue, a driver that fails only on the richer output Office produces, or a document whose content is genuinely set not to print.
Codes and articles
Start here — find out which fix applies
A script that runs the 6 inspection commands from the write-up below and prints what each one returned. It reads the machine and changes nothing — every command that could write, delete, start or stop is excluded from it by construction. Run this first, then pick the fix its output points at.
Fixes (4)
Pin the default printer and stop Windows moving it
Jobs go somewhere unexpected, or Office claims there is no printer.
See what Windows currently thinks the default is.
Get-CimInstance Win32_Printer | Where-Object Default -eq $true | Select-Object Name, PortName, WorkOfflineCheck whether Windows is managing the default itself.
Get-ItemProperty 'HKCU:\Software\Microsoft\Windows NT\CurrentVersion\Windows' -Name LegacyDefaultPrinterMode -ErrorAction SilentlyContinue"Let Windows manage my default printer" sets the default to whatever was last printed to, including at a different site. This is the answer whenever the default keeps changing on its own, and nothing in Office hints at it.
Turn it off so the default stays where you put it.
Set-ItemProperty 'HKCU:\Software\Microsoft\Windows NT\CurrentVersion\Windows' -Name LegacyDefaultPrinterMode -Type DWord -Value 1Set the correct default explicitly.
(Get-CimInstance Win32_Printer -Filter "Name='Your Printer Name'") | Invoke-CimMethod -MethodName SetDefaultPrinterCheck no printer is stuck in the offline state, which makes Office behave as though it does not exist.
Get-Printer | Select-Object Name, PrinterStatus, @{n='Offline';e={(Get-CimInstance Win32_Printer -Filter "Name='$($_.Name)'").WorkOffline}}Restart Office completely. It reads the default at startup and will not notice a change made while it was open.
Clear the print queue and restart the spooler
Nothing prints from any application, or a job is stuck and will not delete. Note that this discards every queued job on the machine, for every user.
Look at what is queued before clearing it, so you know what will be lost.
Get-Printer | ForEach-Object { Get-PrintJob -PrinterName $_.Name -ErrorAction SilentlyContinue } | Select-Object PrinterName, Id, DocumentName, SubmittedTime, JobStatusStop the spooler.
Stop-Service Spooler -ForceEmpty the spool folder.
Remove-Item "$env:SystemRoot\System32\spool\PRINTERS\*" -Force -ErrorAction SilentlyContinueA job that cannot be rendered sits here and blocks everything behind it, and it cannot be deleted through the print queue window because the spooler has it open. Stopping the service is what releases it.
Start the spooler again.
Start-Service SpoolerReprint. If the same document jams the queue again, the document or its driver is the problem — go to the driver fix below.
Get-Service Spooler | Select-Object StatusIsolate the driver
Office prints blank or garbled while simpler applications are fine.
Print the same document to Microsoft Print to PDF. This separates the document from the printer in one step.
A clean PDF means the document and Office are fine and the fault is the driver or the device. A broken PDF means the document itself is the problem and no amount of driver work will help.
List what driver the printer is using.
Get-Printer | Select-Object Name, DriverName, PortNameTry the alternative driver type. If it is on a PCL driver, add the same printer again using the PostScript driver, or the reverse.
Office generates far richer output than most applications — transparency, gradients, embedded fonts — and a driver with a rendering bug will fail on that and nothing else. Swapping the driver type is quicker than diagnosing the bug and usually resolves it outright.
Update the driver from the manufacturer rather than from Windows Update, which often carries a older or generic version.
Test with the document's graphics simplified — in Word, File → Options → Advanced → Print, tick "Print in background" off and test again.
Check the document is not set to withhold content
One document prints blank or missing elements while others are fine.
In Word, check File → Options → Display → Printing options, and confirm "Print drawings created in Word" and "Print background colours and images" are ticked if the missing content is graphical.
Check whether the text is formatted as hidden. Home → the paragraph mark button shows hidden text on screen, and File → Options → Display controls whether it prints.
In Excel, check the print area has not been set to an empty or wrong range. Page Layout → Print Area → Clear Print Area, then set it again.
A print area saved with the file is the single most common reason an Excel sheet prints blank or prints one stray cell. It is invisible in normal view.
Check for rows, columns or sheets set to hidden, and for objects whose properties have printing turned off — right-click an object → Format → Properties → Print object.
Use Print Preview rather than printing to test. It renders through the same path and saves the paper.
Related faults
Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.