Check What Computer You Have

Identify the machine model, operating system, CPU, and memory safely before you troubleshoot or buy upgrades.

Task guide

Check What Computer You Have

Use this when you need a calm first inventory of the computer in front of you.

Many beginner mistakes start with acting on the wrong machine assumptions. A safe inventory makes later decisions more realistic.

Computer and Hardware Fundamentals 15 min both
Safe first move Stay with read-only system information tools. Do not install tools just to inspect the basics.
Use this when

Use this when you need a calm first inventory of the computer in front of you.

Goal

Build a safe first inventory of the computer before you do anything else.

Safe sequence

  1. identify the operating system and machine model
  2. identify the CPU
  3. identify the memory size
  4. write down what you found in plain words

Windows notes

  • Use Get-ComputerInfo, systeminfo, or system information views first.
  • Keep the goal small: identity before action.

Linux notes

  • Use hostnamectl, lscpu, and free -h for a safe first pass.
  • Stop after you can describe the machine clearly.

Move on when

  • you can name the machine in plain language
  • you can separate CPU, memory, and storage correctly
  • you know the machine better than when you started
Before you start
  • Stay with read-only system information tools.
  • Capture the model, CPU, and memory before searching for fixes.
  • Do not guess based on the sticker or the screen size alone.
Verify with
  • You can name the machine model or family.
  • You can identify the operating system.
  • You can identify the CPU and memory size.
Avoid these mistakes
  • Do not install tools just to inspect the basics.
  • Do not change firmware, drivers, or updates during this check.
  • Do not confuse storage size with memory size.
Move on when
  • You can inspect the machine safely on Windows or Linux.
  • You can identify the core specs without outside help.
  • You can explain why the inventory came before troubleshooting.
Reflect before you leave
  • Which detail changed your understanding of the machine most?
  • What assumption did this inspection correct?

Review this task again in about 1, 7, 21 days.

What to do next

Best next step Learning

Open the lesson path when you want the full explanation behind the task.

Open now