Neill's Vibe — Module 04

01 · the scene

"I just installed it. Why is it 'not recognized'?"

The installer ran. It said success. You type the tool's name to use it — and the terminal flatly denies it exists. Same word that was just installed two minutes ago.

PowerShell — right after installing

PS C:\> node --version
node : The term 'node' is not recognized as the name of a cmdlet,
function, script file, or operable program.
(the installer finished. the file is on disk. and yet.)

Neill51% · the terrain

"This is the one that makes you feel insane. I watched it install. It said done. Then the computer says it's not there. So which is lying — the installer or the terminal?"

Claude49% · the execution

"Neither is lying — and this is a spot where I've sent people in circles. I'll start suggesting reinstalls when 'not recognized' usually means the file is fine and the terminal just doesn't know where to look. The right first move is almost never 'install it again.'"

02 · the why

The terminal doesn't search your whole computer. It checks a short list.

When you type a command, the terminal doesn't hunt every folder on the drive. It looks in a specific, ordered list of folders called PATH. If the tool's folder is on that list, it's found instantly. If it isn't — even though the program is sitting right there on disk — you get not recognized.

≡

PATH

a list of folders

An ordered list of directories the terminal searches when you type a command name. Nothing more.

⌕

The lookup

name → folder

Type node → it walks the PATH list looking for a node program. First hit wins.

↻

The stale window

restart to refresh

An open terminal cached the old PATH. A freshly-installed tool often just needs a new terminal.

Why this saves you hours: roughly half of "I installed it but it doesn't work" is a PATH problem, not a broken install. Knowing PATH exists turns a mystifying failure into a two-second diagnosis: the program is fine, the terminal just can't see its folder. The fix is usually to open a new terminal (so it re-reads PATH) — or add the folder to the list. You almost never need to reinstall.

03 · predict it

Installed two minutes ago. "Not recognized." Why?

The installer finished successfully. You type the tool's name in the same terminal window that was open during install, and it says not recognized. Most likely cause?

Not it. The install succeeded and the file's there. Think about how the terminal finds a program — and why a window opened before the install wouldn't know about the change.

Exactly. The installer added the tool's folder to PATH, but your already-open terminal is still running on the old PATH it read at startup. A new terminal reads the updated list and finds it. "Not recognized" = a can't-find-it problem, not a broken install.

04 · the walkthrough

From "not recognized" to found, in four frames.

close + reopen the terminal

step 1First move, every time: open a fresh terminal so it re-reads PATH. Fixes most cases instantly.

echo $env:Path

step 2Still missing? Print PATH ($env:Path in PowerShell) and check whether the tool's folder is in the list.

find the install folder

step 3Locate where the tool actually installed (e.g. C:\Program Files\nodejs). That's the folder PATH needs.

add folder to PATH

step 4Add that folder to PATH (System env settings), reopen the terminal. Now the name resolves.

05 · prove it · gate

Teach it back to unlock the payoff.

Same rule as every module: answer it right, or it isn't done.

A tool is definitely installed (you can see its folder on disk), but the terminal says not recognized. What does that tell you, and what's the fix?

// one correct answer unlocks Module 04

Not the load-bearing answer. The file is clearly there, so it's not a broken or missing install. Think about the gap between "exists on disk" and "the terminal can find it."

That's it. "Not recognized" is a findability problem, not an existence problem. The program is fine; PATH (or a stale terminal) is the issue. Reopen the terminal, add the folder if you must — reinstalling is the wrong reflex. Module unlocked. ↓

the durable idea

"Not recognized" means can't-find-it, not doesn't-exist. The terminal only searches PATH. Reopen the window first; reinstalling is almost never the fix.

06 · factory payoff

⊘ locked — pass the teach-back to claim this piece of the factory

The PATH diagnosis one-liner.

A copy-paste snippet that answers "is this tool on my PATH, and if so where?" in one command — plus a short checklist that walks "not recognized" from the cheap fix (reopen the terminal) to the real fix (add the folder), so you never reinstall by reflex again.