# SHA256 checksum not matching

**URL:** <https://onlykey.discourse.group/t/sha256-checksum-not-matching/896>\
**Category:** Site Feedback\
**Created:** [November 4, 2022, 10:24pm UTC](https://onlykey.discourse.group/t/sha256-checksum-not-matching/896 "2022-11-04T22:24:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tazrog](https://avatars.discourse-cdn.com/v4/letter/t/ecc23a/32.png) [@tazrog](https://onlykey.discourse.group/u/tazrog)\
**Post date:** [November 4, 2022, 10:24pm UTC](https://onlykey.discourse.group/t/sha256-checksum-not-matching/896/1 "2022-11-04T22:24:02Z")

</div>

I checked the checksum value for the windows only desktop app and it does not appear to match what is listed on the website. Not sure if I am making a mistake or not.  
I get 22FC0B80D0B11FA5B0F9A566AE11EDB8AEE41E53905259E2A8A948C71E45E1FE for the Onlykey 5.3.6 window desktop app.  
The website has: Windows SHA 256 CHECKSUM: d221f4199be048ce5acf4ffc960b0ca60ff8846242a59f61c1a964d356244194

My guess is the website was not updated with the new SHA256 Checksum. But to be safe, I am not installing.

---

<div class="post-metadata">

**Author:** ![Qverkk](https://avatars.discourse-cdn.com/v4/letter/q/f4b2a3/32.png) [@Qverkk](https://onlykey.discourse.group/u/Qverkk)\
**Post date:** [November 5, 2022, 8:57am UTC](https://onlykey.discourse.group/t/sha256-checksum-not-matching/896/2 "2022-11-05T08:57:12Z")

</div>

U can get the updates from here:

> **[Releases · trustcrypto/OnlyKey-App](https://github.com/trustcrypto/OnlyKey-App/releases)**
>
> The OnlyKey App is used for the initial setup and configuration of OnlyKey. Supported on Windows, macOS, Linux, and Chromebook (with Chrome App). - trustcrypto/OnlyKey-App

Also checksums are available for verification

---

<div class="post-metadata">

**Author:** ![t11](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@t11](https://onlykey.discourse.group/u/t11)\
**Post date:** [November 8, 2022, 4:50pm UTC](https://onlykey.discourse.group/t/sha256-checksum-not-matching/896/3 "2022-11-08T16:50:00Z")

</div>

Thanks for reporting this, it looks like what happened was the docs still pointed to the v5.3.4 link and hashes. This has been corrected in the docs.