Questions: Basic Computer Troubleshooting

Question 1

A friend's computer is running very slowly. They haven't restarted in three weeks. What should your first recommendation be, and why?

Model answer: Restart the computer. After three weeks of continuous use, memory may be fragmented or leaked by long-running processes, background tasks may have accumulated, and pending updates may be waiting. A restart clears RAM, reloads the OS from a clean state, and applies updates — resolving a large category of slowness causes at zero cost.

Slowness from accumulated memory use is extremely common and is immediately addressed by a restart. Before diagnosing hardware issues, software conflicts, or malware, the restart baseline must be established. Skipping this step wastes time on more complex diagnoses.

Question 2

A user sees an error message: 'VCRUNTIME140.dll was not found.' What is the most effective immediate step?

Model answer: Search the exact error message — 'VCRUNTIME140.dll was not found' — in a web browser, ideally in quotes. This error has a well-known cause (missing Visual C++ Redistributable) and a standard solution. Searching the precise text surfaces that solution immediately without needing to diagnose from first principles.

Error messages contain specific, searchable text that has almost certainly been encountered and documented by others. Searching verbatim saves significant time. The next step after finding the solution (download the Visual C++ Redistributable) is standard and safe.

Question 3

You can load websites on your phone (cellular data), but no websites load on your laptop when connected to the same home Wi-Fi. What does this tell you about where the problem is?

Model answer: The internet connection itself works (phone loads sites fine), so the problem is not the ISP or modem. The fact that your laptop fails on Wi-Fi but your phone succeeds on Wi-Fi narrows the problem to your laptop's Wi-Fi connection or network configuration specifically. Next steps: restart the laptop, forget and rejoin the Wi-Fi network, or check for driver issues.

Isolation by substitution: testing the same network with a different device rules out the network itself and points to the device. This is systematic elimination — each test removes a layer of the stack from suspicion.