microsoft / microsoft/winget-pkgs

[Package Issue]: GoLang.Go's ARM32 installers in 1.19.x〜1.23.8 are broken and should be removed.

Open
#436,952 0 comments 0 reactions 0 assignees View on GitHub
Issue-Bug Needs-Triage
Dominant language
No language data
Stars
11.1k
Forks
9.7k
PR merge metrics
PR metrics pending

Description

### Please confirm these before moving forward

- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] I have not been informed if the issue is resolved in a preview version of the winget client.

### Category of the issue

Other

### Brief description of your issue

Yesterday I was able to acquire a Samsung Galaxy Book Go 1, making me able to test not only ARM64 apps, but since it has a pre-"Snapdragon X" CPU and shipped with 23H2 by default I'm also able to test ARM32 apps.

So while I tested the ARM32 version of `GoLang.Go`, I noticed that while it installed correctly, the post-installation .exe-s seemed to not really do anything.

Image

Apparently this is/was a known problem to Team Go, who believe it to have affected all Go versions after 1.18.x and until they removed designated ARM32 installers in 1.24.0 onwards:

* https://github.com/golang/go/issues/71671

Therefore, the supposed ARM32 installers for the affected versions' Winget manifests should be removed. This would require making 55〜64 "Update version" PRs, which is more than I can do on my own.

### Steps to reproduce

1) Acquire a "Snapdragon 7c Gen 2" PC device.
2) Run Windows 11 ≤23H2
3) Run `winget install GoLang.Go -v 1.23.8 -a arm -s winget`
4) See that it installs correctly.
5) Run `go version` in PowerShell.
6) See that no text emerges from it.

### Actual behavior

ARM32 builds of Go ≥〜1.19.0 are broken due to known Go bugs.

### Expected behavior

Either:
1) That the ARM32 builds of Go ≥〜1.19.0 would work, which they are known to not do, making option 2 the only viable option.
2) That non-functioning ARM32 installers are not in the affected versions' manifests.

### Environment

```raw
Windows Package Manager v1.29.290
© 2026 Microsoft. All rights reserved.

Windows: Windows.Desktop v10.0.22631.6199
System Architecture: Arm64
Package: Microsoft.DesktopAppInstaller v1.29.290.0

WinGet Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User) %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root C:\Program Files\WinGet\Packages
Portable Package Root (x86) C:\Program Files (x86)\WinGet\Packages
Installer Downloads %USERPROFILE%\Downloads
Configuration Modules %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
---------------------------------------------------------------------------
Privacy Statement https://aka.ms/winget-privacy
License Agreement https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting State
--------------------------------------------------
LocalManifestFiles Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride Disabled
LocalArchiveMalwareScanOverride Disabled
ProxyCommandLineOptions Disabled
ConfigurationProcessorPath Disabled
DefaultProxy Disable
```

### Screenshots and Logs

Image

I'm unsure in a hurry how to get go.exe logs, however.

Contributor guide

Open the contributing guide

Research direction

Start by locating the GoLang.Go manifests for versions 1.19.x through 1.23.8 and reviewing their ARM32 installer entries. Confirm the affected architecture and versions against the linked Team Go issue, then update the manifests so the broken ARM32 installers are absent and validate the resulting manifest changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
operating-systems, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.