What is the first step of the troubleshooting process?
Identify the problem.
What is the second step of troubleshooting?
Establish a theory of probable cause.
What comes after testing the theory?
Establish a plan of action and implement the solution.
What is the final step of troubleshooting?
Document findings, actions, and outcomes.
What is the most likely cause of a slow system?
Too many startup applications or insufficient RAM.
What tool can help identify a startup issue?
msconfig or Task Manager’s Startup tab.
If a user cannot access a network share, what should you check first?
Network connectivity and permissions.
What does a ‘NTLDR missing’ error indicate?
Bootloader or boot sector issue on Windows system.
What should you do before removing malware?
Quarantine the infected system.
What is the correct order of malware removal steps?
Identify, Quarantine, Disable Restore, Remediate, Re-enable Restore, Educate user.
What can cause frequent application crashes?
Corrupt files, incompatible updates, or insufficient resources.
What should you check when users report a BSOD?
Hardware issues, driver conflicts, or recent changes.
What’s the best way to verify functionality after a fix?
Test system thoroughly and confirm user satisfaction.
What’s the primary goal of documentation?
Provide reference and accountability for future troubleshooting.
What tool helps roll back driver issues?
Device Manager’s Roll Back Driver feature.
