30 Windows Commands you CAN’T live without
Based on NetworkChuck's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Enable “Run as administrator by default” on the Command Prompt shortcut to avoid repeated elevation prompts.
Briefing
Windows power users can squeeze far more out of the command line than basic “dir” and “ipconfig.” The standout theme is that a handful of built-in Windows commands can turn Command Prompt (and the newer Windows Terminal) into a control panel for privacy, networking, system management, and even everyday utilities—without leaving the terminal.
The privacy and security tricks start immediately. Command Prompt can be forced to run with elevated permissions by default: right-click the shortcut’s file location, open Properties → Advanced, and enable “Run as administrator by default.” From there, the transcript demonstrates a “secret photo” workflow using standard Windows tools. Files can be zipped, then hidden inside an image via a binary copy operation (copy /b image + zip → new image). The result looks like a normal photo to anyone else, while the original data sits inside it. For stronger protection, the built-in Cipher utility can encrypt every file in a folder (cipher /e <folder>), so only the user with the right keys can open the contents.
It also shows how to make folders effectively vanish from view using attribute changes. A folder can be hidden by applying attributes (attrib +h +s +r <folder>), and restored by removing those attributes (switching + to -). For networking, the transcript pivots to Wi‑Fi forensics: netsh wlan show profile reveals every wireless network previously connected, and specifying a particular SSID plus key=clear exposes the saved password in plain text. For convenience, the command can be redirected into a text file (netsh ... > wifi passwords.txt) and wrapped into a batch file so the same dump can be run later with a single command.
Beyond privacy and Wi‑Fi, the transcript highlights practical system and workflow commands. systeminfo provides a quick snapshot of machine details. Secure file transfer is done with secure copy (sftp/scp-style syntax is shown as “s sep” in the transcript), and Explorer can be launched from the command line in both directions—typing cmd into the Explorer address bar to open a terminal “at” a folder, or typing explorer . from Command Prompt to jump back into the current directory.
A pair of commands makes the file system feel more flexible: SUBST maps a folder to a drive letter (subst S: "<path>"), and subst /d removes the mapping. For customization, color changes (color <background><text>) and prompt styling (prompt $G with optional title changes via title <name>) let users tailor the terminal’s look.
The transcript then leans heavily on curl as a Swiss Army knife. curl can fetch weather, expand shortened URLs, check website status codes, retrieve public IP, generate QR codes, and query APIs for “latest video” or “latest tweet” style results. It even demonstrates using curl to support ChatGPT-style Q&A from the command line (via a long curl request), plus a dictionary/word-of-the-day lookup using curl to a dictionary site.
Finally, the transcript argues for moving beyond classic Command Prompt by switching to Windows Terminal (installable on Windows 10). Windows Terminal adds tabs, drag-and-drop file selection for commands like secure copy, “shift-right-click” to open a terminal in a folder, and built-in help plus command-specific usage via “/?”—and it closes by recommending PowerShell for deeper scripting power, while still keeping Command Prompt available for familiar tasks.
Cornell Notes
The core takeaway is that Windows’ built-in command-line tools can do far more than basic navigation: they can protect files, expose saved Wi‑Fi credentials, automate workflows, customize the terminal, and fetch online data—all from the same interface. The transcript demonstrates privacy tactics using zip-in-image hiding (copy /b), folder encryption (cipher /e), and attribute-based hiding (attrib +h +s +r). It also shows how netsh wlan show profile can list every saved network and, with key=clear, reveal saved passwords in plain text, then how to save those results to a text file or batch script. For productivity, it covers systeminfo, SUBST drive mapping, and using Explorer and terminals together. It ends by recommending Windows Terminal’s tabs and PowerShell for deeper capabilities.
How can a user make Command Prompt always start with administrator privileges?
What are the three main “hide and protect” techniques shown for files and folders?
How does netsh reveal saved Wi‑Fi passwords, and how can the output be saved for later?
Which commands help with system info, remote copying, and quick folder-to-terminal workflows?
What does SUBST do, and how is it undone?
Why switch from Command Prompt to Windows Terminal, and what practical features are highlighted?
Review Questions
- Which combination of commands would you use to (1) hide a folder from normal view and (2) later restore it?
- What netsh command sequence would you run to list saved Wi‑Fi networks and then reveal a specific network’s password?
- How does SUBST change how folders appear in Explorer, and what command removes the mapping?
Key Points
- 1
Enable “Run as administrator by default” on the Command Prompt shortcut to avoid repeated elevation prompts.
- 2
Hide data by embedding a zip inside an image using a binary copy approach (copy /b), then encrypt the folder with cipher /e for stronger protection.
- 3
Make folders disappear using attrib +h +s +r and restore them by removing those attributes (switching + to -).
- 4
Use netsh wlan show profile to enumerate saved Wi‑Fi networks, and netsh wlan show profile name=<SSID> key=clear to display saved passwords in plain text.
- 5
Save command output for later by redirecting to a file and wrap repeatable one-liners into batch scripts (e.g., wifi.bat).
- 6
Speed up workflow by launching terminals from Explorer (cmd in the address bar) and opening the current directory from the terminal (explorer .).
- 7
Adopt Windows Terminal for tabs, drag-and-drop file paths, and easier command discovery, then consider PowerShell for deeper automation.