Windows Paths, File Extensions, and Hidden Files

A Windows path is the exact route to a file or folder. Learn to read drive letters and backslash-separated components, distinguish full from relative paths, show file extensions, and reveal hidden items only when needed.

File Explorer’s friendly labels are useful, but a compiler, terminal, script, or submission system uses an exact location and filename.

Read a Windows path component by component

C:\Users\Amina\College\2026-Fall\CS101\project\README.md

• C: identifies a drive.
• \ separates path components.
• Users\Amina identifies a user profile folder.
• the remaining folders narrow the location;
• README.md is the filename; and
• .md is its extension.

Microsoft’s Windows path documentation defines backslashes as component separators and explains drive and UNC path forms.

Do not assume every computer uses C: for every file. External drives and partitions can have other letters. Network paths can begin with a UNC form such as:

\\server\share\folder\file.txt

Use only network shares you are authorized to access.

Distinguish full and relative paths

A full path identifies the route from a drive or share:

C:\Users\Amina\College\CS101\notes.txt

A relative path depends on the current directory:

notes.txt

If the current directory is C:\Users\Amina\College\CS101, both can identify the same file. In another directory, notes.txt identifies something else or nothing.

.. commonly refers to the parent directory:

..\shared\rubric.pdf

Before a command changes a relative path, record the current directory and resolve the intended target.

A subtle Windows form such as C:temp.txt lacks the backslash after the colon. Microsoft documents it as relative to the current directory on drive C, not the same as C:\temp.txt. Prefer clear full paths when ambiguity matters.

Do not assume the visible user folder

Documents, Desktop, or other known folders may be redirected by OneDrive or organizational policy. A File Explorer label does not prove the physical path.

Use Copy as path, file properties, the address bar, or an appropriate terminal command to inspect the actual location. Record whether the file is:

• local only;
• synchronized;
• in a work/school tenant;
• on a network share; or
• available offline.

This article identifies paths; a separate backup plan must determine protection.

Show file extensions

Windows can hide known extensions in File Explorer. Microsoft’s current extension guide uses View → Show → File name extensions in File Explorer.

Keep extensions visible while learning. They help distinguish:

report.docx
report.pdf
report.py
report.py.txt

Renaming report.txt to report.pdf changes the filename, not the file’s content. Conversion requires software that actually creates the target format.

An extension suggests intended type and associated application. It does not prove that a downloaded file is trustworthy.

Show hidden items carefully

In current Windows 11 File Explorer, Microsoft documents View → Show → Hidden items. Hidden status controls ordinary display; it is not encryption, access control, or evidence that a file is unimportant.

Show hidden items when course or official troubleshooting instructions require them. Do not edit or delete a hidden file merely because it becomes visible. System and application folders may contain essential state.

For practice, use a disposable folder and a harmless file whose hidden attribute you intentionally set through documented instructions. Do not practice in Windows, Program Files, or an application data folder.

Complete a two-view exercise

Create a practice folder through File Explorer:

College-Path-Practice

Inside it, create report.txt containing:

Windows path practice

Then:

1. enable file-name extensions;
2. confirm the visible name is report.txt;
3. copy or record its full path;
4. open Windows Terminal or PowerShell;
5. navigate to the practice folder using documented commands;
6. inspect the current directory;
7. list the file;
8. display its content; and
9. compare the terminal path with File Explorer.

Expected evidence:

• both views identify the same full path;
• the extension is visible;
• report.txt works as a relative path only from the practice folder; and
• no system file is changed.

Exact PowerShell commands belong in the next article. Use built-in help or course instructions rather than an unfamiliar copied command.

Diagnose common path mistakes

Wrong current directory

The file exists, but a relative path is evaluated elsewhere. Inspect the current directory before moving files or reinstalling software.

Missing quotes

Paths containing spaces may need shell-specific quoting. Learn the active shell’s rules; do not copy Bash quoting blindly into PowerShell.

Hidden extension

A file appears as program.py but is actually program.py.txt. Show extensions and inspect properties.

Cloud or institutional redirection

The visible Documents folder resolves into OneDrive or an organizational location. Inspect the full path and synchronization status.

Drive mismatch

Instructions assume C: while the project is on another drive. Record the actual drive and current location.

Common mistakes

• Treating a relative path as universal. Record the current directory.
• Omitting the backslash after a drive letter. Understand C: versus C:\.
• Keeping extensions hidden. Show the complete filename.
• Renaming to convert a file. Use a real conversion process.
• Treating hidden as protected or disposable. It is a display attribute.
• Assuming Documents is always local. Inspect the resolved path.
• Editing system files during practice. Use a disposable folder.

Do this now

Complete the two-view exercise. Record the full path, its components, the relative filename, extension, drive, and whether the location is synchronized.

Log what you learned

Record only:

• Result: What did the action produce?
• Evidence: What observation, test, or source supports that result?
• Next action or unresolved question: What should happen next?

Next, use these locations in Windows Terminal and PowerShell for complete beginners.