IT Support in Practice: troubleshooting and ticketing

01

Isolating the problem

In simple words

Imagine two toy cars. One rolls and one does not. You do not guess wildly. You look at what is different between them. IT detectives do the same: they compare what works with what does not.

Before this course: IT Support Basics (course 7.10). You already know the 6-step method (identify, guess, test, plan and fix, verify, document). Here we go deeper into the "guess" and "test" steps.

Key facts

Isolating means making the problem smaller until only one cause is left. Useful questions:

Question	What a "yes" often points to
Does it happen for everyone or one person?	Everyone: something shared (network, server, cloud service). One person: that device or account.
Does it happen on another device with the same account?	Yes: the account or the service. No: the first device.
Does it happen on another account on the same device?	Yes: the device. No: that user's profile or settings.
Did it ever work? When did it stop? What changed?	A recent update, new software, a new password or a moved cable.
Does it happen every time?	Always: a fixed cause. Sometimes: heat, a loose cable, a weak signal or a full disk.

Compare with a known-good. Try the same cable, power outlet, account or app on a machine that works. Swap one part at a time.
Reproduce it. If you can make it happen on demand, you can test whether your fix worked.
Safe Mode narrows things down. Microsoft says Safe Mode starts Windows with a limited set of files and drivers. If a problem does not happen in Safe Mode, default settings and basic drivers are less likely to be the cause.
Do not change several things at once. Write down each change so you can undo it.
Know when to escalate. If the fix needs access you do not have, could risk someone's data, or you have spent your agreed time, hand the ticket to the next level with your notes (see Lesson 6).

Step by step

Write the problem in one sentence: what should happen, and what happens instead.
Ask: one person or everyone? One device or all devices for that person?
Ask: did it ever work, and what changed before it stopped?
Try to reproduce it and note the exact steps.
Compare with a known-good: another device, another account, another cable or another network.
Change one thing, test, and write down the result. Undo it if it did not help.
If the problem disappears in Safe Mode, suspect a driver or startup program (Lesson 3 shows how to check).
Check: you can say in one sentence what is different between "works" and "does not work".

Watch on YouTube

How to troubleshoot (CompTIA A+ 5.1)Professor Messer · YouTube · youtube.com

Videos by other creators on YouTube, for reference. They are not made by or affiliated with The Future Market.

LESSON 01Isolating the problem

LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:10

Voice

Read the video script

[Host] "Two laptops. One prints, one does not. Where do you start?"
[Screen: table with works and does not work columns] "You compare. Same printer, same network, same person. What is different?"
[Text on screen: One thing at a time] "Change one thing, test, write it down. If it does not help, undo it."
[Host] "Problem smaller every step. That is isolating."

Try it now

Pick a small problem you can safely test (for example an app that will not open on one device). Fill in the five isolating questions from the table and write the one-sentence difference between "works" and "does not work".

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "IT Support in Practice: troubleshooting and ticketing" on The Future Market. Lesson 1: "Isolating the problem".

What the lesson teaches:
- Isolating means making the problem smaller until only one cause is left. Useful questions:
- Question - What a "yes" often points to
- Does it happen for everyone or one person? - Everyone: something shared (network, server, cloud service). One person: that device or account.
- Does it happen on another device with the same account? - Yes: the account or the service. No: the first device.
- Does it happen on another account on the same device? - Yes: the device. No: that user's profile or settings.
- Did it ever work? When did it stop? What changed? - A recent update, new software, a new password or a moved cable.
- Does it happen every time? - Always: a fixed cause. Sometimes: heat, a loose cable, a weak signal or a full disk.

The exercise I'm working on:
Pick a small problem you can safely test (for example an app that will not open on one device). Fill in the five isolating questions from the table and write the one-sentence difference between "works" and "does not work".

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.

I'm a parent helping my child (about 8 years old) with a lesson called "Isolating the problem" from the course "IT Support in Practice: troubleshooting and ticketing".

Here's what the lesson says:
Imagine two toy cars. One rolls and one does not. You do not guess wildly. You look at what is different between them. IT detectives do the same: they compare what works with what does not.

The activity:
Pick a small problem you can safely test (for example an app that will not open on one device). Fill in the five isolating questions from the table and write the one-sentence difference between "works" and "does not work".

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.

Open Claude

Sources

Microsoft Support, Start your PC in Safe Mode in Windows: support.microsoft.com/en-us/windows/start-your-pc-in-safe-mode-in-wind

My notes

I learned this

02