Problems updating to 1.1.46 because of wrong checksum in open Code Windows Zip. #8128

Open
opened 2026-02-16 18:09:14 -05:00 by yindo · 2 comments
Owner

Originally created by @ullenboom on GitHub (Jan 31, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

Image

I had the same problem with NPM. This screenshot is from Chocolatay.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @ullenboom on GitHub (Jan 31, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description <img width="909" height="201" alt="Image" src="https://github.com/user-attachments/assets/6bbd30bd-669e-4061-83ad-7d10b6c18635" /> I had the same problem with NPM. This screenshot is from Chocolatay. ### Plugins _No response_ ### OpenCode version _No response_ ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the windowsbug labels 2026-02-16 18:09:14 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 31, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #3415: Windows Defender falsely flags new releases as trojans - This epic issue discusses plans to publish checksums (SHA256) for all release assets and code-sign Windows artifacts to reduce false positives and AV issues.

The checksum problem you're reporting in your Windows Zip file may be related to the broader Windows release quality assurance initiative tracked in #3415. That issue also references similar reports including #3388 and #1103.

Feel free to ignore if this doesn't match your specific case, but checking that issue first might provide useful context or workarounds.

@github-actions[bot] commented on GitHub (Jan 31, 2026): This issue might be a duplicate of existing issues. Please check: - #3415: Windows Defender falsely flags new releases as trojans - This epic issue discusses plans to **publish checksums (SHA256) for all release assets** and code-sign Windows artifacts to reduce false positives and AV issues. The checksum problem you're reporting in your Windows Zip file may be related to the broader Windows release quality assurance initiative tracked in #3415. That issue also references similar reports including #3388 and #1103. Feel free to ignore if this doesn't match your specific case, but checking that issue first might provide useful context or workarounds.
Author
Owner

@ullenboom commented on GitHub (Jan 31, 2026):

Looks identical to me:

PS C:\Users\christian> Get-FileHash -Algorithm SHA256 .\opencode-windows-x64.zip

Algorithm       Hash                                                                   Path
---------       ----                                                                   ----
SHA256          4FF11D71B8DB79BE50B2C0191623105BC6C3CE71DA40203BD082ACBCC5E247A8       C:\Users\christian\opencode-w...

Same hash as shown under https://github.com/anomalyco/opencode/releases/tag/v1.1.47 for opencode-windows-x64.zip.

And:

PS C:\Users\christian> Get-AuthenticodeSignature .\opencode.exe | Format-List *


SignerCertificate      :
TimeStamperCertificate :
Status                 : NotSigned
StatusMessage          : Die Datei "C:\Users\christian\opencode.exe" ist nicht digital signiert. Sie können dieses
                         Skript im aktuellen System nicht ausführen. Weitere Informationen zum Ausführen von Skripts
                         und Festlegen der Ausführungsrichtlinie erhalten Sie unter "about_Execution_Policies"
                         (https:/go.microsoft.com/fwlink/?LinkID=135170).
Path                   : C:\Users\christian\opencode.exe
SignatureType          : None
IsOSBinary             : False

I can start OpenCode and the terminal appears.

@ullenboom commented on GitHub (Jan 31, 2026): Looks identical to me: ``` PS C:\Users\christian> Get-FileHash -Algorithm SHA256 .\opencode-windows-x64.zip Algorithm Hash Path --------- ---- ---- SHA256 4FF11D71B8DB79BE50B2C0191623105BC6C3CE71DA40203BD082ACBCC5E247A8 C:\Users\christian\opencode-w... ``` Same hash as shown under https://github.com/anomalyco/opencode/releases/tag/v1.1.47 for [opencode-windows-x64.zip](https://github.com/anomalyco/opencode/releases/download/v1.1.47/opencode-windows-x64.zip). And: ``` PS C:\Users\christian> Get-AuthenticodeSignature .\opencode.exe | Format-List * SignerCertificate : TimeStamperCertificate : Status : NotSigned StatusMessage : Die Datei "C:\Users\christian\opencode.exe" ist nicht digital signiert. Sie können dieses Skript im aktuellen System nicht ausführen. Weitere Informationen zum Ausführen von Skripts und Festlegen der Ausführungsrichtlinie erhalten Sie unter "about_Execution_Policies" (https:/go.microsoft.com/fwlink/?LinkID=135170). Path : C:\Users\christian\opencode.exe SignatureType : None IsOSBinary : False ``` I can start OpenCode and the terminal appears.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8128