Week 15: Software Troubleshooting Technician Practical

A symptom is the part the user can see.

A diagnosis is the explanation that survives the evidence.

Those are not the same thing.

A blue screen does not automatically mean bad RAM. A phone that drains its battery quickly is not automatically infected. A browser redirect does not prove the entire operating system is compromised. A service that fails to start does not mean Windows needs to be reinstalled.

This week is where the course stops giving you clean topic boundaries and starts giving you what support work actually looks like: overlapping symptoms.

The system question

What still works, what changed, where does the failure begin, and what is the least destructive test that can separate the strongest explanations?

Use the same evidence path for every platform:

baseline
   ↓
scope
   ↓
recent change
   ↓
last proven-good boundary
   ↓
first failed / uncertain boundary
   ↓
best evidence source
   ↓
strongest theory + alternative
   ↓
controlled correction / containment
   ↓
rollback or recovery
   ↓
verification
   ↓
documentation

How the chapter moves

1. Troubleshoot Windows OS Issues follows startup, services, memory, profiles, storage, time, USB resources, and crash evidence without making reinstall the default answer.
2. Troubleshoot Mobile OS and Application Issues keeps repairs proportional to the scope, especially when one app fails while the rest of the device works.
3. Troubleshoot Mobile Security Issues separates suspicious behavior from ordinary configuration, policy, data-use, and connectivity problems.
4. PC Security Troubleshooting Lab works the security symptoms that overlap with browsers, Windows, files, updates, notifications, and networking.
5. Domain 3 Technician Practical removes the labels and makes you decide which system boundary actually owns the evidence.

One rule for the week

Do not choose the most dramatic explanation.

Choose the explanation that accounts for the most evidence while requiring the fewest unsupported assumptions.

Then test it in a way that can prove you wrong.

That is diagnosis.