Current Windows releases include curl, but an older Windows 10 build may contain an outdated copy. Before replacing anything, check which curl executable your shell is actually running.
- Open Command Prompt or PowerShell and run
curl.exe --version. - Run
where curlin Command Prompt, or the appropriate command-resolution check in PowerShell, to see which executable is found first. - Prefer a supported package manager or the official curl project when you need a newer curl than Windows provides. Keep third-party copies in a clearly managed location instead of overwriting protected Windows system files.
- Open a new terminal and run
curl.exe --versionagain to verify the intended version is now first in PATH.
PowerShell aliases can confuse older instructions
Historically, some PowerShell versions mapped curl to a PowerShell web command. Using curl.exe makes it clear that you intend the curl executable.
Do not replace System32 files manually
Windows servicing can own its bundled curl binary. Overwriting system components creates update and integrity problems; manage a separate current copy instead.
Windows 10 support
Windows 10 ended standard support in 2025. Updating one command-line utility does not make the underlying OS supported.
Scripts can depend on behavior introduced in a particular curl version. After updating, test the actual script or API call and review TLS/certificate behavior rather than treating a newer version number alone as proof that the problem is fixed.
Kermit Matthews is a freelance writer based in Philadelphia, Pennsylvania with more than a decade of experience writing technology guides. He has a Bachelor’s and Master’s degree in Computer Science and has spent much of his professional career in IT management.
He specializes in writing content about iPhones, Android devices, Microsoft Office, and many other popular applications and devices.