Go
Also called golang, go sdk
Google's Go toolchain. The Windows SDK puts go.exe under Program Files\Go. It is not the Rust compiler.
What you need to know
go.exe in Program Files\Go is the SDK. rustc.exe is Rust.
The official Windows Go MSI puts go.exe under Program Files\Go. Rust uses rustup and rustc.exe. CMake is a build-file generator, not this compiler.
- What is it?
- Google Go toolchain
- Same as Rust?
- No. Different language
- Typical path?
- Program Files\Go\bin\go.exe
What is Go?
Go is the language and toolchain. go.exe is the SDK driver. It is not Rust, not gcc, and not a Windows inbox compiler.
If you have never used it
If a README said install Go, get the MSI from go.dev/dl. The SDK lands as go.exe in Program Files\Go. That is not rustc.exe. GOPATH and module caches live under your user profile. A go.exe inside a project is unusual and worth inspecting.
What is it used for?
go build and go test. cargo.exe will not build a go.mod.
The MSI under Program Files\Go. rustup uses a user-profile layout instead.
Downloads under %USERPROFILE%\go\pkg\mod. That folder is not node_modules.
Who is it for?
- People following a Go tutorial on Windows
- Users who saw go.exe and thought it was a game
- Anyone who installed rustup and wondered where go env went
Current status
Go (2009) is a current language toolchain from Google LLC. The vendor still points Windows users at https://go.dev/dl/.
How old is it?
Google released Go in 2009. Modules replaced GOPATH-as-the-only-story later. Current Windows MSI builds are the product. A 2013 GOPATH-only tutorial is stale on the module parts.
Versions
Major channels first. Exact build numbers are not all verified here.
System requirements
Values follow the publisher's public guidance. Workload still changes the real need.
Minimum
| Operating system | A current 64-bit Windows 10 or Windows 11 release, per go.dev |
|---|---|
| RAM | The SDK is modest. Large builds want more RAM |
Resource profile
- CPU demand
- Follows what you open inside the app
- RAM demand
- Follows documents, tabs, or libraries
Installed processes
These executables belong to this product when it is installed.
| go.exe | Go toolchain |
|---|
Startup components
go.exe does not start with Windows. You invoke it from a terminal or an IDE.
File locations
| Typical install | C:\Program Files\Go\ |
|---|
File formats
Common problems
Old GOPATH tutorial on a modules repo
go.mod is the current story. GOPATH-only notes from 2015 fight current go.exe.
People install MinGW and think they have Go
gcc is not go.exe. Download the SDK from go.dev/dl.
Getting unstuck
go version and where.exe go
Expect Program Files\Go\bin\go.exe. .cargo\bin\rustc.exe is the other toolchain.
Install from go.dev/dl
Google hosts the MSI. A Golang pack on a freeware site is junk.
Check GOPROXY if module download fails
That is a Go module network setting, not a Cargo.toml problem.
Alternatives
Rust if the project is Rust. gcc/MSVC if you are writing C. The official installer is still go.dev/dl.
Official help and downloads
Start with the vendor. Random exe sites are not a support channel.
| Download | go.dev/dl/ Official installer or vendor page |
|---|---|
| Help | go.dev/doc/ Vendor support |
| Official site | go.dev/ Start here, not a random exe host |
| Getting started | go.dev/doc/install Official Windows install steps |
Related hardware
Builds want CPU and RAM. The module cache wants disk. A GPU is not required.
Technical details
Technical details
Vendor version numbers change. This article does not pin a build.
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Go official site · Vendor product page
- Go help · Vendor support
- Go install docs · What Google documents for Windows
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.