IT Support Engineer Beginner Guide
Hardware and desktop troubleshooting is one of the most important skills for an IT Support Engineer.
The goal is not just to know commands. You should learn a systematic method:
Identify → Check → Test → Find the cause → Fix → Verify → Document
1. Basic Troubleshooting Method
Whenever a user reports a problem, follow this process.
User reports problem ↓ Understand the symptoms ↓ Check simple things first ↓ Identify hardware/software layer ↓ Run diagnostic tests ↓ Find probable cause ↓ Apply fix ↓ Test again ↓ Confirm with user ↓ Document the solution
Example
User:
"My computer is not working."
Don't immediately replace hardware.
Ask/check:
- Is the computer receiving power?
- Are power LEDs on?
- Do you hear fans?
- Is the monitor powered on?
- Is there any beep/error?
- Does BIOS/UEFI appear?
- Does Windows start?
This helps you determine where the failure occurs.
2. Computer Not Turning On 🔌
Symptoms
- No lights
- No fan
- No sound
- Power button does nothing
Troubleshooting
|
Check |
What to do |
|
Power socket |
Test with another device |
|
Power cable |
Check both ends |
|
Power adapter |
Check laptop adapter |
|
Power button |
Try again |
|
Battery |
Connect AC power |
|
PSU |
Check desktop power supply |
|
Motherboard |
Check diagnostic LEDs if available |
Think in layers
Wall socket ↓ Power cable/adapter ↓ PSU ↓ Motherboard ↓ CPU/RAM ↓ Boot process
Important: Don't open a PSU or work inside a powered electrical supply. For hardware replacement, follow proper electrical and manufacturer safety procedures.
3. Computer Turns On but No Display 🖥️
Symptoms
Computer powers on, but monitor says:
No Signal
Check
Monitor power ↓ Monitor input/source ↓ HDMI/DisplayPort cable ↓ Correct video output ↓ GPU/display adapter ↓ RAM ↓ BIOS/UEFI
Common causes
- Loose display cable
- Wrong monitor input
- Bad cable
- Monitor problem
- GPU problem
- RAM not seated correctly
- Hardware failure
Useful test
Connect the monitor to another known-working computer.
If the monitor works there, investigate the original computer.
4. RAM Problems 🧠
RAM problems can cause:
- Random crashes
- Freezes
- Blue screens
- Boot failures
- Application crashes
- No display in some hardware configurations
Basic troubleshooting
- Shut down the computer.
- Disconnect power.
- Follow manufacturer safety instructions.
- Check RAM installation.
- If multiple modules are installed, test systematically according to the motherboard manufacturer's instructions.
- Run a memory diagnostic.
Windows Memory Diagnostic
Press:
Win + R
Run:
mdsched.exe
Then choose the appropriate restart/test option.
5. Hard Disk Failure 💽
A failing HDD can cause:
- Very slow computer
- File corruption
- Windows crashes
- Clicking/unusual mechanical sounds
- Boot problems
- Missing files
Check disk status
PowerShell:
Get-Disk
For volume information:
Get-Volume
You can also check Windows disk errors through:
Event Viewer → Windows Logs → System
Important
If a disk is failing and contains important data:
Prioritize data preservation before repeatedly testing or modifying the disk.
If data is critical, consider professional data recovery rather than experimenting with the failing drive.
6. SSD Problems
SSDs can experience:
- Storage becoming full
- File-system corruption
- Hardware/controller problems
- Firmware-related issues
- Performance degradation
Check available space
PowerShell:
Get-Volume
You can also open:
Settings → System → Storage
Administrator mindset
Don't assume:
"The SSD is bad because Windows is slow."
First investigate:
Storage space ↓ Disk activity ↓ File system ↓ Windows errors ↓ Drive health ↓ Hardware
7. Overheating 🌡️
Symptoms
- Computer becomes very hot
- Fans run loudly
- Performance decreases
- Unexpected shutdown
- System freezes
- Applications crash
Possible causes
- Dust
- Blocked ventilation
- Failed fan
- Poor airflow
- Heavy CPU/GPU workload
- Thermal-management problems
Basic troubleshooting
Check temperature ↓ Check CPU/GPU usage ↓ Check airflow ↓ Check fans ↓ Clean according to manufacturer guidance ↓ Retest
Don't block laptop ventilation with blankets, cushions, or other surfaces that restrict airflow.
8. Keyboard Problems ⌨️
Symptoms
- Some keys don't work
- Keyboard isn't detected
- Wrong characters
- Keyboard randomly disconnects
Troubleshooting
- Check USB/Bluetooth connection.
- Try another USB port.
- Test another keyboard.
- Check keyboard layout.
- Check Device Manager.
- Restart Windows.
- Update/reinstall the appropriate driver if necessary.
Open Device Manager:
devmgmt.msc
9. Mouse Problems 🖱️
Common causes
- Dead battery
- Bad USB connection
- Bluetooth disconnected
- Dirty sensor
- Driver problem
- Hardware failure
Troubleshooting
Check battery ↓ Check connection ↓ Try another USB port ↓ Try another mouse ↓ Check Device Manager
10. Printer Problems 🖨️
Printer problems are extremely common in IT Support.
Common symptoms
- Printer offline
- Cannot print
- Print queue stuck
- Wrong printer selected
- Driver problem
- Network printer unavailable
- Paper/toner problem
Troubleshooting flow
Printer powered on? ↓ Connected? ↓ Correct printer selected? ↓ Printer online? ↓ Print queue? ↓ Printer driver? ↓ Network connectivity? ↓ Print test page
Windows Print Spooler
PowerShell:
Get-Service -Name Spooler
Restart if appropriate:
Restart-Service -Name Spooler
11. USB Problems
Symptoms
- USB device isn't detected
- USB drive disconnects
- Keyboard/mouse doesn't work
- Phone doesn't appear
- USB storage cannot be accessed
Troubleshooting
Try another USB port ↓ Try another cable ↓ Test device on another computer ↓ Check Device Manager ↓ Check Disk Management ↓ Check drivers
Device Manager:
devmgmt.msc
Disk Management:
diskmgmt.msc
12. Monitor Problems
Problem: No Signal
Check:
- Power
- Input source
- HDMI/DP cable
- Cable connection
- GPU
- Display adapter
- Another monitor
Problem: Wrong resolution
Go to:
Settings → System → Display → Display resolution
Problem: Flickering
Possible causes include:
- Cable
- Refresh-rate setting
- Display driver
- Monitor
- GPU
13. Blue Screen of Death — BSOD 💙
A BSOD means Windows encountered a serious system error and stopped to protect the system.
You may see a stop code.
Examples include:
MEMORY_MANAGEMENT IRQL_NOT_LESS_OR_EQUAL CRITICAL_PROCESS_DIED PAGE_FAULT_IN_NONPAGED_AREA
Common causes
- Faulty drivers
- RAM problems
- Hardware failures
- Corrupted system files
- Incompatible software
- Storage problems
Troubleshooting process
Record STOP CODE ↓ Think about recent changes ↓ Check drivers ↓ Check RAM ↓ Check system files ↓ Check disk ↓ Review Event Viewer / crash information ↓ Test
System File Checker
Run Command Prompt as Administrator:
sfc /scannow
DISM
DISM /Online /Cleanup-Image /RestoreHealth
Important: These commands are useful for Windows system-file/component corruption, but they won't repair every hardware or driver problem.
14. Slow Computer 🐌
This is one of the most common IT Support tickets.
Don't immediately say:
"You need more RAM or replace HDD to SSD"
Investigate first.
Step 1 — Task Manager
Ctrl + Shift + Esc
Check:
CPU Memory Disk Network Startup apps Processes
Step 2 — Find the resource-consuming process
PowerShell:
Get-Process
Step 3 — Check storage
Get-Volume
Step 4 — Check startup applications
Task Manager → Startup apps
Step 5 — Check updates/drivers/security
Then test the system again.
15. Windows Not Booting
Possible symptoms:
- Black screen
- Windows logo stuck
- Automatic Repair
- Boot device not found
- Repeated restart
- Recovery screen
Troubleshooting layers (Stop Point)
Power ↓ POST ↓ BIOS/UEFI ↓ Boot device ↓ Windows Boot Manager ↓ Windows kernel ↓ Login screen
The point at which the computer stops gives you an important clue.
Basic questions
- Can you enter BIOS/UEFI?
- Is the SSD/HDD detected?
- Is the correct boot device selected?
- Did a recent update cause the problem?
- Does Windows Recovery Environment start?
16. Application Crashes
Symptoms
An application:
- Freezes
- Closes unexpectedly
- Shows an error
- Won't start
Troubleshooting
Restart application ↓ Restart Windows ↓ Check application update ↓ Check Windows updates ↓ Check Event Viewer ↓ Repair/reset application ↓ Reinstall if necessary
Event Viewer
eventvwr.msc
Look at:
Windows Logs → Application
17. Driver Problems
Drivers are a common cause of Windows problems.
Symptoms
- Device doesn't work
- Device disappears
- BSOD -Blue Sc o dea
- Display problems
- Audio problems
- Network problems
Open:
devmgmt.msc
Look for:
⚠️ Warning icon ❓ Unknown device
Basic process
Identify device ↓ Check driver status ↓ Check manufacturer-supported driver ↓ Update/reinstall/rollback when appropriate ↓ Restart ↓ Test
Avoid downloading random drivers from unknown websites.
18. Windows Update Errors
Symptoms
- Update fails
- Update repeatedly retries
- Error code appears
- Computer gets stuck during update
Basic troubleshooting
- Record the exact error code.
- Restart the computer.
- Check network connectivity.
- Check available storage.
- Check Windows Update status.
- Use Windows' built-in troubleshooting/recovery options where appropriate.
- Search the exact Microsoft error code when deeper research is needed.
Useful PowerShell check
Get-Service -Name wuauserv
This checks the Windows Update service.
19. Missing DLL Files
You may see an error such as:
The program can't start because XYZ.dll is missing.
What is a DLL?
DLL = Dynamic Link Library
Windows applications can use DLL files to provide shared functionality.
Don't do this
Avoid downloading an individual DLL from an unknown "DLL download" website and copying it into system folders.
Better troubleshooting
Identify application ↓ Check exact DLL/error ↓ Repair application ↓ Reinstall application ↓ Run Windows system-file checks
Useful commands:
sfc /scannow
and:
DISM /Online /Cleanup-Image /RestoreHealth
20. Disk Full ⚠️
Symptoms
- Windows becomes slow
- Applications fail
- Updates fail
- Files cannot be saved
- Temporary operations fail
Check storage
PowerShell:
Get-Volume
Or:
Settings → System → Storage
Find what's consuming space
Look at:
Downloads Videos Desktop Recycle Bin Temporary files Application data Old installers Windows update/recovery data
Important
Don't randomly delete files from:
C:\Windows C:\Program Files
System files should only be removed using appropriate Windows tools/procedures.
21. Hardware vs Software Troubleshooting
This distinction is extremely important.
|
Symptom |
Possible Hardware |
Possible Software |
|
No power |
PSU, motherboard |
Rarely |
|
No display |
Monitor, GPU, RAM |
Driver |
|
Slow computer |
HDD/SSD, RAM |
Startup apps, malware, updates |
|
BSOD |
RAM, storage |
Driver/system corruption |
|
No Wi-Fi |
Adapter |
Driver/configuration |
|
No audio |
Sound hardware |
Driver/settings |
|
Printer failure |
Printer/cable |
Driver/spooler |
|
USB failure |
Port/device |
Driver |
|
Boot failure |
SSD/RAM/motherboard |
Boot/Windows corruption |
|
Application crash |
RAM/storage |
Application/Windows |
22. The "Known Good" Method ⭐
One of the most useful IT Support techniques is to compare a problem component with a known-good component.
Example: Keyboard not working
Problem keyboard ↓ Try known-good keyboard ↓ Works? ┌────┴─────┐ YES NO ↓ ↓ Keyboard Computer/ problem USB issue
Example: Monitor nw
Problem monitor ↓ Try known-good monitor ↓ Works? ┌────┴─────┐ YES NO ↓ ↓ Monitor Computer/GPU/ problem cable problem
This can quickly isolate the faulty component.
23. Important Windows Troubleshooting Tools
|
Tool |
Command |
Main Use |
|
Task Manager |
taskmgr |
CPU/RAM/processes |
|
Device Manager |
devmgmt.msc |
Hardware/drivers |
|
Disk Management |
diskmgmt.msc |
Disks/partitions |
|
Event Viewer |
eventvwr.msc |
Error/event logs |
|
Services |
services.msc |
Windows services |
|
System Information |
msinfo32 |
Hardware/system details |
|
DirectX Diagnostic |
dxdiag |
Display/audio diagnostics |
|
Resource Monitor |
resmon |
Detailed resource monitoring |
|
System Configuration |
msconfig |
Startup/boot configuration |
|
Command Prompt |
cmd |
Troubleshooting commands |
|
PowerShell |
powershell |
Administration/automation |
|
Windows Memory Diagnostic |
mdsched.exe |
RAM testing |
24. Important Troubleshooting Commands
System information
systeminfo
Current user
whoami
Computer name
hostname
Network configuration
ipconfig /all
Test network
ping 8.8.8.8
DNS test
nslookup google.com
Running processes
tasklist
Check Windows system files
sfc /scannow
Repair Windows component store
DISM /Online /Cleanup-Image /RestoreHealth
Check disk
chkdsk
For repair operations, understand the options before using them, especially on important systems.
25. Useful PowerShell Commands
Processes
Get-Process
Services
Get-Service
Network adapters
Get-NetAdapter
IP configuration
Get-NetIPConfiguration
Disks
Get-Disk
Partitions
Get-Partition
Volumes
Get-Volume
Computer information
Get-ComputerInfo
26. Practical IT Support Troubleshooting Matrix
|
User Problem |
First Tool/Check |
Next Investigation |
|
PC won't turn on |
Power/cables |
PSU/motherboard |
|
No display |
Monitor/cable |
GPU/RAM |
|
PC very slow |
Task Manager |
Storage/startup/apps |
|
BSOD |
Stop code |
Drivers/RAM/system files |
|
Wi-Fi doesn't work |
Network settings |
Adapter/driver/IP/DNS |
|
No sound |
Sound settings |
Driver/device |
|
Printer won't print |
Printer/queue |
Spooler/driver/network |
|
USB not detected |
Different port |
Device Manager/Disk Management |
|
Windows won't boot |
BIOS/UEFI |
Boot/Recovery/Windows |
|
Application crashes |
Event Viewer |
App repair/reinstall |
|
Update fails |
Error code/storage |
Windows Update troubleshooting |
|
Disk full |
Storage settings |
Large files/temp data |
27. IT Support Troubleshooting Example
Ticket
User: "My Windows laptop is very slow."
Technician workflow
1. Ask questions
When did the problem start? Did anything change recently? Is it slow all the time? Which applications are affected?
2. Check Task Manager
CPU → 20% RAM → 95% Disk → 30%
This suggests memory pressure may be worth investigating.
3. Check applications
Get-Process
4. Check startup applications
Task Manager → Startup apps
5. Check storage
Get-Volume
6. Check updates/security
Make sure there isn't an obvious pending or failing update/security issue.
7. Apply fix
For example, close unnecessary applications or address a problematic startup application.
8. Verify
Ask the user to repeat the task that was previously slow.
9. Document
Problem: Laptop slow Cause: High memory usage from applications Action: Closed unnecessary applications Reduced unnecessary startup items Result: Performance improved
28. Golden Rules for IT Support ⭐
Rule 1 — Start with the simplest explanation
Don't replace a motherboard when the power cable is disconnected.
Rule 2 — Don't guess
Collect evidence.
Rule 3 — Change one thing at a time
Otherwise you won't know which change solved the problem.
Rule 4 — Record error codes
An exact error message is much more useful than:
"Windows is showing some error."
Rule 5 — Test before and after
Before fix → Test After fix → Test again
Rule 6 — Protect user data
Before destructive operations such as formatting or reinstalling Windows, make sure important data is appropriately backed up or otherwise protected.
Rule 7 — Document the solution
Good IT Support isn't only about fixing the problem; it's also about making the solution repeatable.
29. Your IT Support Troubleshooting Roadmap
Computer Hardware ↓ Windows Fundamentals ↓ CMD ↓ PowerShell ↓ Hardware Troubleshooting ↓ Windows Troubleshooting ↓ Networking Troubleshooting ↓ User & Permission Management ↓ Active Directory ↓ Group Policy ↓ Windows Server ↓ Backup & Recovery ↓ PowerShell Automation ↓ IT Support Engineer
⭐ Most Important Skills to Practice
|
Skill |
Priority |
|
Task Manager |
⭐⭐⭐⭐⭐ |
|
Device Manager |
⭐⭐⭐⭐⭐ |
|
Event Viewer |
⭐⭐⭐⭐⭐ |
|
Windows boot troubleshooting |
⭐⭐⭐⭐⭐ |
|
Network troubleshooting |
⭐⭐⭐⭐⭐ |
|
Hardware identification |
⭐⭐⭐⭐⭐ |
|
PowerShell |
⭐⭐⭐⭐⭐ |
|
Disk Management |
⭐⭐⭐⭐ |
|
Services |
⭐⭐⭐⭐ |
|
CMD troubleshooting |
⭐⭐⭐⭐ |
|
Windows Update |
⭐⭐⭐⭐ |
|
Driver troubleshooting |
⭐⭐⭐⭐ |
|
Registry basics |
⭐⭐⭐ |
|
Hardware replacement |
⭐⭐⭐ |
Best practice: Create a small Windows 10/11 lab and intentionally practice safe problems—such as disabling/enabling a non-critical device, stopping a test service, inspecting Event Viewer, checking disk space, and troubleshooting a disconnected network adapter. This gives you real troubleshooting experience instead of only memorizing commands.