I have had to on multiple occasions, maybe we just use it differently

Many Windows administrative, automation, and remote management tasks require Command Prompt or PowerShell because they cannot be efficiently or practically executed via the GUI.

1. Tasks that involve repetitive or bulk operations often require CMD or PowerShell. For example: Renaming thousands of files simultaneously is impractical through File Explorer but can be done easily with Rename-Item in PowerShell

2. Batch file automation using .bat scripts allows automated workflows like clearing temporary files, launching multiple apps, backing up directories, and switching system settings like dark/light mode

3. Scheduled tasks and automatic scripts are better created with command-line scripts, providing repeatable precision versus manual GUI actions

4. Accessing and manipulating Windows services: Use Get-Service and Stop-Service in PowerShell to check or stop services on local or remote machines

5. Managing user accounts and permissions: Commands like net user or whoami /groups provide instant information on users or their groups, which may otherwise require multiple GUI interactions

6. Registry, Group Policy, and WMI tasks: Most registry edits, group policy refreshes (gpupdate /force), and WMI queries are accessible through PowerShell but lack straightforward GUI counterparts

7. System auditing and repair: Commands like sfc /scannow and DISM /RestoreHealth repair system files or images without needing GUI-based troubleshooting tools

8. Managing remote computers: Tools like shutdown /m \computername or PowerShell cmdlets enable shutdowns, restarts, or status checks remotely where GUI Remote Desktop may be impractical or unavailable

9. Collecting diagnostics across multiple endpoints: CMD and PowerShell allow executing scripts across multiple machines unlike GUI tools, which must be operated individually

10. Searching, filtering, and processing files: Commands like Get-ChildItem, Where-Object, and Select-Object enable precise filtering, data extraction, and file management far beyond what the GUI allows

11. Clipboard automation: Using Get-Clipboard and Set-Clipboard for large or structured data transfer without manual selection

12. Reading log data: Extracting and analyzing system or application logs is faster via wevtutil than navigating Event Viewer

13. DNS, IP configuration, and connectivity tests: Commands like ipconfig /all, ping, tracert, Test-NetConnection, and netstat provide immediate network diagnostics that either lack GUI equivalents or are slower to perform