DeskPlainRecord the model, connection, selected queue, exact symptom and result of one small test. Use that evidence to choose a guide or contact official support.
“The printer does not work” describes a result but leaves several possible starting points. A helpful troubleshooting note records what you tried, which connection you used and whether a small test behaves differently from the original document. This can save repeated checks when you return to the problem or ask support for help.
Preview and download the fillable printer diagnostic fieldbook, or use the guided printer troubleshooter to choose a next reading path. Neither tool connects to your printer, scans your network or changes a Windows setting. The output is a record you can review yourself.
Write down the setup you can observe
Record the printer model, Windows version if known, connection type and application used to print. If a work computer manages the printer, say so. A shared office queue can behave differently from a printer connected directly by USB or joined to home Wi-Fi.
| Field | Useful note | Leave out |
|---|---|---|
| Device | Model and exact displayed error | Account passwords or recovery codes |
| Connection | USB, home Wi-Fi or managed shared queue | Private network credentials |
| Scope | One file, one app or every test tried | Confidential document contents |
| Timing | When it last worked and what changed | An assumed cause presented as a fact |
For example, “The queue shows Offline over Wi-Fi; a one-page text document also waits” is more useful than “Windows broke the printer.” The first describes observable facts without guessing the cause.
Begin with the device and selected destination
- Check the printer is powered on and read any device-panel message.
- Confirm the application selected the intended printer rather than a PDF destination or an old duplicate queue.
- Note whether the connection is USB, Wi-Fi or shared through another system.
- Check obvious paper or consumable alerts using the manufacturer’s instructions.
Do not unplug a device while it is updating firmware. If a managed printer needs credentials or a queue policy has changed, use your administrator’s support route rather than replacing the setup yourself.
Test one small document
Use a non-confidential one-page file and record what happens. If it succeeds, compare the original file’s application, page size and print settings. If it also fails, check the connection and queue before focusing on page layout.
The offline checklist follows status and connection clues. The queue guide covers cancelling unwanted jobs. Sending many copies while a job is waiting makes the result harder to interpret and can produce a stack of repeated pages when the connection returns.
Classify a page that actually prints
If paper comes out, record whether it is blank, scaled incorrectly, clipped, rotated or printed on the wrong side. These symptoms point to different checks. A size problem is not the same as a missing connection.
- For a template with the wrong physical size, compare Actual size, Fit and the selected paper size.
- For drifting label alignment, use a plain-paper test and note where the error grows.
- For blank pages, compare a known small document and follow the model’s consumable guidance.
- For duplex orientation, test two clearly numbered pages before printing a large document.
Use the relevant guide rather than changing every setting at once. Keep the result of each change in the checklist so you can return to the previous state.
Record a clear stop point
Stop if a device reports a hardware or consumable problem you cannot resolve using its manual, if a work policy prevents a change, or if the next step would remove a setup you cannot restore. Unsupported driver downloads and broad resets are not part of this checklist.
When contacting official support, include the model, connection, exact message, app, scope and small-test result. If a screenshot is useful, remove personal details and document contents first. The checklist is a communication aid, not a replacement for the manufacturer’s diagnosis.
Keep the successful settings
When the problem is resolved, save the final settings and the test that confirmed success. Note the date and app version where relevant. That makes a future recurrence easier to compare and helps avoid treating a different symptom as the same old issue.
Keep these in mind
- Describe what happened before guessing why.
- Test one small file before repeating a large job.
- Keep passwords and confidential document contents out of support notes.
Common questions
Does the guided tool connect to my printer?
No. It uses the answers you select to suggest a reading path. It does not inspect devices or change settings.
Can I use the checklist for a work printer?
Yes, as a record of observations. Follow your organization’s support rules and do not remove a managed queue without permission.
What should I share with support?
The model, connection, exact message, app and a small-test result are useful. Do not include passwords or confidential file contents.
Sources & further help
Prepared with AI assistance from the linked documentation. This is a source-led explanation, not a claim of hands-on testing across every device. Read the editorial policy.