Troubleshooting is the process of finding the cause of a problem and applying a suitable solution. A good troubleshooter does not randomly change settings. They identify the problem, test possible causes and confirm that the solution works.
The same basic troubleshooting steps can be used for computers, applications, printers, internet connections and other digital devices.
The Basic Troubleshooting Process
A simple troubleshooting process is:
Identify → Check → Isolate → Fix → Test → Record
Following these steps in order can save time and prevent additional problems.
Step 1: Protect Your Data and Stay Safe
Before troubleshooting, consider whether the device contains important data or presents a physical danger.
Protect your data
- Save open documents.
- Back up important files.
- Record important settings.
- Close applications correctly.
- Avoid deleting unknown files.
Stop immediately if:
- You smell burning.
- You see smoke or sparks.
- Liquid has entered the device.
- A battery is swollen or leaking.
- A storage drive makes unusual clicking sounds.
- Important data may be lost.
- The repair requires electrical knowledge.
Physical or electrical problems should be handled by a qualified technician.
Step 2: Identify the Exact Problem
Describe the problem clearly.
A poor description is:
“The computer is not working.”
A better description is:
“The computer turns on, but the screen remains blank.”
Ask these questions:
- What exactly is not working?
- When did the problem begin?
- Does an error message appear?
- Does the problem happen every time?
- What changed before the problem started?
- Does it affect one application or the whole computer?
- Can the problem be reproduced?
A clear description makes it easier to find the correct cause.
Step 3: Collect Information
Gather useful details before changing anything.
Record:
- Device name and model
- Operating system
- Application name
- Error message or code
- Time when the problem occurred
- Recent updates or installations
- Recently connected hardware
- Actions already attempted
Take a screenshot or photograph of the error message if possible. Do not rely only on memory.
Step 4: Check the Simple Things First
Many problems have simple causes.
Check:
- Is the device switched on?
- Is the power cable connected?
- Is the battery charged?
- Are all cables secure?
- Is Wi-Fi enabled?
- Is airplane mode off?
- Is the volume muted?
- Is the correct input or output selected?
- Is enough storage available?
- Is the correct account being used?
For example, a monitor may appear broken when it is simply switched off or connected to the wrong input.
Step 5: Restart the Affected Device
Restarting reloads the operating system, drivers and background processes. It also clears many temporary errors.
Restart the smallest affected part first:
- Restart the application.
- Restart the connected device.
- Restart the computer.
- Restart the router if the network is affected.
Save your work before restarting.
Sleep mode is not the same as restarting. Sleep keeps the current session in memory, while restarting reloads the system.
Step 6: Determine the Scope
Find out how much of the system is affected.
Ask:
- Does the problem affect one file?
- Does it affect one application?
- Does it affect one user account?
- Does it affect one device?
- Does it affect every device on the network?
Example
If one website does not open but other websites work, the internet connection may be fine.
If every device has no internet, the router or service provider may be responsible.
Determining the scope helps reduce the number of possible causes.
Step 7: Try to Reproduce the Problem
Reproducing means repeating the same action to see whether the problem happens again.
For example:
- Open the application.
- Open the same file.
- Perform the action that caused the error.
- Check whether the error returns.
If the problem happens every time, note the exact steps. If it happens randomly, record what the computer was doing at the time.
Do not repeatedly reproduce a problem if it may damage data or hardware.
Step 8: Check Error Messages
Error messages often explain what went wrong.
When an error appears:
- Read the complete message.
- Record the error code.
- Note which application produced it.
- Take a screenshot.
- Check the software or manufacturer’s official support information.
For example:
- “Storage is full” means space must be freed.
- “Access denied” may indicate a permission problem.
- “No internet connection” suggests a network issue.
- “File format not supported” means a compatible application may be required.
Avoid downloading unknown “repair tools” advertised by pop-ups.
Step 9: Identify Possible Causes
Create a short list of likely causes, starting with the simplest.
For a printer that is not printing, possible causes might include:
- Printer is switched off.
- Paper is missing.
- Wrong printer is selected.
- Print queue is stuck.
- USB or Wi-Fi connection has failed.
- Printer driver has a problem.
- Printer hardware is damaged.
Testing possible causes in a logical order is faster than making random changes.
Step 10: Change One Thing at a Time
Apply one solution and then test the result.
For example:
- Reconnect the cable.
- Test the device.
- Restart the device.
- Test it again.
- Update the driver.
- Test it again.
If several changes are made together, you may not know which one solved the problem. You may also create a new problem.
Step 11: Start with the Least Risky Solution
Use the simplest and safest fix first.
A useful order is:
- Check power, cables and settings.
- Restart the application or device.
- Close unnecessary applications.
- Check storage space.
- Install official updates.
- Run a trusted security scan.
- Repair or reinstall the affected application.
- Use recovery tools.
- Replace hardware only if necessary.
Back up important data before reinstalling software, changing partitions or using system recovery.
Step 12: Check for Recent Changes
Many problems begin after a change.
Possible changes include:
- New application installed
- Operating system updated
- Driver updated
- New hardware connected
- Setting changed
- File deleted
- Browser extension added
If the problem started immediately after a change, safely reversing that change may solve it.
For example, if a browser becomes slow after installing a new extension, disable that extension and test the browser again.
Step 13: Install Official Updates
Updates can fix:
- Software bugs
- Security weaknesses
- Compatibility problems
- Driver errors
- Performance issues
Update software using:
- The operating system’s official update service
- The application’s built-in updater
- The device manufacturer’s official website
Avoid unofficial driver and software download websites.
Updates may temporarily slow down the computer while they are installing. Allow them to finish before judging performance.
Step 14: Test the Solution
After applying a fix, confirm that the original problem is completely solved.
Check:
- Does the device now work normally?
- Does the error message still appear?
- Does the problem return after restarting?
- Are other applications working?
- Can the user complete the original task?
- Was any data or setting affected?
A solution is not complete until it has been tested.
Step 15: Record the Solution
Write down:
- Original problem
- Error message
- Possible cause
- Troubleshooting steps attempted
- Final solution
- Date of repair
This information can save time if the same issue happens again.
IT support teams normally record this information in a support ticket.
Example: Troubleshooting an Internet Problem
Problem
A laptop is connected to Wi-Fi, but websites do not open.
Troubleshooting process
- Test another website.
- Check whether other devices have internet access.
- Turn Wi-Fi off and on.
- Restart the laptop.
- Restart the router.
- Forget the Wi-Fi network and reconnect.
- Check for system or network-driver updates.
- Contact the internet provider if every device is affected.
Result
If other devices work after the router restart but the laptop does not, the problem is probably related to the laptop rather than the internet provider.
Example: Troubleshooting a Frozen Application
Problem
A document application stops responding.
Troubleshooting process
- Wait briefly.
- Try to save the document.
- Close the application.
- Use Task Manager or Force Quit if necessary.
- Reopen the application.
- Check for updates.
- Test another document.
- Repair or reinstall the application if the issue continues.
Testing another document helps determine whether the problem is caused by the application or one damaged file.
Useful Troubleshooting Tools
Task Manager or Activity Monitor
Shows running applications and how much processor, memory, storage or network activity they are using.
Storage Management
Shows which files and applications are using storage space.
Security Scanner
Checks for viruses, spyware and other malware.
Device Manager
Windows Device Manager shows connected hardware and possible driver problems.
System Recovery Tools
Recovery tools can repair startup problems or return system settings to an earlier state.
Use advanced tools carefully and back up important data first.
Common Troubleshooting Mistakes
Avoid these mistakes:
- Making several changes together
- Ignoring error messages
- Deleting unknown system files
- Installing random repair software
- Using unofficial drivers
- Forgetting to back up data
- Repeatedly forcing the computer to shut down
- Opening electrical components
- Assuming the first solution worked without testing
- Continuing when physical damage is present
When Should You Escalate the Problem?
Escalation means asking someone with more knowledge or authority for help.
Escalate when:
- Basic steps do not solve the problem.
- Important data is at risk.
- Physical repair is required.
- The device is under warranty.
- Administrator access is required.
- The issue affects many users.
- The same error repeatedly returns.
- There is smoke, liquid damage or a swollen battery.
- The problem involves an organisation’s network or security controls.
Tell the technician what happened and which solutions you already attempted.
Quick Troubleshooting Checklist
Before asking for help, check:
- Power and cables
- Battery level
- Internet connection
- Device settings
- Error messages
- Available storage
- Recent changes
- Application and system updates
- Whether a restart solves the problem
- Whether the issue affects one or several devices
Conclusion
Basic troubleshooting is a logical process. Begin by identifying the exact problem, checking simple causes and changing one thing at a time.
Always test the result and record the final solution. Back up important files before performing major repairs or recovery operations.
Remember: Identify, check, isolate, fix, test and record.
Frequently Asked Questions
What is the first step in troubleshooting?
The first step is to identify and clearly describe the exact problem.
Why should I change only one thing at a time?
It helps you understand which action solved the problem and prevents confusion.
Why is restarting an important troubleshooting step?
Restarting clears temporary errors and reloads applications, drivers and system processes.
What should I record when an error appears?
Record the complete message, error code, affected application and steps that caused it.
When should I contact a technician?
Contact a technician when important data is at risk, physical repair is required or basic troubleshooting does not solve the problem.
