# Syncthing Windows Setup v1.27.2

**URL:** https://forum.syncthing.net/t/syncthing-windows-setup-v1-27-2/21375
**Category:** General
**Created:** [January 2, 2024, 4:27pm UTC](https://forum.syncthing.net/t/syncthing-windows-setup-v1-27-2/21375 "2024-01-02T16:27:38Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Nummer378](https://forum.syncthing.net/user_avatar/forum.syncthing.net/nummer378/32/5958_2.png) [@Nummer378](https://forum.syncthing.net/u/Nummer378)
#### Post date: [January 2, 2024, 11:29pm UTC](https://forum.syncthing.net/t/syncthing-windows-setup-v1-27-2/21375/5 "2024-01-02T23:29:11Z")

</div>

Officially go 1.21.0+ doesn’t support Win 7 anymore, that’s correct. However, in practice that only means “we’ve stopped testing with it”, which isn’t the same as “it won’t work”.

It’s go 1.21.5 ([Syncthing crashing after updating to v1.27.1 / Windows 7 / runtime.asmstdcall() - #2 by calmh](https://forum.syncthing.net/t/syncthing-crashing-after-updating-to-v1-27-1-windows-7-runtime-asmstdcall/21248/2)) that happened to include a code change switching to a CNG function that doesn’t exist in legacy builds of Microsoft’s CryptoAPI. That’s what caused an effective “does not work anymore”. Of course there may be even more incompatibilities that haven’t manifested into something noticeable before things broke.

TL;DR: The last syncthing version that _supported_ Win 7 was 1.23.7. The last version that _is known to work for_ Windows 7 is 1.27.0.

---

_[View the full topic](https://forum.syncthing.net/t/syncthing-windows-setup-v1-27-2/21375)._