A good computer troubleshooting checklist turns a frustrating problem into a series of small, safe steps. Build one around the equipment you use, the symptoms you see, and clear points for stopping or seeking help.
1. Set up the checklist for your workstation
Start with the computer and accessories the checklist is meant to cover. A home desktop with a separate monitor, dock, printer, and router needs different checks from a laptop used on its own. Make a short inventory and include model names or connection types when you know them. Keep serial numbers, passwords, recovery codes, and other sensitive details out of a shared troubleshooting document.
Create the checklist in a format you can reach when the computer is not working. A printed copy, a note on a phone, or a local document on another device can all work. If several people use the same workstation, use plain language and leave space for notes so another person can understand what was tried.
Include these basic fields at the top:
- Device: desktop, laptop, tablet, or other computer
- Operating system and version: record what the system reports, if available
- Connected equipment: monitor, keyboard, mouse, dock, headset, printer, external drive, and network equipment
- Problem began: date, approximate time, and whether anything changed shortly beforehand
- Urgency: whether work is blocked, partly affected, or merely inconvenient
- Checklist owner: the person doing the steps, if useful in a shared setting
Avoid recording account passwords, payment information, or personal files in the checklist. If a repair needs account access, enter credentials only into the normal sign-in screen or the trusted support channel you already use.
2. Describe the symptom before changing anything
A useful checklist begins with what is happening, not a guessed cause. “The computer is broken” is hard to act on; “the laptop powers on, but the built-in display stays black while the power light is on” gives you a starting point. Record the exact message if one appears, and note what you were doing when the issue began.
Use prompts such as:
- What does not work, and what still works?
- Does the issue happen every time or only occasionally?
- Does it affect one application, one accessory, or the whole computer?
- Did it begin after a restart, update, new device, moved cable, or settings change?
- Is the computer unusually hot, noisy, slow, or repeatedly restarting?
- Is there an error message, blinking light, or other visible indicator?
Record observations separately from theories. For example, write “the network icon says disconnected” rather than “the router is broken.” This keeps the checklist open to more than one explanation.
A compact symptom log can help compare attempts:
| Time | What happened | What changed | Result |
|---|---|---|---|
| 9:10 a.m. | External monitor showed no picture | Reseated the video cable | No change |
| 9:18 a.m. | Picture appeared after selecting another input | Monitor input changed | Display works |
Use only the columns you will actually fill in. A checklist should make the process clearer, not create paperwork that gets skipped.
3. Add a safety and data check first
Before troubleshooting, consider whether the computer or accessory may be unsafe to use. Stop and disconnect power if you notice a burning smell, smoke, sparks, liquid inside the device, a swollen battery, a damaged power cord, or unusual heat that does not subside. Do not open a power supply or a battery pack, and do not keep testing equipment that appears damaged. Follow the manufacturer’s safety and service instructions or contact a qualified repair provider.
For a normal software or connection problem, protect your work before making changes. Save open files if possible. If the computer is stable enough, make sure important files have a current backup before trying steps that may alter data, such as resetting the operating system, changing storage settings, or reinstalling software. A sync icon alone does not prove that every file has finished syncing; check the service’s own status or confirm a copy exists somewhere accessible.
Put these questions near the beginning of the checklist:
- Is there any sign of electrical, liquid, battery, or heat damage?
- Are important files saved or backed up before a disruptive step?
- Do I understand what this step will change, and can I undo it?
- Is this a work-managed computer or accessory with support rules I should follow?
If the answer to a safety question is uncertain, stop before opening the device or changing internal components. Manufacturer instructions vary by model, and a procedure suitable for one computer may damage another.
4. Work from simple checks to targeted fixes
Arrange the checklist in stages, starting with low-risk actions that are easy to reverse. Change one thing at a time and record the result. If you change several settings or cables together, you may solve the issue without learning which change mattered—or make it harder to undo an unwanted change.
Check power and physical connections
For a desktop, confirm that the power cable is seated at the computer and outlet, and check whether a power strip or surge protector is switched on. For a laptop, check the charger connection and use the charging equipment specified or approved for that model. USB-C charging depends on the laptop, charger, cable, and port supporting compatible power delivery; the connector shape alone does not establish compatibility.
For a display problem, check that the monitor is powered on, set to the correct input, and connected to the intended video output. A dock or adapter can add another possible point of failure. If practical, bypass it temporarily with a compatible direct connection. Do not force a connector or assume that every port with the same shape supports video.
For a keyboard, mouse, headset, or other accessory, check its power, battery, mute switch, wireless receiver, cable, and selected operating-system input or output. Follow the manufacturer’s instructions for pairing and charging. If the accessory is wireless, check whether it uses Bluetooth or a dedicated receiver; the troubleshooting steps differ.
Check the scope of the problem
Try to determine whether the fault follows one device, one application, or one connection. If available, test a known-good compatible cable or accessory. Alternatively, try the suspect accessory on another compatible device. Avoid changing several devices at once, and do not connect unknown storage media simply to see what happens.
For internet problems, check whether other devices can connect to the same network and whether the computer can reach a different trusted network, if one is available. This helps distinguish a computer-specific issue from a wider network issue, but it does not prove exactly where the fault lies. Restarting a router can interrupt other people’s work or connected equipment; check with other users first and follow the router maker’s instructions.
Restart and check settings
Save work, close applications, and use the operating system’s normal restart option when appropriate. A restart can clear a temporary problem, but it does not repair damaged hardware or explain a recurring fault. Record whether the issue returns and how soon.
Check relevant settings without making broad changes. Examples include the selected display, audio output, keyboard layout, Wi-Fi network, application permissions, or available storage. If you change a setting, write down its original value so you can restore it. Avoid disabling security features or installing unknown “repair” tools as a diagnostic shortcut.
5. Include software and update checks with limits
Software checks belong after you have recorded symptoms and tried basic connections, unless an error message points directly to a specific application or update. Note the application name, version if easy to find, and whether other applications show the same problem. If one application fails while the rest of the computer behaves normally, use that application’s built-in help and support instructions before changing system-wide settings.
Check for operating-system or application updates through the normal settings interface or the publisher’s official source. Updates can fix known issues, but they can also take time, require a restart, or change compatibility with older equipment and software. Before starting an update, save work, connect reliable power where appropriate, and make sure you can wait for it to finish. Do not interrupt an update just because the screen appears unchanged for a short time; follow the device maker’s guidance.
If the problem began immediately after an update or new application, record that timing. Where the system provides a supported way to undo or uninstall the recent change, read its instructions and consider the data and security impact first. Do not download replacement drivers or firmware from random websites. Prefer the computer, accessory, or operating-system manufacturer’s support pages for model-specific files and instructions.
Troubleshooting when the first steps fail
Use the symptom to choose the next branch instead of repeating every step:
- No power: check the approved charger or power cable, outlet, and visible indicators. Stop if there is damage, unusual heat, or a battery concern.
- Power but no picture: check monitor power and input, video cable seating, and compatible ports; if available, try a known-good display connection.
- Slow or frozen system: note whether one application is responsible, save what you can, and check available storage using the operating system’s own tools. Repeated forced shutdowns can lose unsaved work.
- No sound: check mute, volume, selected output, headset connection, and whether the issue affects one application or all sound.
- No network: compare another device on the same network, verify the selected network, and record whether wired and wireless connections behave differently.
These are starting points, not diagnoses. Hardware layouts, recovery features, and menu names vary across manufacturers and operating-system versions. Use the model-specific manual when a step involves internal parts, firmware, reset procedures, or unfamiliar indicators.
6. Make escalation and stopping points explicit
A checklist is more useful when it says when to stop. Set a boundary before attempting invasive or destructive work. Stop and seek manufacturer or trusted technical support if the computer shows physical damage, repeatedly shuts down, cannot safely save important data, or still has the problem after reasonable low-risk checks. Escalate sooner if the computer is managed by an employer, school, or other organization whose support team controls updates, encryption, or device settings.
Avoid opening a device, reseating internal components, changing firmware settings, or reinstalling an operating system unless you have the correct model instructions, understand the risks, and have a reliable backup where needed. Some laptops have sealed components or service procedures that require special tools. A reset or reinstall can remove applications, settings, or files, and recovery options differ by system.
Prepare a short handoff note for support:
- Device make and model, plus operating-system version if available
- The symptom and when it began
- Any exact error text or indicator pattern
- Recent changes that may be relevant
- Steps already tried and the outcome of each
- Whether important files are backed up and whether the issue is urgent
Do not include passwords or private file contents. This record helps the next person avoid repeating steps and gives them enough context to choose a suitable repair path.
7. Keep the checklist current and usable
Review the checklist when you replace a computer, add a dock or monitor, change your network equipment, or notice that a step no longer matches the menus on your system. Remove steps that no longer apply, and add only details that help someone identify the right connection, accessory, or support resource. Keep manufacturer manuals and support links alongside the checklist if they are easy to reach, but make sure the links point to official sources.
For a shared workstation, label cables and ports only when the labels are accurate and do not block ventilation or obscure safety markings. Store spare cables and adapters with their specifications, and keep them separate from damaged equipment. Compatibility depends on the computer’s ports, supported standards, power requirements, and accessory model; test or verify those details before relying on a spare.
A practical checklist is short enough to use during a real problem, but detailed enough to capture what happened. Start with safety, describe the symptom, make one low-risk change at a time, record the result, and stop when the next step could risk data or equipment.